Hello,
In a multi-module project, I am attempting to provide the parent pom
with an assembly descriptor which will pick up the artifacts from some
of its children modules and throw them in a folder. I'm doing this by
closely following the instructions given here:
On Thu, Sep 2, 2010 at 1:26 PM, Pulkit Singhal pulkitsing...@gmail.com wrote:
In a multi-module project, I am attempting to provide the parent pom
with an assembly descriptor which will pick up the artifacts from some
of its children modules
This works best if you put the assembly in its own
Do you mean structuring it like so:
parent-maven-project
|__childA-maven-project
|__childB-maven-project
|__childC-maven-project
|__fake-assembly-project
Is that the best-practice or the practical-practice?
I ask because it feels a bit odd to have a parent for modules and then
not use it for
Best-practice.
Here's one reason:
http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries
/Anders
On Thu, Sep 2, 2010 at 20:54, Pulkit Singhal pulkitsing...@gmail.comwrote:
Do you mean structuring it like so:
parent-maven-project
|__childA-maven-project
On Thu, Sep 2, 2010 at 2:54 PM, Pulkit Singhal pulkitsing...@gmail.com wrote:
Do you mean structuring it like so:
parent-maven-project
|__childA-maven-project
|__childB-maven-project
|__childC-maven-project
|__fake-assembly-project
Is that the best-practice or the practical-practice?
I
Thank You Anders Wendy, that was a very educational link.
But by moving the product assembler from the parent to a child
project, I've now run into a problem because i also have some of the
children of the parent pom building some packages using assemblers ...
their assembled stuff is not
On Thu, Sep 2, 2010 at 4:26 PM, Pulkit Singhal pulkitsing...@gmail.com wrote:
Thank You Anders Wendy, that was a very educational link.
But by moving the product assembler from the parent to a child
project, I've now run into a problem because i also have some of the
children of the parent
The sub-module is using the following goal for the assembler:
execution
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
But I think perhaps my artifact is being installed locally
(/.m2/repository) and then for some
On 02/09/2010 4:26 PM, Pulkit Singhal wrote:
Thank You Anders Wendy, that was a very educational link.
But by moving the product assembler from the parent to a child
project, I've now run into a problem because i also have some of the
children of the parent pom building some packages using
Yup using fileSets tag rather than dependencySets worked.
I simply don't know why given the following structure:
parent-pom.xml
|_artifact-generating-child-pom.xml
|_assembly-based-artifact-generating-child-pom.xml
|_assembly-based-parent-product-packaging-delegate-pom.xml
The
On Thu, Sep 2, 2010 at 4:59 PM, Pulkit Singhal pulkitsing...@gmail.com wrote:
fileSet
directory../artifact-generating-child/target/directory
...
directory../assembly-based-artifact-generating-child/target/directory
Bad idea. Maven modules are intended to stand
Well commands you say ... hmm ... just doing: mvn clean install
and since that assembly:single goal should tie me into the maven
lifecycle, I suppose I felt this command was good enough?
In addition, in the .m2 repo I see exactly:
./m2/repository/parent/artifact-generating-child/artifact-xx.ABC
If someone on the list doesn't mind, and can guide me ... I would like
to put up an example w/o any of my mis-deeds ofcourse on the site that
hosts this one:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html
How can I do that?
On Thu,
On Thu, Sep 2, 2010 at 5:58 PM, Pulkit Singhal pulkitsing...@gmail.com wrote:
If someone on the list doesn't mind, and can guide me ... I would like
to put up an example w/o any of my mis-deeds ofcourse on the site that
hosts this one:
14 matches
Mail list logo
