[jboss-dev] Re: Update to maven-compiler-plugin

[Paul Gier]

You can try removing the metadata in the repository.  I've seen similar problems 
to this when we have our own versions of plugins that are in the central 
repository.  Maven could be having a problem because when it finds the metadata 
in our repo it thinks that is the valid metadata for that artifact so it doesn't 
look at the central repository metadata for the same artifact.

I'd like to split the repository into a few different parts, that I think could 
help with problems like this.

[1] http://repository.jboss.org/maven2

This is where we should deploy jboss projects that we have developed.

[2] http://repository.jboss.org/maven2_thirdparty

This is where we could deploy artifacts that are not controlled by us.  So this 
could be copies and/or forks of projects that we depend on.

[3] http://repository.jboss.org/maven2_legacy

This is where we put old artifacts that were named incorrectly and are not 
needed in any current builds, but still need to be kept for historical builds.


I think dividing up the repositories like this will help to keep [1] a lot 
cleaner for those who only want to use that one.  It should also help with 
debugging problems that have to do with one or more of the repositories.



Thomas Diesler wrote:
> Folks have been reporting the error below
> 
> Unfortunately, I don't know what could be causing this. I've tested the 
> plugin with maven 2.0.7 and 2.0.9
> 
> [INFO] Internal error in the plugin manager executing goal 
> 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:compile': Una
> ble to find the mojo 
> 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:compile' in 
> the plugin 'org.apache.maven.plugins:ma
> ven-compiler-plugin'
> org/codehaus/plexus/compiler/util/scan/InclusionScanException
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error 
> in the plugin manager executing goal 'org.apache.maven.plug
> ins:maven-compiler-plugin:2.0.2.SP1:compile': Unable to find the mojo 
> 'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:co
> mpile' in the plugin 'org.apache.maven.plugins:maven-compiler-plugin'
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543) 
> 
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) 
> 
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) 
> 
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) 
> 
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) 
> 
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) 
> 
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> 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.PluginManagerException: Unable to 
> find the mojo 'org.apache.maven.plugins:maven-compiler-plugin
> :2.0.2.SP1:compile' in the plugin 
> 'org.apache.maven.plugins:maven-compiler-plugin'
> at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:575) 
> 
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:425) 
> 
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) 
> 
> ... 16 more
> Caused by: 
> org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
> Unable to lookup component 'org.apache.mav
> en.plugin.Mojoorg.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:compile', 
> it could not be created
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) 
> 
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) 
> 
> at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566) 
> 
> ... 18 more
> Caused by: 
> org.codehaus.plexus.component.factory.ComponentInstantiationException: 
> Could not instanciate component: role: 'null', i
> mplementation: 'org.apache.maven.plugin.CompilerMojo'
> at 
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) 
> 
> at 
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) 
> 
> at 
> org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464) 
> 
> at 
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93 
> 
> )
> at 
> org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48) 
> 
> at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) 
> 
> ... 20 more
> Caused by: java.lang.NoClassDefFoundError: 
> org/codehaus/plexus/compiler/util/scan/InclusionScanException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
> at java.lang.Class.getConstructor0(Class.java:2671)
> at java.lang.Class.newInstance0(Class.java:321)
> at java.lang.Class.newInstance(Class.java:303)
> at 
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44) 
> 
> ... 24 more
> 
> 
> 
> Thomas Diesler wrote:
>> Folks,
>>
>> I updated the maven-compiler-plugin to version 2.0.2.SP1 to support a 
>> testExcludeFile
>>
>> For details, see http://jira.codehaus.org/browse/MCOMPILER-72
>>
>> cheers
>> -thomas
>>
>