RE: Maven/OS X Development Question
I didn't describe the issue well enough. I am using m2eclipse but that's not pertinent to the issue. The same errors were appearing and related to whether I had the JDK set to 1.5 or 1.6. I was trying to debug the errors from the command line. So I think it really does belong on this forum. I did actually get further by specifying JDK 1.6 for launching the mvn commands but I run into another very different problem when trying to launch the RCP with 1.6 set. It was swt-carbon-3349 jar missing and I need to be able to run on JDK 1.5 anyway so I haven't yet tracked down that issue. All of these maven issues I read related to mvn command line invocations that work in JDK 1.6 and break with JDK 1.5. Any ideas? Wayne Eugene Kuleshov wrote: > > > wxlund wrote: >> >> I'm getting a very similar problem. I'm running eclipse and maven and >> working with the new m2eclipse plugin on OS X doing RCP development with >> Maven. When I try and install my jars with JDK 5.0 configured I get the >> following: >> [skip] >> Now you'd think I'd be a happy camper except that for project reasons I >> must have my JDK set to JDK 5.0. When I execute the mvn commands from >> m2eclipse I get the same errors as I show from the command line. Does >> anybody know what I have to do to get JDK 5.0 working with maven? >> > > Wayne, from your description it is unclear what issue you have with > m2eclipse. For custom Maven launch configurations you can specify what JRE > and Maven runtime is used. You can also see what command line is used by > m2eclipse to launch Maven. See > http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-HowtoretrieveanactualcommandlineusedtostartJVMandMaven > > Please also note that recent m2eclipse builds provide wizards to create > new projects using archetypes and to install artifacts to the local Maven > repository. See > http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy > > BTW, it is better to ask questions related to m2eclipse in its own > mailing list. See http://m2eclipse.codehaus.org/mail-lists.html > > Thanks > > Eugene > > > -- View this message in context: http://www.nabble.com/Maven-OS-X-Development-Question-tp19334759p20355105.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven/OS X Development Question
I'm getting a very similar problem. I'm running eclipse and maven and working with the new m2eclipse plugin on OS X doing RCP development with Maven. When I try and install my jars with JDK 5.0 configured I get the following: = setup = wayne-lunds-macbook-pro:jars wxlund$ java -version java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-284) Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing) echo $MAVEN_HOME /opt/apache-maven-2.0.9 = and error in mvn install:install-file == vn install:install-file -Dfile="activation.jar" -DgroupId=skyway -DartifactId=activation -Dversion=1.0 -Dpackaging=jar [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'install'. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'groupId=skyway': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Tue Nov 04 15:02:28 PST 2008 [INFO] Final Memory: 1M/3M [INFO] I validated the same error with appfuse. mvn archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-core -DremoteRepositories=http://static.appfuse.org/releases -DarchetypeVersion=2.0.2 -DgroupId=com.mycompany.app -DartifactId=myproject [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Invalid task 'archetypeArtifactId=appfuse-core': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Tue Nov 04 15:04:51 PST 2008 [INFO] Final Memory: 2M/4M [INFO] Now I switch to JDK 6.0 and run it again. == setup java home to JDK 6.0 wayne-lunds-macbook-pro:jars wxlund$ echo $JAVA_HOME /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home mvn install:install-file -Dfile="activation.jar" -DgroupId=skyway -DartifactId=activation -Dversion=1.0 -Dpackaging=jar [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'install'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [install:install-file] (aggregator-style) [INFO] ---- [INFO] [install:install-file] [INFO] Installing /Users/wxlund/skyway/workspace/ce-6.1/org.accenture.fa.maven.archetype/jars/activation.jar to /Users/wxlund/.m2/repository/skyway/activation/1.0/activation-1.0.jar [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Nov 04 15:06:07 PST 2008 [INFO] Final Memory: 5M/15M [INFO] and the appfuse archetype = vn archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-core -DremoteRepositories=http://static.appfuse.org/releases -DarchetypeVersion=2.0.2 -DgroupId=com.mycompany.app -DartifactId=myproject [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on => 'false'. [INFO] Setting property: resource.loader =&
Re: mvn site vs mvn package differences caused by cobertura
After a little more exploring I found the root problem for the inconsistency between mvn site and mvn package. (Disclaimer: I've used maven for a few years but have always leaned on smart Dev Arch guys that know the tool much better than myself for setting things up correctly). Anyway, the culprit is the cobertura step. Cobertura reruns the tests but doesn't run them with the required maven-psteclipse-plugin. This explains why it throws bogus errors on not being able to find the bundle activators. Question: How can I get Cobertura to use psteclipse (Junit Plug-in Tests) for running the tests instead of the default junit testing? For now I commented it out of the reporting section so that I can at least see the results of unit testing. Any help would be appreciated. -- View this message in context: http://www.nabble.com/mvn-site-vs-mvn-package-differences-with-eclipse-plugin-tp17372004p17386787.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn site vs mvn package differences with eclipse plung
I am having problems getting my surefire reports from mvn site. When I run mvn package the unit tests seem to report the tests correctly. I randomly tested the failed tests within eclipse and found that the failing tests broken inside and outside of eclipse (meaning when I run mvn package). I correctly get the following: [INFO] Scanning for projects... ... BUILD SUCCESSFUL Total time: 2 minutes 49 seconds [INFO] Extracting errors and failures from surefire reports --- T E S T S --- Ran com.accenture.tools.sd.model.domain.util.BaseTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.15 sec <<< FAILURE! Ran com.accenture.tools.sd.model.domain.util.Composite_MultiLineEntryTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.25 sec Ran com.accenture.tools.sd.model.domain.util.CreateNamesTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.0 sec Ran com.accenture.tools.sd.model.domain.util.DomainaValidatorBorderTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.959 sec Ran com.accenture.tools.sd.model.domain.util.DomainOverrideTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.15 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatoMenuTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.159 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorBaseEnumerationTypeTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.039 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorBitmapTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.979 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorClientTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.978 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorComboBoxTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.029 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorComponentTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.069 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorCompositeCompositeTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.899 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorCompositeDataWidgetTest Tests run: 7, Failures: 6, Errors: 0, Skipped: 0, Time elapsed: 0.979 sec <<< FAILURE! Ran com.accenture.tools.sd.model.domain.util.DomainValidatorCompositeElementTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.999 sec <<< FAILURE! Ran com.accenture.tools.sd.model.domain.util.DomainValidatorCompositeRadioButtonTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.089 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorCompositeTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.139 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorDataElementTest Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.269 sec <<< FAILURE! Ran com.accenture.tools.sd.model.domain.util.DomainValidatorDataSetTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.109 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorFacetBaseDateTimeTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.969 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorFileStructureTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.079 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorFontTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.029 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorGhostStaticImageTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.019 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorIndexTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.989 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorJpegTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.029 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorListBoxTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.889 sec <<< ERROR! Ran com.accenture.tools.sd.model.domain.util.DomainValidatorlistboxwidgetElementTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.818 sec <<< ERROR! Ran com.accenture.tools.sd.model.domain.util.DomainValidatorMaskTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.869 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorMessageTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.059 sec Ran com.accenture.tools.sd.model.domain.util.DomainValidatorMultiLineEntryTest Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.969 sec <<< FAILURE! Ran com.accenture.tool
