Hi,
what you are trying to do cannot work within one maven execution.
In your case, mvn initialize works because maven-install-plugin doesn't
require dependencies of the project, so the build plan can be executed.
mvn install cannot work, because dependencies are resolved before any
plugin part
It turns out I was wrong. You got the answer to why this happens from
someone else in this thread.
/Anders
On Tue, Mar 5, 2013 at 2:06 PM, Macbeth, Andrew (US SSA)
andrew.macb...@baesystems.com wrote:
Anders,
I included the debug output and pom.xml's in my previous message.
Wondering if
Before Maven starts executing plugins against projects, Maven first has to
construct the build plan.
The build plan needs to take into account the inter-project dependencies,
so that the projects can be built in the correct sequence.
So if A - B - C, Maven needs to ensure that C is built before
Thanks to all. Simply knowing that this can't work will help me from beating my
head against the wall trying to make it work.
Very much appreciate the explanations.
Andy
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, March 05, 2013
This is not a problem report, but more an information request.
The scm section in my poms never had a tag section.
I just noticed the release plugin (2.3.2) is adding tag to the scm
section of poms during a release:
scm
...
tagHEADtag
scm
The maven docs say this is the default value by
