I don't think I'll be making any byte for byte exactly guarantees but
as we progress I am going to try and ensure backward compatibility
insofar as behavior. Plugins will work the same apart from plugins
that use components from maven-artifact. We'll be using Mercury for
that and for any plugins here that are here will be ported and
anything popular like the Jetty plugin. People who have implemented
their own plugins using the artifact components will need to make the
same changes we will here.
But I build 5-6 projects all the time with Maven 3.x without any
change to the underlying plugins. There are however going to be
changes to the plugin api that people will be able to take advantage
of if they want their plugins to work well in incremental environments
like Eclipse. But that will be optional for those that care. Igor has
made changes to the plexus, modello, plugin api, and resources plugins
to work in an incremental mode inside m2e to provide near
instantaneous execution.
As we approach publicly consumable alphas I'll have a lot more to say.
On 11-Feb-09, at 10:01 PM, Paul Benedict wrote:
Does any tool exist that can build a project in Maven 2 and Maven 3
and then compare the binaries to see if they are equal? Assuming v3 is
fully backwards compatible with v2, I hope there would be only
superficial differences.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
