Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
If you put your code somewhere for the Mapping, Reader and Writer I will take a
look. I'm working on the shell and polyglot currently so it wouldn't take me
long to get you going.
On Oct 14, 2010, at 4:11 PM, Mike Lenner wrote:
> It seems that overriding MavenCli.createModelProcessor as shown b
I said copy what's in polyglot. I just assumed you would look at delegating
model processor.
You create a Mapping, Reader and Writer. The Mapping is discovered and injected
into Polyglot. Polyglot walks through the Mappings and if a particular mapping
can accept processing the model input the
It seems that overriding MavenCli.createModelProcessor as shown below
is incorrect. That will change the ModelProcessor used by MavenCli to
*locate* the build file, but not the ModelProcessor used by
DefaultModelBuilder to *read* the build file and generate a Model.
So, following Polyglot, it act