Hi,
Is there anyway to control or influence the reactor build order?
If the parent-as-dependent feature is intentional (and not a bug) then
perhaps the parent element could have an attribute or child element
that allowed you to specify whether you wished the parent to be built
first or last.
Am back from a long weekend and have isolated the difference between
what works and what doesn't. My child pom.xml files specify the parent
element so that it pulls information including version number from the
parent pom.xml.
I created a project exactly as per your (Tim's) project structure
Hi,
just did a quick test. The difference is, that wih the parent element
present, the build order of the projects change:
Without Parent:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - my-test-group:suba:jar:1.0-SNAPSHOT
[INFO] Unnamed -
I have decided that I may not be able to get this working until Maven
2.1 is released. I think the problem may be that I cannot attach the
assembly to the life-cycle for a parent project that has no artifacts or
a parent that has children with no assembly.
Instead I have worked around the
It's working for me with this test project:
.
|-- pom.xml
|-- src
| `-- main
| `-- assembly
| `-- assembly.xml
|-- suba
| |-- pom.xml
| `-- src
| `-- main
| `-- java
| `-- TestClass.java
`-- subb
|-- pom.xml
Thanks,
I will try this and post back what I find.
If it's working for you then I suspect I must have configured something
wrong somewhere in my one of my poms.
Cheers,
Evan.
Tim Kettler wrote:
It's working for me with this test project:
.
|-- pom.xml
|-- src
| `-- main
|
Tim,
what version of the assembly plugin are you using? I have a very similar
setup to Evan's, and I'm getting the same does not have an artifact with a
file error when binding to package and running the single goal. I'm using
the latest released assembly, 2.2-beta-1.
Kalle
On 9/5/07, Evan
Hi,
maven-2.0.7, assembly-plugin-2.2-beta-1, install-plugin:2.2
I tried this with a clean local repository (-Dmaven.repo.local=...), to
ensure only released plugins are used in the build.
Have you tried the test project? There were a couple of posts from
people having this kind of problem
Hi,
I am having trouble deploying a 'tar.gz' assembly of a parent project
using the deploy goal.
The parent project has a number of child module projects.
Essentially I am running the following on the parent project:
mvn package assembly:assembly deploy
and what is happening is that all
Hi,
Evan Toliopoulos schrieb:
Hi,
I am having trouble deploying a 'tar.gz' assembly of a parent project
using the deploy goal.
The parent project has a number of child module projects.
Essentially I am running the following on the parent project:
mvn package assembly:assembly deploy
Hi,
I am having trouble deploying a 'tar.gz' assembly of a parent project using the
deploy goal.
The parent project has a number of child module projects.
Essentially I am running the following on the parent project:
mvn package assembly:assembly deploy
and what is happening is that all
Thanks,
Though it still is not working. I get the following error:
Failed to create assembly: Artifact:
com.emagineinternational:sms-transceiver-mq:jar:6.5.1-SNAPSHOT (included
by module) does not have an artifact with a file. Please ensure the
package phase is run before the assembly is
12 matches
Mail list logo
