1:10 p.m.
I'm seeing this error trying to build the common project
Anybody else see this?
Is it just me or is this stuff very flakey! :-)
[common/build] mvn package
<snip/>
Cause: Cannot find setter nor field in
org.apache.maven.archiver.ManifestConfiguration for
'addDefaultSpecificationEntries'
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: Unable
to parse the created DOM for plugin configuration
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
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:256)
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.PluginConfigurationException: Error
configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: Unable
to parse the created DOM for plugin configuration
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1036)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:576)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:390)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot find
setter nor field in org.apache.maven.archiver.ManifestConfiguration for
'addDefaultSpecificationEntries'
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.<init>(ComponentValueSetter.java:68)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1030)
... 19 more
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
1:21 p.m.
Never mind, apparently I've got to upgrade to Maven 2.1 to support this
feature.
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-custom...
I don't suppose there is someway to specify to express a sanity check
so you get a more reasonable error message?
e.g. something like the following in the pom.xml:
<min-maven-version>2.1</min-maven-version>
On Thu, 2007-02-01 at 20:10 +0100, Adrian wrote:
I'm seeing this error trying to build the common project
Anybody else see this?
Is it just me or is this stuff very flakey! :-)
[common/build] mvn package
<snip/>
Cause: Cannot find setter nor field in
org.apache.maven.archiver.ManifestConfiguration for
'addDefaultSpecificationEntries'
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: Unable
to parse the created DOM for plugin configuration
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
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:256)
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.PluginConfigurationException: Error
configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: Unable
to parse the created DOM for plugin configuration
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1036)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:576)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:390)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot find
setter nor field in org.apache.maven.archiver.ManifestConfiguration for
'addDefaultSpecificationEntries'
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.<init>(ComponentValueSetter.java:68)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1030)
... 19 more
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
1:29 p.m.
Hmmm, it's not Maven 2.1 (there's no such thing)
but version 2.1 of the jar plugin
which I already have installed in my maven repository!!!!
More voodoo to try to understand. ;-)
On Thu, 2007-02-01 at 20:21 +0100, Adrian wrote:
Never mind, apparently I've got to upgrade to Maven 2.1 to
support this
feature.
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-custom...
I don't suppose there is someway to specify to express a sanity check
so you get a more reasonable error message?
e.g. something like the following in the pom.xml:
<min-maven-version>2.1</min-maven-version>
On Thu, 2007-02-01 at 20:10 +0100, Adrian wrote:
> I'm seeing this error trying to build the common project
>
> Anybody else see this?
>
> Is it just me or is this stuff very flakey! :-)
>
> [common/build] mvn package
> <snip/>
> Cause: Cannot find setter nor field in
> org.apache.maven.archiver.ManifestConfiguration for
> 'addDefaultSpecificationEntries'
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: Unable
> to parse the created DOM for plugin configuration
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> 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:256)
> 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.PluginConfigurationException: Error
> configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: Unable
> to parse the created DOM for plugin configuration
> at
>
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1036)
> at
>
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:576)
> at
>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:390)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by:
> org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot
find setter nor field in org.apache.maven.archiver.ManifestConfiguration for
'addDefaultSpecificationEntries'
> at
>
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.<init>(ComponentValueSetter.java:68)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
> at
>
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:207)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
> at
>
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
> at
>
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
> at
>
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1030)
> ... 19 more
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
1:47 p.m.
Its running fine for me and I did just update the common trunk projects.
Could be that my local repo already has a valid version of this jar.
What is flakey is relying on the external repos for plugins. Do you see
this plugin being downloaded from an external repo?
[starksm@succubus build]$ mvn package
...
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] JBoss Logging Programming Interface ................... SUCCESS
[1.625s]
[INFO] JBoss Common Classes .................................. SUCCESS
[6.288s]
[INFO] JBoss Logging Log4j ................................... SUCCESS
[0.701s]
[INFO] JBoss Logging JDK ..................................... SUCCESS
[1.009s]
[INFO] JBoss Common Build .................................... SUCCESS
[0.544s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10 seconds
[INFO] Finished at: Thu Feb 01 11:43:25 PST 2007
[INFO] Final Memory: 21M/294M
[INFO]
------------------------------------------------------------------------
[starksm@succubus build]$
Adrian wrote:
Hmmm, it's not Maven 2.1 (there's no such thing)
but version 2.1 of the jar plugin
which I already have installed in my maven repository!!!!
More voodoo to try to understand. ;-)
On Thu, 2007-02-01 at 20:21 +0100, Adrian wrote:
> Never mind, apparently I've got to upgrade to Maven 2.1 to support this
> feature.
>
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-custom...
>
> I don't suppose there is someway to specify to express a sanity check
> so you get a more reasonable error message?
>
> e.g. something like the following in the pom.xml:
> <min-maven-version>2.1</min-maven-version>
>
> On Thu, 2007-02-01 at 20:10 +0100, Adrian wrote:
>> I'm seeing this error trying to build the common project
>>
>> Anybody else see this?
>>
>> Is it just me or is this stuff very flakey! :-)
>>
>> [common/build] mvn package
>> <snip/>
>> Cause: Cannot find setter nor field in
>> org.apache.maven.archiver.ManifestConfiguration for
>> 'addDefaultSpecificationEntries'
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>> configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: Unable
>> to parse the created DOM for plugin configuration
>> at
>>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563)
>> at
1:53 p.m.
Here is what the maven-jar-plugin-2.1.jar in my local checkout of the
repository.jboss.com/maven2/org/apache/maven/plugins/maven-jar-plugin/2.1
cvs contents are. I also use the cvs workspace as my local maven repo.
[starksm@succubus 2.1]$ ls -l maven-jar-plugin-2.1.jar
-rw-rw-r-- 1 starksm starksm 19098 Dec 10 09:01 maven-jar-plugin-2.1.jar
[starksm@succubus 2.1]$ cat maven-jar-plugin-2.1.jar.sha1
980129713b81c844b3538bafbd37ff131941d384
[starksm@succubus 2.1]$ sha1sum maven-jar-plugin-2.1.jar
980129713b81c844b3538bafbd37ff131941d384 maven-jar-plugin-2.1.jar
Adrian wrote:
Hmmm, it's not Maven 2.1 (there's no such thing)
but version 2.1 of the jar plugin
which I already have installed in my maven repository!!!!
More voodoo to try to understand. ;-)
2:17 p.m.
I've managed to fix the problem by blowing away my maven repository
and reloading it.
rm -rf ~/.m2
Before doing that I tried deleting the 2.0 version of the jar-plugin
from the repository.
But it redownloaded it and failed again.
Who knows what the problem was?
Some dodgy reference somewhere in the repository?
On Thu, 2007-02-01 at 11:53 -0800, Scott M Stark wrote:
Here is what the maven-jar-plugin-2.1.jar in my local checkout of
the
repository.jboss.com/maven2/org/apache/maven/plugins/maven-jar-plugin/2.1
cvs contents are. I also use the cvs workspace as my local maven repo.
[starksm@succubus 2.1]$ ls -l maven-jar-plugin-2.1.jar
-rw-rw-r-- 1 starksm starksm 19098 Dec 10 09:01 maven-jar-plugin-2.1.jar
[starksm@succubus 2.1]$ cat maven-jar-plugin-2.1.jar.sha1
980129713b81c844b3538bafbd37ff131941d384
[starksm@succubus 2.1]$ sha1sum maven-jar-plugin-2.1.jar
980129713b81c844b3538bafbd37ff131941d384 maven-jar-plugin-2.1.jar
Adrian wrote:
> Hmmm, it's not Maven 2.1 (there's no such thing)
> but version 2.1 of the jar plugin
> which I already have installed in my maven repository!!!!
>
> More voodoo to try to understand. ;-)
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
7002
days inactive
7002
days old
jboss-development@lists.jboss.org
5 comments
2 participants
participants (2)
-
Adrian -
Scott M Stark