I have spent quite a lot of time determining that plugin dependency
definitions seem to be per plugin within a build (maven 2.0.5).
This creates some very interesting "features" in hierarchical builds,
where starting the build at different levels can cause
different definitions to be active.
The following scenario causes my troubles:
maven-artifact-ant plugin-definition A needs a dependency to lib X to
run properly.
maven-artifact-ant plugin-definition B cannot have a dependency to lib X
to run properly.
These scenarios are everyday in test-code and web-test code. Most
selenium users will know this...
Is this a bug? Anyone have any good workarounds? Should I post this to
Jira ?
The enclosed zip file contains a 3-pom example. Verify that the build
works initially, then change the order of the two module includes in the
top-level pom and watch the fireworks ;)
Regards,
Kristian Rosenvold,
Zenior AS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
