> Right now I'm not opposed to making this change during the 1.x timeline. We
> are upgrading to the Maven 3 way which is in the interest of most our users.
> Quite likely no one will be affected by the small delta above and if so
> there should be a very easy workaround.
I agree that the impact on the public api after replacing old maven
classes should be minimal to none.
> I guess it also opens up the door to solve problems like that we always do a
> maven install.
>
> The other question is how much this would affect our pom publishing, which
> is the more sensitive bit?
I'll try to do a very quick spike, drop maven3 classes instead of
ant-tasks and see if integ tests like it.
Cheers!
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
