RE: maven-assembly-plugin: doesn't work from a reactor build
On Tue, April 24, 2007 4:09 pm, Jörg Schaible wrote: > use goal "single" instead of "attached". This also seems to make no difference. One thing I have noticed is that a small part of the assembly is created, with the contents below. It looks like as soon as it's encountered the dependency with a classifier (one of the dependencies has a classifier of "solaris") the assembly silently fails, then continues, resulting in a jar file like below. Note the directory "-solaris" below: Archive: /udd008/app/alchemy/development/mx/trunk/alchemy-measure-assembly/target/alchemy-measure-assembly-4.0.4-SNAPSHOT-jar-with-dependencies.jar LengthDateTimeName -- 0 04-24-07 16:33 META-INF/ 3009 04-24-07 16:33 META-INF/MANIFEST.MF 0 12-12-06 13:04 org/ 0 12-12-06 13:03 org/jboss/ 0 04-24-07 16:33 org/jboss/annotation/ 0 04-24-07 16:33 org/jboss/annotation/security/ 0 04-24-07 16:33 org/jboss/annotation/ejb/ 0 04-24-07 16:33 org/jboss/annotation/ejb/cache/ 0 04-24-07 16:33 org/jboss/annotation/ejb/cache/simple/ 0 04-24-07 16:33 org/jboss/annotation/ejb/cache/tree/ 0 04-24-07 16:33 org/jboss/annotation/internal/ 0 04-03-07 15:56 quant/ 0 04-24-07 16:33 -solaris/ 0 04-03-07 15:56 -solaris/quant/ 0 04-03-07 15:56 -solaris/META-INF/ 1273 12-12-06 13:03 org/jboss/annotation/security/SecurityDomainImpl.class 440 12-12-06 13:03 org/jboss/annotation/security/RunAsPrincipal.class 668 12-12-06 13:03 org/jboss/annotation/security/RunAsPrincipalImpl.class 507 12-12-06 13:03 org/jboss/annotation/security/SecurityDomain.class 734 12-12-06 13:03 org/jboss/annotation/ejb/LocalBindingImpl.class 445 12-12-06 13:03 org/jboss/annotation/ejb/LocalBinding.class 430 12-12-06 13:03 org/jboss/annotation/ejb/Local.class 661 12-12-06 13:03 org/jboss/annotation/ejb/IIOP.class 594 12-12-06 13:03 org/jboss/annotation/ejb/ExcludeDefaultInterceptorsImpl.class 586 12-12-06 13:03 org/jboss/annotation/ejb/ExcludeClassInterceptorsImpl.class 1038 12-12-06 13:03 org/jboss/annotation/ejb/Durability.class 1135 12-12-06 13:03 org/jboss/annotation/ejb/DependsImpl.class 449 12-12-06 13:03 org/jboss/annotation/ejb/Depends.class 1062 12-12-06 13:03 org/jboss/annotation/ejb/DeliveryMode.class 1818 12-12-06 13:03 org/jboss/annotation/ejb/DefaultActivationSpecsImpl.class 470 12-12-06 13:03 org/jboss/annotation/ejb/DefaultActivationSpecs.class 555 12-12-06 13:03 org/jboss/annotation/ejb/CurrentMessageImpl.class 419 12-12-06 13:03 org/jboss/annotation/ejb/CurrentMessage.class 2217 12-12-06 13:03 org/jboss/annotation/ejb/ConsumerImpl.class 540 12-12-06 13:03 org/jboss/annotation/ejb/Consumer.class 1464 12-12-06 13:03 org/jboss/annotation/ejb/ClusteredImpl.class 600 12-12-06 13:03 org/jboss/annotation/ejb/Clustered.class 522 12-12-06 13:03 org/jboss/annotation/ejb/cache/simple/CacheConfig.class 1031 12-12-06 13:03 org/jboss/annotation/ejb/cache/simple/CacheConfigImpl.class 455 12-12-06 13:03 org/jboss/annotation/ejb/cache/simple/PersistenceManager.class 911 12-12-06 13:03 org/jboss/annotation/ejb/cache/simple/PersistenceManagerImpl.class 612 12-12-06 13:03 org/jboss/annotation/ejb/cache/tree/CacheConfig.class 1323 12-12-06 13:03 org/jboss/annotation/ejb/cache/tree/CacheConfigImpl.class 422 12-12-06 13:03 org/jboss/annotation/ejb/cache/Cache.class 694 12-12-06 13:03 org/jboss/annotation/ejb/cache/CacheImpl.class 1239 12-12-06 13:03 org/jboss/annotation/ejb/AcknowledgementMode.class 431 12-12-06 13:03 org/jboss/annotation/ejb/AspectDomain.class 739 12-12-06 13:03 org/jboss/annotation/ejb/AspectDomainImpl.class 671 12-12-06 13:03 org/jboss/annotation/ejb/LocalHomeImpl.class 521 12-12-06 13:03 org/jboss/annotation/ejb/LocalImpl.class 476 12-12-06 13:03 org/jboss/annotation/ejb/Management.class 780 12-12-06 13:03 org/jboss/annotation/ejb/ManagementImpl.class 748 12-12-06 13:03 org/jboss/annotation/ejb/MessageProperties.class 2038 12-12-06 13:03 org/jboss/annotation/ejb/MessagePropertiesImpl.class 524 12-12-06 13:03 org/jboss/annotation/ejb/PoolClass.class 1724 12-12-06 13:03 org/jboss/annotation/ejb/PoolClassImpl.class 650 12-12-06 13:03 org/jboss/annotation/ejb/Producer.class 443 12-12-06 13:03 org/jboss/annotation/ejb/Producers.class 667 12-12-06 13:03 org/jboss/annotation/ejb/RemoteBinding.class 2804 12-12-06 13:03 org/jboss/annotation/ejb/RemoteBindingImpl.class 458 12-12-06 13:03 org/jboss/annotation/ejb/RemoteBindings.class 1107 12-12-06 13:03 org/jboss/annotation/ejb/RemoteBindingsImpl.class 675 12-12-06 13:03 org/jboss/
RE: maven-assembly-plugin: doesn't work from a reactor build
Hi Graham, use goal "single" instead of "attached". - Jörg Graham Leggett wrote on Monday, April 23, 2007 4:45 PM: > Hi all, > > I have an assembly linked into the mvn build lifecycle like > below using > the "attached" goal. > > When mvn install is run from the assembly artifact, the > assembly is built > correctly. > > If however mvn install is run from the root pom (ie a reactor build), > the assembly plugin goes through the motions, but the assembly > created is empty. > > Does the "attached" goal work in multi-module / reactor builds? > > > maven-assembly-plugin > 2.2-beta-1 > > > assembly.xml > > > > > make-assembly > package > > attached > > > > > > Regards, > Graham - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-assembly-plugin: doesn't work from a reactor build
On Tue, April 24, 2007 3:07 am, Wayne Fay wrote:
> Are you sure Assembly is finding the assembly.xml you've specified
> during the reactor build? I know paths specified in child pom plugins
> sometimes don't work as expected during reactor builds, etc.
I tried to change the descriptor to add the basedir in front of the path
to the assembly, but it made no difference:
${basedir}/assembly.xml
> As a test, rename the assembly.xml file to .blah and run from child.
> If the assembly plugin "looks" the same as when executed from the
> parent directory, I'd assume this is what's going on.
Tried this as well, renamed the assembly to something else, and got the
following error:
[INFO] Error reading assemblies: Error locating assembly descriptor file:
/udd001/app/alchemy/development/mx/trunk/alchemy-measure-assembly/assembly.xml
/udd001/app/alchemy/development/mx/trunk/alchemy-measure-assembly/assembly.xml
(No such file or directory)
It's definitely picking up the assembly file in both cases.
Regards,
Graham
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-assembly-plugin: doesn't work from a reactor build
Are you sure Assembly is finding the assembly.xml you've specified during the reactor build? I know paths specified in child pom plugins sometimes don't work as expected during reactor builds, etc. As a test, rename the assembly.xml file to .blah and run from child. If the assembly plugin "looks" the same as when executed from the parent directory, I'd assume this is what's going on. Wayne On 4/23/07, Graham Leggett <[EMAIL PROTECTED]> wrote: Hi all, I have an assembly linked into the mvn build lifecycle like below using the "attached" goal. When mvn install is run from the assembly artifact, the assembly is built correctly. If however mvn install is run from the root pom (ie a reactor build), the assembly plugin goes through the motions, but the assembly created is empty. Does the "attached" goal work in multi-module / reactor builds? maven-assembly-plugin 2.2-beta-1 assembly.xml make-assembly package attached Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-assembly-plugin: doesn't work from a reactor build
Hi all, I have an assembly linked into the mvn build lifecycle like below using the "attached" goal. When mvn install is run from the assembly artifact, the assembly is built correctly. If however mvn install is run from the root pom (ie a reactor build), the assembly plugin goes through the motions, but the assembly created is empty. Does the "attached" goal work in multi-module / reactor builds? maven-assembly-plugin 2.2-beta-1 assembly.xml make-assembly package attached Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
