Update to maven-compiler-plugin

Folks,

I updated the maven-compiler-plugin to version 2.0.2.SP1 to
support a 
testExcludeFile

For details, see http://j
ira.codehaus.org/browse/MCOMPILER-72

cheers
-thomas

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

The only problem I have with exclude files is that the
negative scenario 
is never tested. So when the actual fix is made it's up to
the developer 
to clean up the excludes.

If he doesn't do that, then regression might set in
unnoticed.

Also failure might change in the mean time, so the known
issue becomes 
invalid.

In the past I've been thinking about a change in Junit where
a test goes 
yellow instead of green or red. Meaning a known issue has
been detected.
That way both QA and Dev can ascertain the status of a run.

Carlo

Thomas Diesler wrote:
> Folks,
> 
> I updated the maven-compiler-plugin to version
2.0.2.SP1 to support a 
> testExcludeFile
> 
> For details, see http://j
ira.codehaus.org/browse/MCOMPILER-72
> 
> cheers
> -thomas
> 

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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:co
mpile': Una
ble to find the mojo 
'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:co
mpile' in 
the plugin 'org.apache.maven.plugins:ma
ven-compiler-plugin'
org/codehaus/plexus/compiler/util/scan/InclusionScanExceptio
n
[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.executeG
oals(DefaultLifecycleExecutor.java:543)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oalWithLifecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oal(DefaultLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeT
askSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:143)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:33
3)
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(NativeMethodAcce
ssorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.ja
va: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.getConfiguredMo
jo(DefaultPluginManager.java:575)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(Def
aultPluginManager.java:425)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oals(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: 
org.codehaus.plexus.component.repository.exception.Component
LookupException: 
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(DefaultPle
xusContainer.java:335)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPle
xusContainer.java:440)
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMo
jo(DefaultPluginManager.java:566)
... 18 more
Caused by: 
org.codehaus.plexus.component.factory.ComponentInstantiation
Exception: 
Could not instanciate component: role: 'null', i
mplementation: 'org.apache.maven.plugin.CompilerMojo'
at 
org.codehaus.plexus.component.factory.java.JavaComponentFact
ory.makeException(JavaComponentFactory.java:77)
at 
org.codehaus.plexus.component.factory.java.JavaComponentFact
ory.newInstance(JavaComponentFactory.java:62)
at 
org.codehaus.plexus.DefaultPlexusContainer.createComponentIn
stance(DefaultPlexusContainer.java:1464)
at 
org.codehaus.plexus.component.manager.AbstractComponentManag
er.createComponentInstance(AbstractComponentManager.java:93
)
at 
org.codehaus.plexus.component.manager.PerLookupComponentMana
ger.getComponent(PerLookupComponentManager.java:48)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPle
xusContainer.java:331)
... 20 more
Caused by: java.lang.NoClassDefFoundError: 
org/codehaus/plexus/compiler/util/scan/InclusionScanExceptio
n
at java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.lang.Class.privateGetDeclaredConstructors(Class.java:23
57)
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.JavaComponentFact
ory.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://j
ira.codehaus.org/browse/MCOMPILER-72
> 
> cheers
> -thomas
> 

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

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://repo
sitory.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:co
mpile': Una
> ble to find the mojo 
>
'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:co
mpile' in 
> the plugin 'org.apache.maven.plugins:ma
> ven-compiler-plugin'
>
org/codehaus/plexus/compiler/util/scan/InclusionScanExceptio
n
> [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.executeG
oals(DefaultLifecycleExecutor.java:543) 
> 
> at 
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oalWithLifecycle(DefaultLifecycleExecutor.java:480) 
> 
> at 
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oal(DefaultLifecycleExecutor.java:459) 
> 
> at 
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oalAndHandleFailures(DefaultLifecycleExecutor.java:311) 
> 
> at 
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeT
askSegments(DefaultLifecycleExecutor.java:278) 
> 
> at 
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:143) 
> 
> at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:33
3)
> 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(NativeMethodAcce
ssorImpl.java:39) 
> 
> at 
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:25) 
> 
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.ja
va: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.getConfiguredMo
jo(DefaultPluginManager.java:575) 
> 
> at 
>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(Def
aultPluginManager.java:425) 
> 
> at 
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oals(DefaultLifecycleExecutor.java:539) 
> 
> ... 16 more
> Caused by: 
>
org.codehaus.plexus.component.repository.exception.Component
LookupException: 
> 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(DefaultPle
xusContainer.java:335) 
> 
> at 
>
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPle
xusContainer.java:440) 
> 
> at 
>
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMo
jo(DefaultPluginManager.java:566) 
> 
> ... 18 more
> Caused by: 
>
org.codehaus.plexus.component.factory.ComponentInstantiation
Exception: 
> Could not instanciate component: role: 'null', i
> mplementation: 'org.apache.maven.plugin.CompilerMojo'
> at 
>
org.codehaus.plexus.component.factory.java.JavaComponentFact
ory.makeException(JavaComponentFactory.java:77) 
> 
> at 
>
org.codehaus.plexus.component.factory.java.JavaComponentFact
ory.newInstance(JavaComponentFactory.java:62) 
> 
> at 
>
org.codehaus.plexus.DefaultPlexusContainer.createComponentIn
stance(DefaultPlexusContainer.java:1464) 
> 
> at 
>
org.codehaus.plexus.component.manager.AbstractComponentManag
er.createComponentInstance(AbstractComponentManager.java:93

> 
> )
> at 
>
org.codehaus.plexus.component.manager.PerLookupComponentMana
ger.getComponent(PerLookupComponentManager.java:48) 
> 
> at 
>
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPle
xusContainer.java:331) 
> 
> ... 20 more
> Caused by: java.lang.NoClassDefFoundError: 
>
org/codehaus/plexus/compiler/util/scan/InclusionScanExceptio
n
> at java.lang.Class.getDeclaredConstructors0(Native
Method)
> at
java.lang.Class.privateGetDeclaredConstructors(Class.java:23
57)
> 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.JavaComponentFact
ory.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://j
ira.codehaus.org/browse/MCOMPILER-72
>>
>> cheers
>> -thomas
>>
> 

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

That sounds like a good idea. The current maven repo is a
bit of a mess.

Paul Gier wrote:
> 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://repo
sitory.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:co
mpile': Una
>> ble to find the mojo 
>>
'org.apache.maven.plugins:maven-compiler-plugin:2.0.2.SP1:co
mpile' in 
>> the plugin 'org.apache.maven.plugins:ma
>> ven-compiler-plugin'
>>
org/codehaus/plexus/compiler/util/scan/InclusionScanExceptio
n
>> [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.executeG
oals(DefaultLifecycleExecutor.java:543) 
>>
>> at 
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oalWithLifecycle(DefaultLifecycleExecutor.java:480) 
>>
>> at 
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oal(DefaultLifecycleExecutor.java:459) 
>>
>> at 
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oalAndHandleFailures(DefaultLifecycleExecutor.java:311) 
>>
>> at 
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeT
askSegments(DefaultLifecycleExecutor.java:278) 
>>
>> at 
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:143) 
>>
>> at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:33
3)
>> 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(NativeMethodAcce
ssorImpl.java:39) 
>>
>> at 
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:25) 
>>
>> at
java.lang.reflect.Method.invoke(Method.java:585)
>> at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.ja
va: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.getConfiguredMo
jo(DefaultPluginManager.java:575) 
>>
>> at 
>>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(Def
aultPluginManager.java:425) 
>>
>> at 
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeG
oals(DefaultLifecycleExecutor.java:539) 
>>
>> ... 16 more
>> Caused by: 
>>
org.codehaus.plexus.component.repository.exception.Component
LookupException: 
>> 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(DefaultPle
xusContainer.java:335) 
>>
>> at 
>>
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPle
xusContainer.java:440) 
>>
>> at 
>>
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMo
jo(DefaultPluginManager.java:566) 
>>
>> ... 18 more
>> Caused by: 
>>
org.codehaus.plexus.component.factory.ComponentInstantiation
Exception: 
>> Could not instanciate component: role: 'null', i
>> mplementation:
'org.apache.maven.plugin.CompilerMojo'
>> at 
>>
org.codehaus.plexus.component.factory.java.JavaComponentFact
ory.makeException(JavaComponentFactory.java:77) 
>>
>> at 
>>
org.codehaus.plexus.component.factory.java.JavaComponentFact
ory.newInstance(JavaComponentFactory.java:62) 
>>
>> at 
>>
org.codehaus.plexus.DefaultPlexusContainer.createComponentIn
stance(DefaultPlexusContainer.java:1464) 
>>
>> at 
>>
org.codehaus.plexus.component.manager.AbstractComponentManag
er.createComponentInstance(AbstractComponentManager.java:93

>>
>> )
>> at 
>>
org.codehaus.plexus.component.manager.PerLookupComponentMana
ger.getComponent(PerLookupComponentManager.java:48) 
>>
>> at 
>>
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPle
xusContainer.java:331) 
>>
>> ... 20 more
>> Caused by: java.lang.NoClassDefFoundError: 
>>
org/codehaus/plexus/compiler/util/scan/InclusionScanExceptio
n
>> at java.lang.Class.getDeclaredConstructors0(Native
Method)
>> at
java.lang.Class.privateGetDeclaredConstructors(Class.java:23
57)
>> 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.JavaComponentFact
ory.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://j
ira.codehaus.org/browse/MCOMPILER-72
>>>
>>> cheers
>>> -thomas
>>>
>>
> 
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment