Assembly plugin 2.2-beta-2 shows odd behavior regarding dependencies inclusion
Hello, we face a rather advanced requirement regarding creation of various assemblies in a multimodule project. What we are trying to achieve is as follows. Assume there is a root project P consisting of multiple module projects M1, ..., Mn (hierarchy depth max. 1). From the root POM we create various assemblies in the usual way (one descriptor file for each assembly; not attached to the build lifecycle). That works fine. Now, we also need to create yet another assembly just for one module, say M1. Whatever we have tried so far, we were not able to get it working without the overall build to fail, or at least without achieving exactly what we need. The only configuration where the overall build did not fail is to put the assembly descriptor for M1 to the root POM together with the other ones. Unfortunately, the file name of the packaged assembly will then always start with the artifactId and version number of P, rather than the artifactId and version of M1. Whenever we put the maven assembly plugin in the POM of M1, in addition to the assembly plugin in the root POM, the build does fail with various error messages. We tried both to attach execution to the package lifecycle, or to use standalone execution using assembly:assembly on the command line. We also tried almost every combination of single, attached, and assembly mojo when execution is attached to the package build lifecycle. All without success. The question is whether this constellation was taken into account at design time of the assembly plugin, thus, whether it is possible at all. If not, should I file a feature request. BTW, we use assembly plugin 2.2-beta-3 and Maven 2.0.9. Regards, Thorsten -- View this message in context: http://www.nabble.com/Assembly-plugin-2.2-beta-2-shows-odd-behavior-regarding-dependencies-inclusion-tp21602014p21602014.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Assembly plugin 2.2-beta-2 shows odd behavior regarding dependencies inclusion
Sorry, the subject of this posting is false. I used Nabble to post that message and for some strange reason it used a subject from an earlier posting. I re-posted this message with the correct subject. -- Thorsten TM wrote: Hello, we face a rather advanced requirement regarding creation of various assemblies in a multimodule project. What we are trying to achieve is as follows. Assume there is a root project P consisting of multiple module projects M1, ..., Mn (hierarchy depth max. 1). From the root POM we create various assemblies in the usual way (one descriptor file for each assembly; not attached to the build lifecycle). That works fine. Now, we also need to create yet another assembly just for one module, say M1. Whatever we have tried so far, we were not able to get it working without the overall build to fail, or at least without achieving exactly what we need. The only configuration where the overall build did not fail is to put the assembly descriptor for M1 to the root POM together with the other ones. Unfortunately, the file name of the packaged assembly will then always start with the artifactId and version number of P, rather than the artifactId and version of M1. Whenever we put the maven assembly plugin in the POM of M1, in addition to the assembly plugin in the root POM, the build does fail with various error messages. We tried both to attach execution to the package lifecycle, or to use standalone execution using assembly:assembly on the command line. We also tried almost every combination of single, attached, and assembly mojo when execution is attached to the package build lifecycle. All without success. The question is whether this constellation was taken into account at design time of the assembly plugin, thus, whether it is possible at all. If not, should I file a feature request. BTW, we use assembly plugin 2.2-beta-3 and Maven 2.0.9. Regards, Thorsten -- View this message in context: http://www.nabble.com/Assembly-plugin-2.2-beta-2-shows-odd-behavior-regarding-dependencies-inclusion-tp21602014p21602133.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembly plugin 2.2-beta-2 shows odd behavior regarding dependencies inclusion
Hello,
today I tried to upgrade the Maven assembly plugin from 2.2-beta-1 to
2.2-beta-2. However, I noticed that for my project which consists of
multiple modules the resulting binary assembly now contains dependency JAR
files multiple times. The assembly descriptor contains the following excerpt
(with changed module names):
moduleSets
moduleSet
includes
include${pom.groupId}:a/include
include${pom.groupId}:b/include
include${pom.groupId}:c/include
/includes
binaries
includeDependenciestrue/includeDependencies
unpackfalse/unpack
outputDirectory/lib/outputDirectory
/binaries
/moduleSet
/moduleSets
The projects a, b, c have several dependencies, whereby some of those
dependencies refer to identical artifacts (derived from a parent POM), e.g.,
commons-logging. The resulting ZIP and TAR.GZ assembly files then contain
those dependencies multiple times (in the lib folder) with equal names! Im
not sure if this is a bug or a feature and I might have missed something.
When I change the version back to 2.2-beta-1 it works as expected, i.e., all
files exist only once.
Any hints?
Thanks,
Thorsten
--
View this message in context:
http://www.nabble.com/Assembly-plugin-2.2-beta-2-shows-odd-behavior-regarding-dependencies-inclusion-tp16720569s177p16720569.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
