The tests issue seems to be a transient test subsystem problem, not an issue with the actual plugin. If tests of the plugin do work as expected when the subsystem holds up, should this really hold a release? Take a look at MECLIPSE-248 to see if the suggestions in there clear up the tests on solaris for you.
-----Original Message----- From: Vincent Siveton [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 7:22 PM To: Maven Developers List Subject: Re: [VOTE] maven-eclipse-plugin 2.4 Same thing here: Tests work on windows, failed on solaris so -1 too Cheers, Vincent 2007/7/4, Kenney Westerhof <[EMAIL PROTECTED]>: > Update: > > It seems i was impatient, it took almost 3 minutes to run that single test. > After that it continued (on 2.0.7), but I got a failure: > > ------------------------------------------------------------------------ ------- > Test set: org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest > ------------------------------------------------------------------------ ------- > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 39.878 sec <<< FAILURE! > testModule1Project(org.apache.maven.plugin.eclipse.EclipsePluginMasterPr ojectTest) Time elapsed: 11.979 sec <<< ERROR! > org.apache.maven.plugin.eclipse.ExecutionFailedException: Failed to execute build. > POM: /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl ugin/target/test-classes/projects/master-test/pom.xml > Goals: org.apache.maven.plugins:maven-eclipse-plugin:test:clean, org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse > Exit Code: 1 > Error: null > Build Log: file:/vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclip se-plugin/target/surefire-reports/build-output/org.apache.maven.plugin.e clipse.EclipsePluginMasterProjectTest_testModule1Project.build.log > (Resulting exit code: 1) > at org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.executeMav en(AbstractEclipsePluginTestCase.java:309) > > Last part of the file:/ indicated above: > > [ERROR] BUILD ERROR > [INFO] ------------------------------------------------------------------------ > [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin' > Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugi n:test:eclipse. > [INFO] ------------------------------------------------------------------------ > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse': Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin' > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:543) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:493) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:463) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-eclipse-plugin:test:eclipse' in the plugin 'org.apache.maven.plugins:maven-eclipse-plugin' > at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl uginManager.java:571) > at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:421) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) > ... 16 more > Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupExcept ion: Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse-plugi n:test:eclipse. > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:323) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:312) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:440) > at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl uginManager.java:562) > ... 18 more > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 9 seconds > > > btw, tests take about 7 minutes whereas bootstrapping maven itself takes only 3 minutes. > > my -1 stands, unless I'm the only one where this fails. > > -- Kenney > > Kenney Westerhof wrote: > > I assume this is a vote to _release_ maven-eclipse-plugin 2.4. > > > > -1 until the tests are fixed: > > > > > > [INFO] [surefire:test] > > [INFO] Surefire report directory: > > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl ugin/target/surefire-reports > > > > > > ------------------------------------------------------- > > T E S T S > > ------------------------------------------------------- > > Running org.apache.maven.plugin.eclipse.AddMavenRepoMojoTest > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.899 sec > > Running > > org.apache.maven.plugin.eclipse.writers.EclipseOSGiManifestWriterTest > > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec > > Running org.apache.maven.plugin.eclipse.RadPluginTest > > *** Running test builds; output will be directed to: > > target/surefire-reports/build-output > > > > [INFO] Installing target/maven-eclipse-plugin-test.jar to > > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl ugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-eclipse-p lugin/test/maven-eclipse-plugin-test.jar > > > > [INFO] Installing ../pom.xml to > > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl ugin/target/test-classes/m2repo/org/apache/maven/plugins/maven-plugins/9 -SNAPSHOT/maven-plugins-9-SNAPSHOT.pom > > > > [INFO] Installing ../../pom/maven/pom.xml to > > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl ugin/target/test-classes/m2repo/org/apache/maven/maven-parent/6-SNAPSHOT /maven-parent-6-SNAPSHOT.pom > > > > [INFO] Installing ../../pom/maven/../asf/pom.xml to > > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl ugin/target/test-classes/m2repo/org/apache/apache/5-SNAPSHOT/apache-5-SN APSHOT.pom > > > > *** Installed test-version of the Eclipse plugin to: > > /vol/home/forge/work/opensource-rw/maven-trunks/plugins/maven-eclipse-pl ugin/target/test-classes/m2repo > > > > > > and it indefinitely hangs at this point, no cpu load. > > > > > > Tested with maven 2.1 and 2.0.7. > > Otherwise the plugin works great. > > > > -- Kenney > > > > Brian E. Fox wrote: > >> It's been about 5 months since an eclipse plugin release and we have > >> lots of fixes and a handful of enhancements: > >> > >> Bug > >> * [MECLIPSE-108] - .wtpmodules with version 2.4 for > >> javax.servlet:servlet-api:2.3 > >> * [MECLIPSE-109] - .component wb-resource source path incorrect for ear > >> packaging > >> * [MECLIPSE-151] - Incorrect name for test sources jars > >> * [MECLIPSE-198] - EJB version is not resloved > >> * [MECLIPSE-215] - WTP 1.5 Documentation > >> * [MECLIPSE-220] - Incorrect eclipse facet information when doing mvn > >> eclipse:eclipse for war and ejb projects. > >> * [MECLIPSE-225] - Invalid .classpath Entries. > >> * [MECLIPSE-233] - Manifest attributes incorrectly treated as > >> case-sensitive > >> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs() reuses > >> String method argument causing maven-eclipse.xml copy-resources problems > >> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the > >> resolution:=optional directive > >> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method > >> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't used in > >> wtp facet > >> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory Server > >> to be built > >> * [MECLIPSE-248] - Eclipse plugin looks for pom version "test" > >> * [MECLIPSE-255] - WTP Settings does not use servlet-api version defined > >> in pom.xml > >> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0 in a > >> Java 5.0 project > >> * [MECLIPSE-278] - duplicated classpathentries > >> * [MECLIPSE-279] - PDE projects should be considered java projects in > >> all cases > >> * [MECLIPSE-287] - Regression - fails to correctly construct classpath > >> containing dependencies with classifiers > >> Improvement > >> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF > >> * [MECLIPSE-267] - Resolve version ranges in make-artifacts > >> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of servlet > >> version, jsp version, ... possible through pom configuration > >> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder > >> creation while executing eclipse:rad > >> New Feature > >> * [MECLIPSE-119] - Allow custom project name for eclipse projects > >> * [MECLIPSE-189] - addVersionToProjectName property > >> * [MECLIPSE-251] - Allows prefixing of eclipse project name > >> * [MECLIPSE-271] - Ability to skip > >> > >> The site has been updated: > >> http://maven.apache.org/plugins/maven-eclipse-plugin > >> > >> Plugin is staged here: > >> http://people.apache.org/~brianf/staging-repository/ > >> > >> Vote is open for 72hrs. > >> > >> +1 > >> > >> > >> --------------------------------------------------------------------- > >> 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
