Cool...I'll back out the change and find the right template....
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
"Sam Ruby" <[EMAIL PROTECTED]>
05/04/02 11:03 PM
Please respond to turbine-maven-dev
To: [EMAIL PROTECTED]
cc:
Subject: Re: cvs commit: jakarta-turbine-maven/src/templates/build
build-gump.xml
The problem with this is that this places a nag entry into an Ant build
file (both have project elements, so this is confusing, but note the
<target> elements). Needless to say, adding nag entries there doesn't do
much for Gump but confuses the heck out of Ant.
A contributing issue is the confusing name given to this template.
- Sam Ruby
[EMAIL PROTECTED] on 05/04/2002 08:55:58 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: cvs commit: jakarta-turbine-maven/src/templates/build
build-gump.xml
dion 02/05/04 05:55:58
Modified: src/templates/build build-gump.xml
Log:
Added gump nag back
Revision Changes Path
1.4 +6 -0
jakarta-turbine-maven/src/templates/build/build-gump.xml
Index: build-gump.xml
===================================================================
RCS file:
/home/cvs/jakarta-turbine-maven/src/templates/build/build-gump.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- build-gump.xml 3 May 2002 01:30:14 -0000 1.3
+++ build-gump.xml 4 May 2002 12:55:57 -0000 1.4
@@ -32,6 +32,12 @@
basedir="${build.dest}"
excludes="**/package.html"
/>
+
+#if ( $project.build.nagEmailAddress )
+
+ <nag from="$project.build.nagEmailAddress" to
="$project.build.nagEmailAddress"/>
+
+#end
</target>
