I noticed this was failing too - the original test in maven.xml was calling the wrong location, but that seems to be fixed.
maven maven:jar-install currently fails this test too, so the problem is probably still reactor related.
I've also noticed that setting ~/build.properties to have a maven.username (userful for anyone running site:deploy or similar) breaks this test, which is expected. Should there be a way to have touchstone ignore ~/build.properties?
- Brett
[EMAIL PROTECTED] wrote:
jvanzyl 2003/06/09 20:23:51
Modified: src/test/touchstone-build maven.xml
Log:
o This will fix the bootstrap until I find out what the problem is. I actually
think there is a problem with the bootstrap ...
Revision Changes Path
1.35 +3 -1 maven/src/test/touchstone-build/maven.xml
Index: maven.xml
===================================================================
RCS file: /home/cvs/maven/src/test/touchstone-build/maven.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- maven.xml 7 Jun 2003 01:27:53 -0000 1.34
+++ maven.xml 10 Jun 2003 03:23:51 -0000 1.35
@@ -186,8 +186,10 @@
but was set to '${test-mavenjellyscope}'.
</fail> </j:if>
-
+ + <!--
<attainGoal name="test-reactor-maven-username"/>
+ -->
</goal>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Web Developer f2 network ~ everything essential 02 8596 4437
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
