Ralph Goers wrote:
Ralph Goers wrote:
Ralph Goers wrote:
Shane Isbell wrote:
I've been refactoring more of the project builder code and
encountered a
rule that if a dependencyManagement/dependencies/dependency element
has
type=pom and scope=import, the dependency management section of that
dependency should be imported into the containing pom model. This is a
one-off rule that doesn't easily fit into the new project builder
which
keeps all pom specific rules in the PomClassicTransformer class.
This type
of behavior could be handled instead by mixins/imports within the
latest
maven-shared-model code. The way this would work is that you could
use a
mavenImport tag in the dependencyManagement section of the pom and
then the
framework would handle importing the xml fragment containing the
dependency
info. Thoughts?
Shane
I'm not sure I completely follow. Can you provide an example?
Shane, can you please provide an example of the way it would work?
I'm still waiting for an example. I'd really like to understand what
you are talking about.
Pinging one more time. I'd really like to understand this.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
