Re: [jboss-dev] Common build broken again?
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