Re: [m2] quick update question, Mac OS X build failure
Ok thanks, useful property to know. Also at last I've noticed I get an integration test countdown! Worth pointing out is that for the last four svn updates over a week and a half I consistently get: Failed tests: [it0065, it0063]. You should know that it doesn't (seem to) affect day to day maven usage though. Here are the details of the two failures on Mac OS X tiger: ** it0065... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean install *** Verifying: fail when [ERROR] detected? true *** Error Stacktrace: org.apache.maven.it.VerificationException: Expected file was not found: /Users/developer/projects/maven-working/maven-core-it/it0065/ target/parent-basedir at org.apache.maven.it.Verifier.verifyExpectedResult (Verifier.java:530) at org.apache.maven.it.Verifier.verify(Verifier.java:117) at org.apache.maven.it.Verifier.main(Verifier.java:759) Error Stacktrace * it0063... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean package - Standard Error - Exit code: 1 Error Stacktrace: org.apache.maven.it.VerificationException at org.apache.maven.it.Verifier.executeGoals(Verifier.java:639) at org.apache.maven.it.Verifier.main(Verifier.java:753) Error Stacktrace Log file contents: + Error stacktraces are turned on. [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] [INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0 [INFO]task-segment: [clean:clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Main Error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 Root error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 On 12 Sep 2005, at 14:43, Brett Porter wrote: That's the safest option, but I also do this: m2 install cp target/*.jar $M2_HOME/lib for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] quick update question, Mac OS X build failure
65 was only created in the last couple of hours and I broke it - fixing now. 63 is a bug on Mac OS X - it would be great if you could file that in JIRA as it will mean you can't use anything wanting tools.jar as a dependency. Thanks, Brett On 9/12/05, Ashley Williams [EMAIL PROTECTED] wrote: Ok thanks, useful property to know. Also at last I've noticed I get an integration test countdown! Worth pointing out is that for the last four svn updates over a week and a half I consistently get: Failed tests: [it0065, it0063]. You should know that it doesn't (seem to) affect day to day maven usage though. Here are the details of the two failures on Mac OS X tiger: ** it0065... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean install *** Verifying: fail when [ERROR] detected? true *** Error Stacktrace: org.apache.maven.it.VerificationException: Expected file was not found: /Users/developer/projects/maven-working/maven-core-it/it0065/ target/parent-basedir at org.apache.maven.it.Verifier.verifyExpectedResult (Verifier.java:530) at org.apache.maven.it.Verifier.verify(Verifier.java:117) at org.apache.maven.it.Verifier.main(Verifier.java:759) Error Stacktrace * it0063... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean package - Standard Error - Exit code: 1 Error Stacktrace: org.apache.maven.it.VerificationException at org.apache.maven.it.Verifier.executeGoals(Verifier.java:639) at org.apache.maven.it.Verifier.main(Verifier.java:753) Error Stacktrace Log file contents: + Error stacktraces are turned on. [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] [INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0 [INFO] task-segment: [clean:clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Main Error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 Root error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 On 12 Sep 2005, at 14:43, Brett Porter wrote: That's the safest option, but I also do this: m2 install cp target/*.jar $M2_HOME/lib for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] quick update question, Mac OS X build failure
the tools.jar bug is now in jira. On 12 Sep 2005, at 15:24, Brett Porter wrote: 65 was only created in the last couple of hours and I broke it - fixing now. 63 is a bug on Mac OS X - it would be great if you could file that in JIRA as it will mean you can't use anything wanting tools.jar as a dependency. Thanks, Brett On 9/12/05, Ashley Williams [EMAIL PROTECTED] wrote: Ok thanks, useful property to know. Also at last I've noticed I get an integration test countdown! Worth pointing out is that for the last four svn updates over a week and a half I consistently get: Failed tests: [it0065, it0063]. You should know that it doesn't (seem to) affect day to day maven usage though. Here are the details of the two failures on Mac OS X tiger: ** it0065... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean install *** Verifying: fail when [ERROR] detected? true *** Error Stacktrace: org.apache.maven.it.VerificationException: Expected file was not found: /Users/developer/projects/maven-working/maven-core-it/it0065/ target/parent-basedir at org.apache.maven.it.Verifier.verifyExpectedResult (Verifier.java:530) at org.apache.maven.it.Verifier.verify(Verifier.java:117) at org.apache.maven.it.Verifier.main(Verifier.java:759) Error Stacktrace * it0063... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean package - Standard Error - Exit code: 1 Error Stacktrace: org.apache.maven.it.VerificationException at org.apache.maven.it.Verifier.executeGoals(Verifier.java:639) at org.apache.maven.it.Verifier.main(Verifier.java:753) Error Stacktrace Log file contents: + Error stacktraces are turned on. [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] - --- [INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0 [INFO] task-segment: [clean:clean, package] [INFO] - --- [INFO] [clean:clean] [INFO] [resources:resources] [INFO] - --- [INFO] BUILD FAILURE [INFO] - --- [INFO] Main Error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../ lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 Root error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../ lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 On 12 Sep 2005, at 14:43, Brett Porter wrote: That's the safest option, but I also do this: m2 install cp target/*.jar $M2_HOME/lib for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
