On 12 Mar 07, at 2:23 AM 12 Mar 07, Kenney Westerhof wrote:
I think we should require the hiding of p-u 1.4.1 in 2.0.6, or let
it still use 1.1. All previous releases (except for beta releases)
use p-u 1.1. I'm afraid exposing p-u 1.4.1 will break more
than just surefire.
I certainly do the hiding, it's not that big of a deal. I think
rolling back now would break other things and we should be free to
use internally what we need and not have that affect its use elsewhere.
Jason.
Jason van Zyl wrote:
On 12 Mar 07, at 12:22 AM 12 Mar 07, Jerome Lacoste wrote:
On 3/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 11 Mar 07, at 9:48 PM 11 Mar 07, Jerome Lacoste wrote:
[...]
Some days ago we talked about trying to not expose the internal
maven
> plexus-utils to the projects it builds.
>
I have done work on trunk and am working with Torsten to finish the
minijar plugin to hide internal dependencies.
> I see that 2.0.6 will have plexus-utils 1.4 (
> http://jira.codehaus.org/browse/MNG-2828) but will the root issue
> be also
> fixed in 2.0.6 ?
It's actually 1.4.1, but it's really the surefire plugin which is
going to cause grief.
Do you mean that hiding the dependencies will break the surefire
plugin ?
No, hiding the dependencies means that usage of p-u would be
scrambled inside the Maven core, and plugins would be free to load
whatever version of p-u they wanted to.
Jason.
I have several plugins that would benefit from using the latest
plexus-utils
and if I got it right, they won't be able to do it until this is
fixed.
J
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
