Hi,

2/3 are known issues, resolved once the help plugin is released (its not
part of the bootstrap).

4 is something on your instance, so I'm not sure anything can be done
about that.

Someone will need to see if we can reproduce it0088 using the tag to see
if maybe it was only fixed in some environments.

- Brett

Grzegorz Słowikowski wrote:
> Hi
> 
> I just cleared my local repo and tried to bootstrap Maven from 2.0.2 tag.
> There are some problems in integration tests (localhost:9999 is my maven 
> proxy):
> I think 2. and 3. should be fixed easy and quickly.
> 
> 1. it0088
> Log fragment:
> 
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> [surefire] Running org.apache.maven.it0088.PomInterpolationTest
> [surefire] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 0,047 sec 
> <<<<<<<< FAILURE !! 
> 
> Results :
> [surefire] Tests run: 2, Failures: 2, Errors: 0
> 
> [INFO] 
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] There are some test failure.
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: There are some test 
> failure.
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>  at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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.MojoExecutionException: There are some 
> test failure.
>  at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:384)
>  at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530)
>  ... 16 more
> 
> 
> 2. it0075
> It tries to use maven-help-plugin. There are no releases of this plugin on 
> ibiblio.
> There is only maven-projecthelp-plugin (old name of this plugin) 2.0-beta-1.
> I think that someone spoiled 
> www.ibiblio.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> file (probably the one who releases pmd plugin). There are no prefix -> 
> artifactid mappings
> except pmd.
> 
> Log fragment:
> 
> [INFO] 
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-help-plugin' does not exist 
> or no valid version could be found
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 
> 'org.apache.maven.plugins:maven-help-plugin' does not exist or no valid 
> version could be found
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1203)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1436)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:378)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:134)
>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>  at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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.version.PluginVersionNotFoundException: 
> The plugin 'org.apache.maven.plugins:maven-help-plugin' does not exist or no 
> valid version could be found
>  at 
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
>  at 
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>  at 
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1174)
>  ... 14 more
> 
> 
> 3. it0043
> The same problem as with it0075
> Log fragment:
> 
> [INFO] 
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-help-plugin' does not exist 
> or no valid version could be found
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 
> 'org.apache.maven.plugins:maven-help-plugin' does not exist or no valid 
> version could be found
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1203)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1383)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:378)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:134)
>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>  at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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.version.PluginVersionNotFoundException: 
> The plugin 'org.apache.maven.plugins:maven-help-plugin' does not exist or no 
> valid version could be found
>  at 
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
>  at 
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>  at 
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177)
>  at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1174)
>  ... 14 more
> 
> 
> 4. it0016
> I havent seen http 500 error for long time (maybe because I use proxy, and 
> not I cleaned it and in efect downloaded
> more artifacts than usually)
> 
> Log fragment:
> 
> [INFO] 
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> 
> Error transferring file
>   javax.servlet:servlet-api:jar:2.4
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   maven-proxy (http://localhost:9999/repository),
>   repo-piaskownica (http://piaskownica.tiger.com.pl:5080/repository/m2)
> Path to dependency: 
>  1) org.apache.maven:maven-core-it0016:war:1.0
>  2) javax.servlet:servlet-api:jar:2.4
> 
> 
> 
> Caused by I/O exception: Server returned HTTP response code: 500 for URL: 
> http://localhost:9999/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar.sha1
> 
> 
> 
> Greetings
> 
> Greg
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to