On 01/12/2008, at 4:58 AM, jallen wrote:
Should this be detected by mvn and prevented?
Yes (I'm surprised it isn't, I thought plugin dependencies were in the
reactor ordering).
So bottom line question, what is the specified behaviour for what
I'm doing?
Does maven try and do anything clever replacing artifacts in the
build with
ones that have just been created in the reactor?
Yes, it does, and current versions are known to not get it right all
the time which might explain what you are seeing.
Does anyone have any
suggestions on how best to sort this chicken and egg issue? My corp
pom also
sets up defaults for scm, distrMgt and a bunch of other stuff. I
suppose I
could make the config artifact completely stand-alone, duplicating
the corp
pom static stuff in its pom so its no longer involved in the reactor.
Is your corp pom also in the reactor? Usually, it would be outside.
The structure should look like this in terms of Maven inheritance:
. corp-pom (shared settings)
+-- corp-rules-artifact (PMD, checkstyle rules)
\-- corp-project-pom (includes the plugin definition)
\-- your-project (uses the rules definition)
All 4 of these projects would have separate SCM trunks and be released
separately (you could put the rules and the project pom together since
they probably change at the same time though).
Thoughts, comments and admonishments welcome,
:)
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
