Our primary focus with 3.0 is backward compatibility and stability. We
have spent an enormous amount of time adding tests and making it so
that end users don't have to make any changes.
The other major change was the way the system embeds. That said
everything for integrators will be in flux until we reach a beta
state. So anything you might have been using during alphas has no
guarantee of being there until the betas stabilize. The
ContainerCustomizer for example is not there anymore. We use the
container directly now, and we use the components directly instead of
using the embedder. Embedding documentation and the apis will
stabilize with the betas. There's no ETA, no guarantees and the only
thing to look at right now is the M2Eclipse codebase. Number one
priority is the CLI and backward compatibility.
On 2009-10-07, at 7:36 AM, [email protected] wrote:
Hi,
I'm doing some research on conflict resolving between Java
components. Now I would like to use my own ConflictResolver during a
Maven run. I'm using Maven Embedder in my application and tried
several ways on how to manipulate the Plexus container to use my own
ConflictResolver. I used the "customize" interface that is meant to
manipulate the container on Embedder startup but an "addComponent"
did not work as expected.
Can someone give me a hint how to do that? I know the Wiki page at
[1] that suggests to manipulate the POM to configure the
ConflictResolver that should be used. But I'm working with Embedder
and I can not change the POMs. I would like to inject my
ConflictResolver as the default resolver when the Embedder is
created. But how?
Thank you,
Fabian
[1] http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
