remember: we'll have to explain users why we did a breaking change
I don't think such an explanation will be possible for users: for long-dev
like me, it's hardly a valid explanation
Can you explain in plain english some cases, please?
And remember we'll require to prepare a list of known
Am 12/20/16 um 10:28 schrieb Michael Osipov:
>> Am 12/19/16 um 15:56 schrieb Michael Osipov:
>>> [DEBUG]net.sf.michael-o.dirctxsrc:dircontextsource:jar:1.3:compile
>>> [DEBUG] org.slf4j:slf4j-simple:jar:1.7.21:runtime (scope managed from
>>> test by
Am 12/20/16 um 08:06 schrieb Hervé BOUTEMY:
> I must confess I never investigated why this "provided" recipe worked: it
> just
> looked nice :)
>
> but you didn't answer the important part of the question:
> From a purist point of view, I understand
> From a user point of view, do you have any
Am 2016-12-11 um 19:59 schrieb Dan Tran:
Hi
I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time.
Let me know if you need me to wait
Dan,
you can start with your preperations. I have done my changes.
Michael
Hello Maven developers,
I made a framework which can use Maven repository at runtime.
I had to override DependencyCollector so it can change artifact dependencies
dynamically.
I was wondering if this modification could be integrated to Maven
Also the framework can associate one classloader per
> Am 12/19/16 um 15:56 schrieb Michael Osipov:
> > [DEBUG]net.sf.michael-o.dirctxsrc:dircontextsource:jar:1.3:compile
> > [DEBUG] org.slf4j:slf4j-simple:jar:1.7.21:runtime (scope managed from
> > test by com.company.project:project-parent:0.11-SNAPSHOT)
>
>
