You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Arnaud HERITIER <ah...@apache.org> on 2012/10/16 15:18:19 UTC
Release of the dependency plugin 2.6
Hi all,
i would like to release the dependency plugin soon.
There only too old issues not closed attached to the current version (
http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel)
but I suppose they are migrated release after release without any real work
on them.
I'm interested especially by this fix to use it as report (
http://jira.codehaus.org/browse/MDEP-366) and it has the perf improvement
with the plexus-utils upgrade (http://jira.codehaus.org/browse/MDEP-377)
Nobody against it ?
Cheers
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Hervé BOUTEMY <he...@free.fr>.
if maven-dependency-tree[1]'s DependencyGraphBuilder can be used, it gives
you both Maven 2 & 3 compatibility without hard code
Regards,
Hervé
[1] http://maven.apache.org/shared/maven-dependency-tree/
Le lundi 22 octobre 2012 19:09:48 Arnaud Héritier a écrit :
> As discussed on IRC for now I don't see a better solution.
> Someone else has a feedback or some ideas ?
>
> Arnaud
>
> On Mon, Oct 22, 2012 at 6:21 PM, Paul Gier <pg...@redhat.com> wrote:
> > I have now split out the manual purge option into a separate mojo, and
> > added the requiresDependencyResolution annotation to the
> > purge-local-repository mojo. Hopefully, this will allow the dependency
> > resolution to happen more predictably.
> >
> > The advantage of this is that the code is much simpler, and most of the
> > ITs seem to work with Maven 2 and 3. Hopefully, all the active ITs will
> > pass on Jenkins now.
> >
> > However, there are a couple of disadvantages to this approach. One is
> > that the full dependency tree is always resolved before the purge which
> > makes the plugin inefficient for some use-cases. But hopefully, those
> > use-cases can be handled by the manual purge goal instead. The other
> > disadvantage is that the IT which uses a pom with an unresolvable
> > dependency (bad pom) does not work because Maven fails before the plugin
> > has a chance to re-resolve it. This seems like a fairly important use
> > case to me, because one of the reasons for purging might be that you
> > have a bad pom in the local repo. Unfortunately, I'm not able to figure
> > out how to get around this in a reliable way.
> >
> > Eventually, we should probably just break Maven 2 compatibility, and use
> > the Aether API for dependency resolution. Maybe this can be done for
> > version 3.0 of the dependency plugin.
> >
> > On 10/22/2012 08:16 AM, Arnaud Héritier wrote:
> > > I was looking at the issue and don't really understand what's wrong with
> > > what you did.
> > > I think you are facing the *fucking bug/feature* in Maven 3 (from
> > > aether)
> > > that rejects some dependencies that are available in the local
> > > repository
> > > but not in the remote.
> > > This is because you install manually the artifact in the local repo and
> > > thus ather doesn't want it and we cannot bypass this control.
> > > It may explain why ITs are ok with Maven 2 but not Maven 3 on Jenkins.
> > >
> > > Arnaud
> > >
> > > On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier <pg...@redhat.com> wrote:
> > >> Sorry about that, looks like two of them are failing on Jenkins also.
> > >> I'm not sure why I don't see the failures locally, I tested with Maven
> > >> 2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
> > >>
> > >> On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
> > >>> FYI, I will need to release also maven-dependency-analyzer
> > >>> I need to check its status
> > >>> Also 3 ITs added by Paul this WE are failing on my laptop. I will
> > >>> study
> > >>
> > >> if
> > >>
> > >>> I have an environment issue of if this is a problem in ITs or the code
> > >>>
> > >>> cheers
> > >>>
> > >>> On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <aheritier@gmail.com
> > >>>
> > >>> wrote:
> > >>>> no problem, you're doing the harder work :-)
> > >>>> I'll launch the release process today.
> > >>>> I hope to not have too many glitches as I didn't do that for a (too)
> > >>
> > >> long
> > >>
> > >>>> time..
> > >>>>
> > >>>> Arnaud
> > >>>>
> > >>>> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
> > >>>>> Ok, I'm done working on the purge-local-repositories goal for now,
> > >>>>> thanks for waiting for me.
> > >>>>>
> > >>>>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
> > >>>>>> Hi Paul,
> > >>>>>>
> > >>>>>> Yes no problem I can do it tomorrow or this week end.
> > >>>>>> I just would like to have it out before the end of next week
> > >>>>>>
> > >>>>>> Cheers,
> > >>>>>>
> > >>>>>> Arnaud
> > >>>>>>
> > >>>>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com>
> >
> > wrote:
> > >>>>>>> Hi Arnaud,
> > >>>>>>>
> > >>>>>>> Can you hold off one more day? I have a couple of fixes I want to
> > >>
> > >> get
> > >>
> > >>>>>>> in, and I want to do a bit more testing.
> > >>>>>>>
> > >>>>>>> Thanks!
> > >>>>>>>
> > >>>>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
> > >>>>>>>> ok thx.
> > >>>>>>>> I'll do the release tomorrow
> > >>>>>>>>
> > >>>>>>>> Arnaud
> > >>>>>>>>
> > >>>>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
> > >>>>>
> > >>>>> rfscholte@apache.org
> > >>>>>
> > >>>>>>>> wrote:
> > >>>>>>>>> Ok, I'm ready
> > >>>>>>>>>
> > >>>>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
> > >>>>>>>>>
> > >>>>>>>>> aheritier@gmail.com>:
> > >>>>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
> > >>>>>
> > >>>>> rfscholte@apache.org
> > >>>>>
> > >>>>>>>>>>> wrote:
> > >>>>>>>>>> Hi,
> > >>>>>>>>>>
> > >>>>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would
> > >>
> > >> need
> > >>
> > >>>>> to
> > >>>>>
> > >>>>>>>>>>> write an IT with a custom packaging type.
> > >>>>>>>>>>> That would probably take some time, so I'll pick that up for
> >
> > the
> >
> > >>>>> 2.7
> > >>>>>
> > >>>>>>>>>> ok
> > >>>>>>>>>>
> > >>>>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue.
> >
> > It
> >
> > >>>>> has a
> > >>>>>
> > >>>>>>>>>>> good patch, although I think that the useBaseVersion should be
> > >>>>>
> > >>>>> 'true'
> > >>>>>
> > >>>>>>> by
> > >>>>>>>
> > >>>>>>>>>>> default. I can fix that today or tomorrow.
> > >>>>>>>>>>
> > >>>>>>>>>> ok let me know when it will be good on your side.
> > >>>>>>>>>>
> > >>>>>>>>>> thx
> > >>>>>>>>>>
> > >>>>>>>>>>> thanks,
> > >>>>>>>>>>>
> > >>>>>>>>>>> Robert
> > >>>>>>>>>>>
> > >>>>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
> > >>>>>>>>>>> stephen.alan.connolly@gmail.****com
> > >>
> > >> <stephen.alan.connolly@gmail.
> > >>
> > >>>>>>> **com<st...@gmail.com>
> > >>>>>>>
> > >>>>>>>>>>> We should probably close MDEP-124 as WONT FIX given that
> > >>>>>>>>>>> there
> > >>>>>
> > >>>>> seems
> > >>>>>
> > >>>>>>> no
> > >>>>>>>
> > >>>>>>>>>>>> way
> > >>>>>>>>>>>> to fix it... or at least the addition of a configuration
> >
> > element
> >
> > >>>>> to
> > >>>>>
> > >>>>>>>>>>>> allow
> > >>>>>>>>>>>> flagging specific dependencies as used even if they seem not.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> MDPE-166 also seems like it should just display a different
> > >>
> > >> output
> > >>
> > >>>>>>> for
> > >>>>>>>
> > >>>>>>>>>>>> <scope>runtime</scope> namely something like "Unable to
> > >>
> > >> determine
> > >>
> > >>>>>>>>>>>> whether
> > >>>>>>>>>>>> used or unused as scope is runtime"
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I think the above two "solutions" would be quick to implement
> > >>
> > >> and
> > >>
> > >>>>>>> would
> > >>>>>>>
> > >>>>>>>>>>>> close the issues out.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <
> >
> > aheritier@apache.org
> >
> > >>>>>>> wrote:
> > >>>>>>>>>>>> Hi all,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> i would like to release the dependency plugin soon.
> > >>>>>>>>>>>>> There only too old issues not closed attached to the
> >
> > current
> >
> > >>>>>>> version
> > >>>>>>>
> > >>>>>>>>>>>>> (
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
> > >>>>>>>
> > >>>>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
> > >>
> > >> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
> > >>
> > >>>>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
> > >>>>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
> >
> > http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin
> > .system.project%3Aroadmap-panel>
> > >>>>>>>>>>>>> )
> > >>>>>>>>>>>>> but I suppose they are migrated release after release
> > >>>>>>>>>>>>> without
> > >>
> > >> any
> > >>
> > >>>>>>> real
> > >>>>>>>
> > >>>>>>>>>>>>> work
> > >>>>>>>>>>>>> on them.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> I'm interested especially by this fix to use it as report
> > >>>>>>>>>>>>> (
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
> > >>>>>>>
> > >>>>>>> http://jira.codehaus.org/**browse/MDEP-366>
> > >>>>>>>
> > >>>>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
> > >>>>>>>
> > >>>>>>> http://jira.codehaus.org/browse/MDEP-366>
> > >>>>>>>
> > >>>>>>>>>>>>>> )
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> and it has the perf improvement
> > >>>>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
> > >>>>>>>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
> > >>>>>>>
> > >>>>>>> http://jira.codehaus.org/browse/MDEP-377>
> > >>>>>>>
> > >>>>>>>>>>>>>> )
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>> Nobody against it ?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Cheers
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> -----
> > >>>>>>>>>>>>> Arnaud Héritier
> > >>>>>>>>>>>>> http://aheritier.net
> > >>>>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
> > >>>>>>>>>>>>> Twitter/Skype : aheritier
> > >>
> > >> ------------------------------****----------------------------**
> > >>
> > >>>>>>>>>>> --**---------
> > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
> > >>>>>>>>>>> dev-unsubscribe@maven.**apache.org <
> > >>>>>
> > >>>>> dev-unsubscribe@maven.apache.org
> > >>>>>
> > >>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ------------------------------**------------------------------**---------
> >
> > >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
> > >>>>>>>
> > >>>>>>> dev-unsubscribe@maven.apache.org>
> > >>>>>>>
> > >>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> >
> > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>>>
> > >>>>> --------------------------------------------------------------------
> > >>>>> -
> > >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>>
> > >>>> --
> > >>>> -----
> > >>>> Arnaud Héritier
> > >>>> 06-89-76-64-24
> > >>>> http://aheritier.net
> > >>>> Mail/GTalk: aheritier@gmail.com
> > >>>> Twitter/Skype : aheritier
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Hervé BOUTEMY <he...@free.fr>.
Le mercredi 24 octobre 2012 22:50:19 Arnaud Héritier a écrit :
> It is what I supposed few days ago that it was a problem with aether that
> rejected artifacts installed locally without using aether itself.
not exactly
Aether already resolved the artifact before the plugin deleted it and asked to
re-resolve: that's not a classical scenario, Aether tries to resolve an
artifact only once in a session, and that's a Good Thing (TM)
The only problem is that resolveAlways() API should bypass this feature and it
seems it doesn't do
> it is more annoying if resolver.resolveAlways() doesn't work :(
if my explanations are right, we should open a MNG issue and create either an
IT or a UT: I don't have time to work on it for the moment, but if nobody
beats me, I'll keep this on my TODO list
>
> Arnaud
>
> On Wed, Oct 24, 2012 at 7:25 PM, Hervé BOUTEMY <he...@free.fr>wrote:
> > I had a look at the IT output and found this log message
> > [DEBUG] Skipped remote update check for
> > org.apache.maven.its.dependency:purge-
> > local-repository:pom:1.0, already updated during this session.
> >
> > the code causaing this message is in Aether
> >
> > I doubt maven-dependency-tree will do anything about this problem: this
> > seems
> > to be a cache feature of Aether we exceptionnaly don't want
> >
> > IMHO, if we used resolver.resolveAlways() API (like it was done in
> > previous m-
> > dependency-p version), this cache should be avoided but I tried and it
> > didn't
> > change anything
> > but this time, this would be a Maven core bug :)
> >
> > WDYT?
> >
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 24 octobre 2012 08:56:32 Paul Gier a écrit :
> > > Hi Arnaud,
> > >
> > > I should have some time today to try out the shared dependency tree API,
> > > if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
> > > I can do since this seems to be a regression in 3.0.4. At that point I
> > > will just configure the failing ITs to be skipped for 3.0.4.
> > >
> > > Jenkins also confirmed what I'm seeing locally, that all the ITs pass
> > > with 3.0.3:
> > > https://builds.apache.org/job/maven-plugins-ITs-m3.0.3/
> > >
> > > All the dependency plugin ITs pass, however, the job shows failure
> > > because some of the invoker plugin its are failing in 3.0.3.
> > >
> > > On 10/24/2012 08:28 AM, Arnaud Héritier wrote:
> > > > ok. thanks
> > > > I'll launch the release process tonight.
> > > >
> > > > On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies
> >
> > <bi...@gmail.com>wrote:
> > > >> I reran the build with a clean local repo and it's good. So I
> > > >> withdraw
> > > >> my complaint, go right ahead.
> > > >>
> > > >> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <aheritier@gmail.com
> > > >>
> > > >> wrote:
> > > >>> Strange your issue with the report.
> > > >>> I don't have it on my side.
> >
> > > >>> Example :
> > https://projects.exoplatform.org/forum/forum-component/forum-component-co
> >
> > > >> mmon/dependency-analysis.html>>
> > > >>
> > > >>> I need to investigate more but it won't be before tonight
> > > >>>
> > > >>>
> > > >>> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <
> >
> > bimargulies@gmail.com
> >
> > > >>> wrote:
> > > >>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
> > > >>
> > > >> bimargulies@gmail.com>
> > > >>
> > > >>>> wrote:
> > > >>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <
> >
> > aheritier@gmail.com
> >
> > > >>>> wrote:
> > > >>>>>> Ok if we are all agree I'll process the release this evening.
> > > >>>>>> Thanks for your help guys
> > > >>>>>
> > > >>>>> I am -1 to a release which does not work, at all, on Maven 3.0.4.
> > > >>>>> I
> > > >>>>> tested the 'report' mojo last night with the current snapshot and
> >
> > it
> >
> > > >>>>> died with the same wierd classworlds error that the ITs die with.
> >
> > I'm
> >
> > > >>>>> willing to help fix this up, but I;m not following the logic of a
> > > >>>>> release. Feel free to explain why I'm confused.
> > > >>>>
> > > >>>> I'll do more diagnosis later today.
> > > >>>>
> > > >>>>>> Arnaud
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
> > > >>
> > > >> herve.boutemy@free.fr
> > > >>
> > > >>>>> wrote:
> > > >>>>>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> > > >>>>>>>> I did some more testing, and the tests only seem to fail using
> > > >>
> > > >> Maven
> > > >>
> > > >>>>>>>> 3.0.4 for me. I was testing locally with Maven 3.0.3
> >
> > previously.
> >
> > > >>>> For
> > > >>>>
> > > >>>>>>>> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
> > > >>
> > > >> If
> > > >>
> > > >>>> you
> > > >>>>
> > > >>>>>>>> want to release this week it's probably ok to release even with
> > > >>
> > > >> these
> > > >>
> > > >>>>>>>> failures because the previous release didn't work at all with
> > > >>
> > > >> Maven
> > > >>
> > > >>>> 3.
> > > >>>>
> > > >>>>>>>> We just didn't have ITs to catch it. We could set the invoker
> > > >>
> > > >> not to
> > > >>
> > > >>>>>>>> execute those for Maven 3, and maybe put a note in the docs,
> > > >>>>>>>> and
> > > >>>>
> > > >>>> find a
> > > >>>>
> > > >>>>>>>> better fix for a 2.6.1 release.
> > > >>>>>>>
> > > >>>>>>> +1
> > > >>>>>>>
> > > >>>>>>> yes, this is not a regression but better ITs
> > > >>>>>>>
> > > >>>>>>> Regards,
> > > >>>>>>>
> > > >>>>>>> Hervé
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >>
> > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> -----
> > > >>>>>> Arnaud Héritier
> > > >>>>>> 06-89-76-64-24
> > > >>>>>> http://aheritier.net
> > > >>>>>> Mail/GTalk: aheritier@gmail.com
> > > >>>>>> Twitter/Skype : aheritier
> >
> > ---------------------------------------------------------------------
> >
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >>>> For additional commands, e-mail: dev-help@maven.apache.org
> > > >>>
> > > >>> --
> > > >>> -----
> > > >>> Arnaud Héritier
> > > >>> 06-89-76-64-24
> > > >>> http://aheritier.net
> > > >>> Mail/GTalk: aheritier@gmail.com
> > > >>> Twitter/Skype : aheritier
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >> For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Anders Hammar <an...@hammar.net>.
As long as the failing ITs have corresponding JIRAs I think this is good.
/Anders
On Thu, Oct 25, 2012 at 7:15 AM, Paul Gier <pg...@redhat.com> wrote:
> You're right, the maven dependency tree API ran into the same issue.
> Since using the plugin annotation for automatic resolution didn't make
> the problem any better (and made it worse in some cases), I switched the
> plugin back to resolving dependencies inside the plugin execution, and
> merged back the manual purge option. Hopefully this is ok with everyone.
>
> This definitely seems like a bug in Maven 3.0.4 behaviour not allowing
> forced resolution with resolver.resolveAlways(). I set the invoker
> plugin to skip the failing ITs for the relevant versions of Maven. So
> here is the status of the ITs:
>
> Maven 2.0.x and 2.2.1 - 6 of 7 are passing, only the broken pom use case
> is failing, which is kind of an edge case anyway.
>
> Maven 3.0.x (not 3.0.4) - All 7 ITs are passing
>
> Maven 3.0.4 - 4 of 7 are passing. The three that are failing all
> involve resolving, purging, and then re-resolving, so they are affected
> by the same bug.
>
> IMO, this is ok for a release considering that this goal in the previous
> version of the dependency plugin didn't really work with Maven 3 at all
> because it couldn't find any remotely downloaded dependencies in the
> local repo (http://jira.codehaus.org/browse/MDEP-383).
>
> On 10/24/2012 12:25 PM, Hervé BOUTEMY wrote:
>> I had a look at the IT output and found this log message
>> [DEBUG] Skipped remote update check for org.apache.maven.its.dependency:purge-
>> local-repository:pom:1.0, already updated during this session.
>>
>> the code causaing this message is in Aether
>>
>> I doubt maven-dependency-tree will do anything about this problem: this seems
>> to be a cache feature of Aether we exceptionnaly don't want
>>
>> IMHO, if we used resolver.resolveAlways() API (like it was done in previous m-
>> dependency-p version), this cache should be avoided but I tried and it didn't
>> change anything
>> but this time, this would be a Maven core bug :)
>>
>> WDYT?
>>
>> Regards,
>>
>> Hervé
>>
>> Le mercredi 24 octobre 2012 08:56:32 Paul Gier a écrit :
>>> Hi Arnaud,
>>>
>>> I should have some time today to try out the shared dependency tree API,
>>> if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
>>> I can do since this seems to be a regression in 3.0.4. At that point I
>>> will just configure the failing ITs to be skipped for 3.0.4.
>>>
>>> Jenkins also confirmed what I'm seeing locally, that all the ITs pass
>>> with 3.0.3:
>>> https://builds.apache.org/job/maven-plugins-ITs-m3.0.3/
>>>
>>> All the dependency plugin ITs pass, however, the job shows failure
>>> because some of the invoker plugin its are failing in 3.0.3.
>>>
>>> On 10/24/2012 08:28 AM, Arnaud Héritier wrote:
>>>> ok. thanks
>>>> I'll launch the release process tonight.
>>>>
>>>> On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies
>> <bi...@gmail.com>wrote:
>>>>> I reran the build with a clean local repo and it's good. So I withdraw
>>>>> my complaint, go right ahead.
>>>>>
>>>>> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <ah...@gmail.com>
>>>>>
>>>>> wrote:
>>>>>> Strange your issue with the report.
>>>>>> I don't have it on my side.
>>>>>
>>>>>> Example :
>>>>> https://projects.exoplatform.org/forum/forum-component/forum-component-co
>>>>> mmon/dependency-analysis.html>>
>>>>>> I need to investigate more but it won't be before tonight
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <bimargulies@gmail.com
>>>>>>
>>>>>> wrote:
>>>>>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
>>>>>
>>>>> bimargulies@gmail.com>
>>>>>
>>>>>>> wrote:
>>>>>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <aheritier@gmail.com
>>>>>>>
>>>>>>> wrote:
>>>>>>>>> Ok if we are all agree I'll process the release this evening.
>>>>>>>>> Thanks for your help guys
>>>>>>>>
>>>>>>>> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
>>>>>>>> tested the 'report' mojo last night with the current snapshot and it
>>>>>>>> died with the same wierd classworlds error that the ITs die with. I'm
>>>>>>>> willing to help fix this up, but I;m not following the logic of a
>>>>>>>> release. Feel free to explain why I'm confused.
>>>>>>>
>>>>>>> I'll do more diagnosis later today.
>>>>>>>
>>>>>>>>> Arnaud
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
>>>>>
>>>>> herve.boutemy@free.fr
>>>>>
>>>>>>>> wrote:
>>>>>>>>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
>>>>>>>>>>> I did some more testing, and the tests only seem to fail using
>>>>>
>>>>> Maven
>>>>>
>>>>>>>>>>> 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
>>>>>>>
>>>>>>> For
>>>>>>>
>>>>>>>>>>> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
>>>>>
>>>>> If
>>>>>
>>>>>>> you
>>>>>>>
>>>>>>>>>>> want to release this week it's probably ok to release even with
>>>>>
>>>>> these
>>>>>
>>>>>>>>>>> failures because the previous release didn't work at all with
>>>>>
>>>>> Maven
>>>>>
>>>>>>> 3.
>>>>>>>
>>>>>>>>>>> We just didn't have ITs to catch it. We could set the invoker
>>>>>
>>>>> not to
>>>>>
>>>>>>>>>>> execute those for Maven 3, and maybe put a note in the docs, and
>>>>>>>
>>>>>>> find a
>>>>>>>
>>>>>>>>>>> better fix for a 2.6.1 release.
>>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> yes, this is not a regression but better ITs
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Hervé
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> -----
>>>>>>>>> Arnaud Héritier
>>>>>>>>> 06-89-76-64-24
>>>>>>>>> http://aheritier.net
>>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>> --
>>>>>> -----
>>>>>> Arnaud Héritier
>>>>>> 06-89-76-64-24
>>>>>> http://aheritier.net
>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>> Twitter/Skype : aheritier
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
You're right, the maven dependency tree API ran into the same issue.
Since using the plugin annotation for automatic resolution didn't make
the problem any better (and made it worse in some cases), I switched the
plugin back to resolving dependencies inside the plugin execution, and
merged back the manual purge option. Hopefully this is ok with everyone.
This definitely seems like a bug in Maven 3.0.4 behaviour not allowing
forced resolution with resolver.resolveAlways(). I set the invoker
plugin to skip the failing ITs for the relevant versions of Maven. So
here is the status of the ITs:
Maven 2.0.x and 2.2.1 - 6 of 7 are passing, only the broken pom use case
is failing, which is kind of an edge case anyway.
Maven 3.0.x (not 3.0.4) - All 7 ITs are passing
Maven 3.0.4 - 4 of 7 are passing. The three that are failing all
involve resolving, purging, and then re-resolving, so they are affected
by the same bug.
IMO, this is ok for a release considering that this goal in the previous
version of the dependency plugin didn't really work with Maven 3 at all
because it couldn't find any remotely downloaded dependencies in the
local repo (http://jira.codehaus.org/browse/MDEP-383).
On 10/24/2012 12:25 PM, Hervé BOUTEMY wrote:
> I had a look at the IT output and found this log message
> [DEBUG] Skipped remote update check for org.apache.maven.its.dependency:purge-
> local-repository:pom:1.0, already updated during this session.
>
> the code causaing this message is in Aether
>
> I doubt maven-dependency-tree will do anything about this problem: this seems
> to be a cache feature of Aether we exceptionnaly don't want
>
> IMHO, if we used resolver.resolveAlways() API (like it was done in previous m-
> dependency-p version), this cache should be avoided but I tried and it didn't
> change anything
> but this time, this would be a Maven core bug :)
>
> WDYT?
>
> Regards,
>
> Hervé
>
> Le mercredi 24 octobre 2012 08:56:32 Paul Gier a écrit :
>> Hi Arnaud,
>>
>> I should have some time today to try out the shared dependency tree API,
>> if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
>> I can do since this seems to be a regression in 3.0.4. At that point I
>> will just configure the failing ITs to be skipped for 3.0.4.
>>
>> Jenkins also confirmed what I'm seeing locally, that all the ITs pass
>> with 3.0.3:
>> https://builds.apache.org/job/maven-plugins-ITs-m3.0.3/
>>
>> All the dependency plugin ITs pass, however, the job shows failure
>> because some of the invoker plugin its are failing in 3.0.3.
>>
>> On 10/24/2012 08:28 AM, Arnaud Héritier wrote:
>>> ok. thanks
>>> I'll launch the release process tonight.
>>>
>>> On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies
> <bi...@gmail.com>wrote:
>>>> I reran the build with a clean local repo and it's good. So I withdraw
>>>> my complaint, go right ahead.
>>>>
>>>> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <ah...@gmail.com>
>>>>
>>>> wrote:
>>>>> Strange your issue with the report.
>>>>> I don't have it on my side.
>>>>
>>>>> Example :
>>>> https://projects.exoplatform.org/forum/forum-component/forum-component-co
>>>> mmon/dependency-analysis.html>>
>>>>> I need to investigate more but it won't be before tonight
>>>>>
>>>>>
>>>>> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <bimargulies@gmail.com
>>>>>
>>>>> wrote:
>>>>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
>>>>
>>>> bimargulies@gmail.com>
>>>>
>>>>>> wrote:
>>>>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <aheritier@gmail.com
>>>>>>
>>>>>> wrote:
>>>>>>>> Ok if we are all agree I'll process the release this evening.
>>>>>>>> Thanks for your help guys
>>>>>>>
>>>>>>> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
>>>>>>> tested the 'report' mojo last night with the current snapshot and it
>>>>>>> died with the same wierd classworlds error that the ITs die with. I'm
>>>>>>> willing to help fix this up, but I;m not following the logic of a
>>>>>>> release. Feel free to explain why I'm confused.
>>>>>>
>>>>>> I'll do more diagnosis later today.
>>>>>>
>>>>>>>> Arnaud
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
>>>>
>>>> herve.boutemy@free.fr
>>>>
>>>>>>> wrote:
>>>>>>>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
>>>>>>>>>> I did some more testing, and the tests only seem to fail using
>>>>
>>>> Maven
>>>>
>>>>>>>>>> 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
>>>>>>
>>>>>> For
>>>>>>
>>>>>>>>>> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
>>>>
>>>> If
>>>>
>>>>>> you
>>>>>>
>>>>>>>>>> want to release this week it's probably ok to release even with
>>>>
>>>> these
>>>>
>>>>>>>>>> failures because the previous release didn't work at all with
>>>>
>>>> Maven
>>>>
>>>>>> 3.
>>>>>>
>>>>>>>>>> We just didn't have ITs to catch it. We could set the invoker
>>>>
>>>> not to
>>>>
>>>>>>>>>> execute those for Maven 3, and maybe put a note in the docs, and
>>>>>>
>>>>>> find a
>>>>>>
>>>>>>>>>> better fix for a 2.6.1 release.
>>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> yes, this is not a regression but better ITs
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Hervé
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>
>>>>>>>> --
>>>>>>>> -----
>>>>>>>> Arnaud Héritier
>>>>>>>> 06-89-76-64-24
>>>>>>>> http://aheritier.net
>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>> Twitter/Skype : aheritier
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>> --
>>>>> -----
>>>>> Arnaud Héritier
>>>>> 06-89-76-64-24
>>>>> http://aheritier.net
>>>>> Mail/GTalk: aheritier@gmail.com
>>>>> Twitter/Skype : aheritier
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
It is what I supposed few days ago that it was a problem with aether that
rejected artifacts installed locally without using aether itself.
it is more annoying if resolver.resolveAlways() doesn't work :(
Arnaud
On Wed, Oct 24, 2012 at 7:25 PM, Hervé BOUTEMY <he...@free.fr>wrote:
> I had a look at the IT output and found this log message
> [DEBUG] Skipped remote update check for
> org.apache.maven.its.dependency:purge-
> local-repository:pom:1.0, already updated during this session.
>
> the code causaing this message is in Aether
>
> I doubt maven-dependency-tree will do anything about this problem: this
> seems
> to be a cache feature of Aether we exceptionnaly don't want
>
> IMHO, if we used resolver.resolveAlways() API (like it was done in
> previous m-
> dependency-p version), this cache should be avoided but I tried and it
> didn't
> change anything
> but this time, this would be a Maven core bug :)
>
> WDYT?
>
> Regards,
>
> Hervé
>
> Le mercredi 24 octobre 2012 08:56:32 Paul Gier a écrit :
> > Hi Arnaud,
> >
> > I should have some time today to try out the shared dependency tree API,
> > if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
> > I can do since this seems to be a regression in 3.0.4. At that point I
> > will just configure the failing ITs to be skipped for 3.0.4.
> >
> > Jenkins also confirmed what I'm seeing locally, that all the ITs pass
> > with 3.0.3:
> > https://builds.apache.org/job/maven-plugins-ITs-m3.0.3/
> >
> > All the dependency plugin ITs pass, however, the job shows failure
> > because some of the invoker plugin its are failing in 3.0.3.
> >
> > On 10/24/2012 08:28 AM, Arnaud Héritier wrote:
> > > ok. thanks
> > > I'll launch the release process tonight.
> > >
> > > On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies
> <bi...@gmail.com>wrote:
> > >> I reran the build with a clean local repo and it's good. So I withdraw
> > >> my complaint, go right ahead.
> > >>
> > >> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <aheritier@gmail.com
> >
> > >>
> > >> wrote:
> > >>> Strange your issue with the report.
> > >>> I don't have it on my side.
> > >>
> > >>> Example :
> > >>
> https://projects.exoplatform.org/forum/forum-component/forum-component-co
> > >> mmon/dependency-analysis.html>>
> > >>> I need to investigate more but it won't be before tonight
> > >>>
> > >>>
> > >>> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <
> bimargulies@gmail.com
> > >>>
> > >>> wrote:
> > >>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
> > >>
> > >> bimargulies@gmail.com>
> > >>
> > >>>> wrote:
> > >>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <
> aheritier@gmail.com
> > >>>>
> > >>>> wrote:
> > >>>>>> Ok if we are all agree I'll process the release this evening.
> > >>>>>> Thanks for your help guys
> > >>>>>
> > >>>>> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
> > >>>>> tested the 'report' mojo last night with the current snapshot and
> it
> > >>>>> died with the same wierd classworlds error that the ITs die with.
> I'm
> > >>>>> willing to help fix this up, but I;m not following the logic of a
> > >>>>> release. Feel free to explain why I'm confused.
> > >>>>
> > >>>> I'll do more diagnosis later today.
> > >>>>
> > >>>>>> Arnaud
> > >>>>>>
> > >>>>>>
> > >>>>>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
> > >>
> > >> herve.boutemy@free.fr
> > >>
> > >>>>> wrote:
> > >>>>>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> > >>>>>>>> I did some more testing, and the tests only seem to fail using
> > >>
> > >> Maven
> > >>
> > >>>>>>>> 3.0.4 for me. I was testing locally with Maven 3.0.3
> previously.
> > >>>>
> > >>>> For
> > >>>>
> > >>>>>>>> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
> > >>
> > >> If
> > >>
> > >>>> you
> > >>>>
> > >>>>>>>> want to release this week it's probably ok to release even with
> > >>
> > >> these
> > >>
> > >>>>>>>> failures because the previous release didn't work at all with
> > >>
> > >> Maven
> > >>
> > >>>> 3.
> > >>>>
> > >>>>>>>> We just didn't have ITs to catch it. We could set the invoker
> > >>
> > >> not to
> > >>
> > >>>>>>>> execute those for Maven 3, and maybe put a note in the docs, and
> > >>>>
> > >>>> find a
> > >>>>
> > >>>>>>>> better fix for a 2.6.1 release.
> > >>>>>>>
> > >>>>>>> +1
> > >>>>>>>
> > >>>>>>> yes, this is not a regression but better ITs
> > >>>>>>>
> > >>>>>>> Regards,
> > >>>>>>>
> > >>>>>>> Hervé
> > >>
> > >> ---------------------------------------------------------------------
> > >>
> > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>>>>
> > >>>>>> --
> > >>>>>> -----
> > >>>>>> Arnaud Héritier
> > >>>>>> 06-89-76-64-24
> > >>>>>> http://aheritier.net
> > >>>>>> Mail/GTalk: aheritier@gmail.com
> > >>>>>> Twitter/Skype : aheritier
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>
> > >>> --
> > >>> -----
> > >>> Arnaud Héritier
> > >>> 06-89-76-64-24
> > >>> http://aheritier.net
> > >>> Mail/GTalk: aheritier@gmail.com
> > >>> Twitter/Skype : aheritier
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Hervé BOUTEMY <he...@free.fr>.
I had a look at the IT output and found this log message
[DEBUG] Skipped remote update check for org.apache.maven.its.dependency:purge-
local-repository:pom:1.0, already updated during this session.
the code causaing this message is in Aether
I doubt maven-dependency-tree will do anything about this problem: this seems
to be a cache feature of Aether we exceptionnaly don't want
IMHO, if we used resolver.resolveAlways() API (like it was done in previous m-
dependency-p version), this cache should be avoided but I tried and it didn't
change anything
but this time, this would be a Maven core bug :)
WDYT?
Regards,
Hervé
Le mercredi 24 octobre 2012 08:56:32 Paul Gier a écrit :
> Hi Arnaud,
>
> I should have some time today to try out the shared dependency tree API,
> if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
> I can do since this seems to be a regression in 3.0.4. At that point I
> will just configure the failing ITs to be skipped for 3.0.4.
>
> Jenkins also confirmed what I'm seeing locally, that all the ITs pass
> with 3.0.3:
> https://builds.apache.org/job/maven-plugins-ITs-m3.0.3/
>
> All the dependency plugin ITs pass, however, the job shows failure
> because some of the invoker plugin its are failing in 3.0.3.
>
> On 10/24/2012 08:28 AM, Arnaud Héritier wrote:
> > ok. thanks
> > I'll launch the release process tonight.
> >
> > On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies
<bi...@gmail.com>wrote:
> >> I reran the build with a clean local repo and it's good. So I withdraw
> >> my complaint, go right ahead.
> >>
> >> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <ah...@gmail.com>
> >>
> >> wrote:
> >>> Strange your issue with the report.
> >>> I don't have it on my side.
> >>
> >>> Example :
> >> https://projects.exoplatform.org/forum/forum-component/forum-component-co
> >> mmon/dependency-analysis.html>>
> >>> I need to investigate more but it won't be before tonight
> >>>
> >>>
> >>> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <bimargulies@gmail.com
> >>>
> >>> wrote:
> >>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
> >>
> >> bimargulies@gmail.com>
> >>
> >>>> wrote:
> >>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <aheritier@gmail.com
> >>>>
> >>>> wrote:
> >>>>>> Ok if we are all agree I'll process the release this evening.
> >>>>>> Thanks for your help guys
> >>>>>
> >>>>> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
> >>>>> tested the 'report' mojo last night with the current snapshot and it
> >>>>> died with the same wierd classworlds error that the ITs die with. I'm
> >>>>> willing to help fix this up, but I;m not following the logic of a
> >>>>> release. Feel free to explain why I'm confused.
> >>>>
> >>>> I'll do more diagnosis later today.
> >>>>
> >>>>>> Arnaud
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
> >>
> >> herve.boutemy@free.fr
> >>
> >>>>> wrote:
> >>>>>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> >>>>>>>> I did some more testing, and the tests only seem to fail using
> >>
> >> Maven
> >>
> >>>>>>>> 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
> >>>>
> >>>> For
> >>>>
> >>>>>>>> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
> >>
> >> If
> >>
> >>>> you
> >>>>
> >>>>>>>> want to release this week it's probably ok to release even with
> >>
> >> these
> >>
> >>>>>>>> failures because the previous release didn't work at all with
> >>
> >> Maven
> >>
> >>>> 3.
> >>>>
> >>>>>>>> We just didn't have ITs to catch it. We could set the invoker
> >>
> >> not to
> >>
> >>>>>>>> execute those for Maven 3, and maybe put a note in the docs, and
> >>>>
> >>>> find a
> >>>>
> >>>>>>>> better fix for a 2.6.1 release.
> >>>>>>>
> >>>>>>> +1
> >>>>>>>
> >>>>>>> yes, this is not a regression but better ITs
> >>>>>>>
> >>>>>>> Regards,
> >>>>>>>
> >>>>>>> Hervé
> >>
> >> ---------------------------------------------------------------------
> >>
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>
> >>>>>> --
> >>>>>> -----
> >>>>>> Arnaud Héritier
> >>>>>> 06-89-76-64-24
> >>>>>> http://aheritier.net
> >>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>> Twitter/Skype : aheritier
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>> --
> >>> -----
> >>> Arnaud Héritier
> >>> 06-89-76-64-24
> >>> http://aheritier.net
> >>> Mail/GTalk: aheritier@gmail.com
> >>> Twitter/Skype : aheritier
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
ok, let me know if you succeed to do something with the dependency tree API.
Arnaud
On Wed, Oct 24, 2012 at 3:56 PM, Paul Gier <pg...@redhat.com> wrote:
> Hi Arnaud,
>
> I should have some time today to try out the shared dependency tree API,
> if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
> I can do since this seems to be a regression in 3.0.4. At that point I
> will just configure the failing ITs to be skipped for 3.0.4.
>
> Jenkins also confirmed what I'm seeing locally, that all the ITs pass
> with 3.0.3:
> https://builds.apache.org/job/maven-plugins-ITs-m3.0.3/
>
> All the dependency plugin ITs pass, however, the job shows failure
> because some of the invoker plugin its are failing in 3.0.3.
>
> On 10/24/2012 08:28 AM, Arnaud Héritier wrote:
> > ok. thanks
> > I'll launch the release process tonight.
> >
> > On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies <bimargulies@gmail.com
> >wrote:
> >
> >> I reran the build with a clean local repo and it's good. So I withdraw
> >> my complaint, go right ahead.
> >>
> >> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <ah...@gmail.com>
> >> wrote:
> >>> Strange your issue with the report.
> >>> I don't have it on my side.
> >>> Example :
> >>>
> >>
> https://projects.exoplatform.org/forum/forum-component/forum-component-common/dependency-analysis.html
> >>> I need to investigate more but it won't be before tonight
> >>>
> >>>
> >>> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <
> bimargulies@gmail.com
> >>> wrote:
> >>>
> >>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
> >> bimargulies@gmail.com>
> >>>> wrote:
> >>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <
> aheritier@gmail.com
> >>>
> >>>> wrote:
> >>>>>> Ok if we are all agree I'll process the release this evening.
> >>>>>> Thanks for your help guys
> >>>>>
> >>>>> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
> >>>>> tested the 'report' mojo last night with the current snapshot and it
> >>>>> died with the same wierd classworlds error that the ITs die with. I'm
> >>>>> willing to help fix this up, but I;m not following the logic of a
> >>>>> release. Feel free to explain why I'm confused.
> >>>>
> >>>> I'll do more diagnosis later today.
> >>>>
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Arnaud
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
> >> herve.boutemy@free.fr
> >>>>> wrote:
> >>>>>>
> >>>>>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> >>>>>>>> I did some more testing, and the tests only seem to fail using
> >> Maven
> >>>>>>>> 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
> >>>> For
> >>>>>>>> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
> >> If
> >>>> you
> >>>>>>>> want to release this week it's probably ok to release even with
> >> these
> >>>>>>>> failures because the previous release didn't work at all with
> >> Maven
> >>>> 3.
> >>>>>>>> We just didn't have ITs to catch it. We could set the invoker
> >> not to
> >>>>>>>> execute those for Maven 3, and maybe put a note in the docs, and
> >>>> find a
> >>>>>>>> better fix for a 2.6.1 release.
> >>>>>>> +1
> >>>>>>>
> >>>>>>> yes, this is not a regression but better ITs
> >>>>>>>
> >>>>>>> Regards,
> >>>>>>>
> >>>>>>> Hervé
> >>>>>>>
> >>>>>>>
> >> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> -----
> >>>>>> Arnaud Héritier
> >>>>>> 06-89-76-64-24
> >>>>>> http://aheritier.net
> >>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>> Twitter/Skype : aheritier
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> -----
> >>> Arnaud Héritier
> >>> 06-89-76-64-24
> >>> http://aheritier.net
> >>> Mail/GTalk: aheritier@gmail.com
> >>> Twitter/Skype : aheritier
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
Hi Arnaud,
I should have some time today to try out the shared dependency tree API,
if it doesn't work in Maven 3.0.4 with that, then I'm not sure what else
I can do since this seems to be a regression in 3.0.4. At that point I
will just configure the failing ITs to be skipped for 3.0.4.
Jenkins also confirmed what I'm seeing locally, that all the ITs pass
with 3.0.3:
https://builds.apache.org/job/maven-plugins-ITs-m3.0.3/
All the dependency plugin ITs pass, however, the job shows failure
because some of the invoker plugin its are failing in 3.0.3.
On 10/24/2012 08:28 AM, Arnaud Héritier wrote:
> ok. thanks
> I'll launch the release process tonight.
>
> On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> I reran the build with a clean local repo and it's good. So I withdraw
>> my complaint, go right ahead.
>>
>> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <ah...@gmail.com>
>> wrote:
>>> Strange your issue with the report.
>>> I don't have it on my side.
>>> Example :
>>>
>> https://projects.exoplatform.org/forum/forum-component/forum-component-common/dependency-analysis.html
>>> I need to investigate more but it won't be before tonight
>>>
>>>
>>> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <bimargulies@gmail.com
>>> wrote:
>>>
>>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
>> bimargulies@gmail.com>
>>>> wrote:
>>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <aheritier@gmail.com
>>>
>>>> wrote:
>>>>>> Ok if we are all agree I'll process the release this evening.
>>>>>> Thanks for your help guys
>>>>>
>>>>> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
>>>>> tested the 'report' mojo last night with the current snapshot and it
>>>>> died with the same wierd classworlds error that the ITs die with. I'm
>>>>> willing to help fix this up, but I;m not following the logic of a
>>>>> release. Feel free to explain why I'm confused.
>>>>
>>>> I'll do more diagnosis later today.
>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Arnaud
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
>> herve.boutemy@free.fr
>>>>> wrote:
>>>>>>
>>>>>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
>>>>>>>> I did some more testing, and the tests only seem to fail using
>> Maven
>>>>>>>> 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
>>>> For
>>>>>>>> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
>> If
>>>> you
>>>>>>>> want to release this week it's probably ok to release even with
>> these
>>>>>>>> failures because the previous release didn't work at all with
>> Maven
>>>> 3.
>>>>>>>> We just didn't have ITs to catch it. We could set the invoker
>> not to
>>>>>>>> execute those for Maven 3, and maybe put a note in the docs, and
>>>> find a
>>>>>>>> better fix for a 2.6.1 release.
>>>>>>> +1
>>>>>>>
>>>>>>> yes, this is not a regression but better ITs
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Hervé
>>>>>>>
>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> -----
>>>>>> Arnaud Héritier
>>>>>> 06-89-76-64-24
>>>>>> http://aheritier.net
>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>> Twitter/Skype : aheritier
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> -----
>>> Arnaud Héritier
>>> 06-89-76-64-24
>>> http://aheritier.net
>>> Mail/GTalk: aheritier@gmail.com
>>> Twitter/Skype : aheritier
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
ok. thanks
I'll launch the release process tonight.
On Wed, Oct 24, 2012 at 2:18 PM, Benson Margulies <bi...@gmail.com>wrote:
> I reran the build with a clean local repo and it's good. So I withdraw
> my complaint, go right ahead.
>
> On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <ah...@gmail.com>
> wrote:
> > Strange your issue with the report.
> > I don't have it on my side.
> > Example :
> >
> https://projects.exoplatform.org/forum/forum-component/forum-component-common/dependency-analysis.html
> > I need to investigate more but it won't be before tonight
> >
> >
> > On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <bimargulies@gmail.com
> >wrote:
> >
> >> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <
> bimargulies@gmail.com>
> >> wrote:
> >> > On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <aheritier@gmail.com
> >
> >> wrote:
> >> >> Ok if we are all agree I'll process the release this evening.
> >> >> Thanks for your help guys
> >> >
> >> > I am -1 to a release which does not work, at all, on Maven 3.0.4. I
> >> > tested the 'report' mojo last night with the current snapshot and it
> >> > died with the same wierd classworlds error that the ITs die with. I'm
> >> > willing to help fix this up, but I;m not following the logic of a
> >> > release. Feel free to explain why I'm confused.
> >>
> >> I'll do more diagnosis later today.
> >>
> >> >
> >> >
> >> >>
> >> >> Arnaud
> >> >>
> >> >>
> >> >> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <
> herve.boutemy@free.fr
> >> >wrote:
> >> >>
> >> >>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> >> >>> > I did some more testing, and the tests only seem to fail using
> Maven
> >> >>> > 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
> >> For
> >> >>> > Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x.
> If
> >> you
> >> >>> > want to release this week it's probably ok to release even with
> these
> >> >>> > failures because the previous release didn't work at all with
> Maven
> >> 3.
> >> >>> > We just didn't have ITs to catch it. We could set the invoker
> not to
> >> >>> > execute those for Maven 3, and maybe put a note in the docs, and
> >> find a
> >> >>> > better fix for a 2.6.1 release.
> >> >>> +1
> >> >>>
> >> >>> yes, this is not a regression but better ITs
> >> >>>
> >> >>> Regards,
> >> >>>
> >> >>> Hervé
> >> >>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >> -----
> >> >> Arnaud Héritier
> >> >> 06-89-76-64-24
> >> >> http://aheritier.net
> >> >> Mail/GTalk: aheritier@gmail.com
> >> >> Twitter/Skype : aheritier
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
> > --
> > -----
> > Arnaud Héritier
> > 06-89-76-64-24
> > http://aheritier.net
> > Mail/GTalk: aheritier@gmail.com
> > Twitter/Skype : aheritier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Benson Margulies <bi...@gmail.com>.
I reran the build with a clean local repo and it's good. So I withdraw
my complaint, go right ahead.
On Wed, Oct 24, 2012 at 7:56 AM, Arnaud Héritier <ah...@gmail.com> wrote:
> Strange your issue with the report.
> I don't have it on my side.
> Example :
> https://projects.exoplatform.org/forum/forum-component/forum-component-common/dependency-analysis.html
> I need to investigate more but it won't be before tonight
>
>
> On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <bi...@gmail.com>
>> wrote:
>> > On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <ah...@gmail.com>
>> wrote:
>> >> Ok if we are all agree I'll process the release this evening.
>> >> Thanks for your help guys
>> >
>> > I am -1 to a release which does not work, at all, on Maven 3.0.4. I
>> > tested the 'report' mojo last night with the current snapshot and it
>> > died with the same wierd classworlds error that the ITs die with. I'm
>> > willing to help fix this up, but I;m not following the logic of a
>> > release. Feel free to explain why I'm confused.
>>
>> I'll do more diagnosis later today.
>>
>> >
>> >
>> >>
>> >> Arnaud
>> >>
>> >>
>> >> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <herve.boutemy@free.fr
>> >wrote:
>> >>
>> >>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
>> >>> > I did some more testing, and the tests only seem to fail using Maven
>> >>> > 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
>> For
>> >>> > Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If
>> you
>> >>> > want to release this week it's probably ok to release even with these
>> >>> > failures because the previous release didn't work at all with Maven
>> 3.
>> >>> > We just didn't have ITs to catch it. We could set the invoker not to
>> >>> > execute those for Maven 3, and maybe put a note in the docs, and
>> find a
>> >>> > better fix for a 2.6.1 release.
>> >>> +1
>> >>>
>> >>> yes, this is not a regression but better ITs
>> >>>
>> >>> Regards,
>> >>>
>> >>> Hervé
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >> -----
>> >> Arnaud Héritier
>> >> 06-89-76-64-24
>> >> http://aheritier.net
>> >> Mail/GTalk: aheritier@gmail.com
>> >> Twitter/Skype : aheritier
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
Strange your issue with the report.
I don't have it on my side.
Example :
https://projects.exoplatform.org/forum/forum-component/forum-component-common/dependency-analysis.html
I need to investigate more but it won't be before tonight
On Wed, Oct 24, 2012 at 1:48 PM, Benson Margulies <bi...@gmail.com>wrote:
> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <bi...@gmail.com>
> wrote:
> > On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <ah...@gmail.com>
> wrote:
> >> Ok if we are all agree I'll process the release this evening.
> >> Thanks for your help guys
> >
> > I am -1 to a release which does not work, at all, on Maven 3.0.4. I
> > tested the 'report' mojo last night with the current snapshot and it
> > died with the same wierd classworlds error that the ITs die with. I'm
> > willing to help fix this up, but I;m not following the logic of a
> > release. Feel free to explain why I'm confused.
>
> I'll do more diagnosis later today.
>
> >
> >
> >>
> >> Arnaud
> >>
> >>
> >> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <herve.boutemy@free.fr
> >wrote:
> >>
> >>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> >>> > I did some more testing, and the tests only seem to fail using Maven
> >>> > 3.0.4 for me. I was testing locally with Maven 3.0.3 previously.
> For
> >>> > Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If
> you
> >>> > want to release this week it's probably ok to release even with these
> >>> > failures because the previous release didn't work at all with Maven
> 3.
> >>> > We just didn't have ITs to catch it. We could set the invoker not to
> >>> > execute those for Maven 3, and maybe put a note in the docs, and
> find a
> >>> > better fix for a 2.6.1 release.
> >>> +1
> >>>
> >>> yes, this is not a regression but better ITs
> >>>
> >>> Regards,
> >>>
> >>> Hervé
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>
> >>
> >> --
> >> -----
> >> Arnaud Héritier
> >> 06-89-76-64-24
> >> http://aheritier.net
> >> Mail/GTalk: aheritier@gmail.com
> >> Twitter/Skype : aheritier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Benson Margulies <bi...@gmail.com>.
On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies <bi...@gmail.com> wrote:
> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <ah...@gmail.com> wrote:
>> Ok if we are all agree I'll process the release this evening.
>> Thanks for your help guys
>
> I am -1 to a release which does not work, at all, on Maven 3.0.4. I
> tested the 'report' mojo last night with the current snapshot and it
> died with the same wierd classworlds error that the ITs die with. I'm
> willing to help fix this up, but I;m not following the logic of a
> release. Feel free to explain why I'm confused.
I'll do more diagnosis later today.
>
>
>>
>> Arnaud
>>
>>
>> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <he...@free.fr>wrote:
>>
>>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
>>> > I did some more testing, and the tests only seem to fail using Maven
>>> > 3.0.4 for me. I was testing locally with Maven 3.0.3 previously. For
>>> > Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If you
>>> > want to release this week it's probably ok to release even with these
>>> > failures because the previous release didn't work at all with Maven 3.
>>> > We just didn't have ITs to catch it. We could set the invoker not to
>>> > execute those for Maven 3, and maybe put a note in the docs, and find a
>>> > better fix for a 2.6.1 release.
>>> +1
>>>
>>> yes, this is not a regression but better ITs
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> -----
>> Arnaud Héritier
>> 06-89-76-64-24
>> http://aheritier.net
>> Mail/GTalk: aheritier@gmail.com
>> Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Benson Margulies <bi...@gmail.com>.
On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier <ah...@gmail.com> wrote:
> Ok if we are all agree I'll process the release this evening.
> Thanks for your help guys
I am -1 to a release which does not work, at all, on Maven 3.0.4. I
tested the 'report' mojo last night with the current snapshot and it
died with the same wierd classworlds error that the ITs die with. I'm
willing to help fix this up, but I;m not following the logic of a
release. Feel free to explain why I'm confused.
>
> Arnaud
>
>
> On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <he...@free.fr>wrote:
>
>> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
>> > I did some more testing, and the tests only seem to fail using Maven
>> > 3.0.4 for me. I was testing locally with Maven 3.0.3 previously. For
>> > Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If you
>> > want to release this week it's probably ok to release even with these
>> > failures because the previous release didn't work at all with Maven 3.
>> > We just didn't have ITs to catch it. We could set the invoker not to
>> > execute those for Maven 3, and maybe put a note in the docs, and find a
>> > better fix for a 2.6.1 release.
>> +1
>>
>> yes, this is not a regression but better ITs
>>
>> Regards,
>>
>> Hervé
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
Ok if we are all agree I'll process the release this evening.
Thanks for your help guys
Arnaud
On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY <he...@free.fr>wrote:
> Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> > I did some more testing, and the tests only seem to fail using Maven
> > 3.0.4 for me. I was testing locally with Maven 3.0.3 previously. For
> > Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If you
> > want to release this week it's probably ok to release even with these
> > failures because the previous release didn't work at all with Maven 3.
> > We just didn't have ITs to catch it. We could set the invoker not to
> > execute those for Maven 3, and maybe put a note in the docs, and find a
> > better fix for a 2.6.1 release.
> +1
>
> yes, this is not a regression but better ITs
>
> Regards,
>
> Hervé
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Hervé BOUTEMY <he...@free.fr>.
Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
> I did some more testing, and the tests only seem to fail using Maven
> 3.0.4 for me. I was testing locally with Maven 3.0.3 previously. For
> Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If you
> want to release this week it's probably ok to release even with these
> failures because the previous release didn't work at all with Maven 3.
> We just didn't have ITs to catch it. We could set the invoker not to
> execute those for Maven 3, and maybe put a note in the docs, and find a
> better fix for a 2.6.1 release.
+1
yes, this is not a regression but better ITs
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
I did some more testing, and the tests only seem to fail using Maven
3.0.4 for me. I was testing locally with Maven 3.0.3 previously. For
Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If you
want to release this week it's probably ok to release even with these
failures because the previous release didn't work at all with Maven 3.
We just didn't have ITs to catch it. We could set the invoker not to
execute those for Maven 3, and maybe put a note in the docs, and find a
better fix for a 2.6.1 release.
On 10/22/2012 02:55 PM, Arnaud Héritier wrote:
> Take your time. It won't be critical to delay the release and I prefer to
> have a good solution
> If I don't succeed to release it this week I'll see if someone else can do
> it later.
> I'm not sure I'll be able to do it in next 2 weeks, I'll be on the other
> side of the planet where they have some rules about internet less fun than
> here.
>
> Arnaud
>
> On Mon, Oct 22, 2012 at 9:39 PM, Paul Gier <pg...@redhat.com> wrote:
>
>> After this change, I'm still seeing the same failures on Jenkins, but
>> not seeing them locally :(
>>
>> I may try the DependencyGraphBuilder as Hervé suggested, but it will
>> probably take another day, because I have some day job work to finish
>> today.
>>
>> On 10/22/2012 12:09 PM, Arnaud Héritier wrote:
>>> As discussed on IRC for now I don't see a better solution.
>>> Someone else has a feedback or some ideas ?
>>>
>>> Arnaud
>>>
>>> On Mon, Oct 22, 2012 at 6:21 PM, Paul Gier <pg...@redhat.com> wrote:
>>>
>>>> I have now split out the manual purge option into a separate mojo, and
>>>> added the requiresDependencyResolution annotation to the
>>>> purge-local-repository mojo. Hopefully, this will allow the dependency
>>>> resolution to happen more predictably.
>>>>
>>>> The advantage of this is that the code is much simpler, and most of the
>>>> ITs seem to work with Maven 2 and 3. Hopefully, all the active ITs will
>>>> pass on Jenkins now.
>>>>
>>>> However, there are a couple of disadvantages to this approach. One is
>>>> that the full dependency tree is always resolved before the purge which
>>>> makes the plugin inefficient for some use-cases. But hopefully, those
>>>> use-cases can be handled by the manual purge goal instead. The other
>>>> disadvantage is that the IT which uses a pom with an unresolvable
>>>> dependency (bad pom) does not work because Maven fails before the plugin
>>>> has a chance to re-resolve it. This seems like a fairly important use
>>>> case to me, because one of the reasons for purging might be that you
>>>> have a bad pom in the local repo. Unfortunately, I'm not able to figure
>>>> out how to get around this in a reliable way.
>>>>
>>>> Eventually, we should probably just break Maven 2 compatibility, and use
>>>> the Aether API for dependency resolution. Maybe this can be done for
>>>> version 3.0 of the dependency plugin.
>>>>
>>>>
>>>> On 10/22/2012 08:16 AM, Arnaud Héritier wrote:
>>>>> I was looking at the issue and don't really understand what's wrong
>> with
>>>>> what you did.
>>>>> I think you are facing the *fucking bug/feature* in Maven 3 (from
>> aether)
>>>>> that rejects some dependencies that are available in the local
>> repository
>>>>> but not in the remote.
>>>>> This is because you install manually the artifact in the local repo and
>>>>> thus ather doesn't want it and we cannot bypass this control.
>>>>> It may explain why ITs are ok with Maven 2 but not Maven 3 on Jenkins.
>>>>>
>>>>> Arnaud
>>>>>
>>>>> On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier <pg...@redhat.com> wrote:
>>>>>
>>>>>> Sorry about that, looks like two of them are failing on Jenkins also.
>>>>>> I'm not sure why I don't see the failures locally, I tested with Maven
>>>>>> 2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
>>>>>>
>>>>>> On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
>>>>>>> FYI, I will need to release also maven-dependency-analyzer
>>>>>>> I need to check its status
>>>>>>> Also 3 ITs added by Paul this WE are failing on my laptop. I will
>> study
>>>>>> if
>>>>>>> I have an environment issue of if this is a problem in ITs or the
>> code
>>>>>>>
>>>>>>> cheers
>>>>>>>
>>>>>>> On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <
>> aheritier@gmail.com
>>>>>>> wrote:
>>>>>>>
>>>>>>>> no problem, you're doing the harder work :-)
>>>>>>>> I'll launch the release process today.
>>>>>>>> I hope to not have too many glitches as I didn't do that for a (too)
>>>>>> long
>>>>>>>> time..
>>>>>>>>
>>>>>>>> Arnaud
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com>
>> wrote:
>>>>>>>>
>>>>>>>>> Ok, I'm done working on the purge-local-repositories goal for now,
>>>>>>>>> thanks for waiting for me.
>>>>>>>>>
>>>>>>>>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
>>>>>>>>>> Hi Paul,
>>>>>>>>>>
>>>>>>>>>> Yes no problem I can do it tomorrow or this week end.
>>>>>>>>>> I just would like to have it out before the end of next week
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> Arnaud
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com>
>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Arnaud,
>>>>>>>>>>>
>>>>>>>>>>> Can you hold off one more day? I have a couple of fixes I want
>> to
>>>>>> get
>>>>>>>>>>> in, and I want to do a bit more testing.
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>>
>>>>>>>>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
>>>>>>>>>>>> ok thx.
>>>>>>>>>>>> I'll do the release tomorrow
>>>>>>>>>>>>
>>>>>>>>>>>> Arnaud
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
>>>>>>>>> rfscholte@apache.org
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Ok, I'm ready
>>>>>>>>>>>>>
>>>>>>>>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>>>>>>>>>>>>> aheritier@gmail.com>:
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
>>>>>>>>> rfscholte@apache.org
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would
>>>>>> need
>>>>>>>>> to
>>>>>>>>>>>>>>> write an IT with a custom packaging type.
>>>>>>>>>>>>>>> That would probably take some time, so I'll pick that up for
>>>> the
>>>>>>>>> 2.7
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ok
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue.
>>>> It
>>>>>>>>> has a
>>>>>>>>>>>>>>> good patch, although I think that the useBaseVersion should
>> be
>>>>>>>>> 'true'
>>>>>>>>>>> by
>>>>>>>>>>>>>>> default. I can fix that today or tomorrow.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ok let me know when it will be good on your side.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> thx
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> thanks,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Robert
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>>>>>>>>>>>>>>> stephen.alan.connolly@gmail.****com
>>>>>> <stephen.alan.connolly@gmail.
>>>>>>>>>>> **com<st...@gmail.com>
>>>>>>>>>>>>>>>>> :
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We should probably close MDEP-124 as WONT FIX given that
>> there
>>>>>>>>> seems
>>>>>>>>>>> no
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> way
>>>>>>>>>>>>>>>> to fix it... or at least the addition of a configuration
>>>> element
>>>>>>>>> to
>>>>>>>>>>>>>>>> allow
>>>>>>>>>>>>>>>> flagging specific dependencies as used even if they seem
>> not.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> MDPE-166 also seems like it should just display a different
>>>>>> output
>>>>>>>>>>> for
>>>>>>>>>>>>>>>> <scope>runtime</scope> namely something like "Unable to
>>>>>> determine
>>>>>>>>>>>>>>>> whether
>>>>>>>>>>>>>>>> used or unused as scope is runtime"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I think the above two "solutions" would be quick to
>> implement
>>>>>> and
>>>>>>>>>>> would
>>>>>>>>>>>>>>>> close the issues out.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <
>>>> aheritier@apache.org
>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> i would like to release the dependency plugin soon.
>>>>>>>>>>>>>>>>> There only too old issues not closed attached to the
>>>> current
>>>>>>>>>>> version
>>>>>>>>>>>>>>>>> (
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
>>>>>>>>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>>>>>>>>>>>>>>>>>
>>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>>>>>>>>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>>>>>>>>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
>>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>>>> but I suppose they are migrated release after release
>> without
>>>>>> any
>>>>>>>>>>> real
>>>>>>>>>>>>>>>>> work
>>>>>>>>>>>>>>>>> on them.
>>>>>>>>>>>>>>>>> I'm interested especially by this fix to use it as
>> report (
>>>>>>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
>>>>>>>>>>> http://jira.codehaus.org/**browse/MDEP-366>
>>>>>>>>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
>>>>>>>>>>> http://jira.codehaus.org/browse/MDEP-366>
>>>>>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> and it has the perf improvement
>>>>>>>>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>>>>>>>>>>>>>>> browse/MDEP-377 <
>> http://jira.codehaus.org/**browse/MDEP-377<
>>>>>>>>>>> http://jira.codehaus.org/browse/MDEP-377>
>>>>>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Nobody against it ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Cheers
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -----
>>>>>>>>>>>>>>>>> Arnaud Héritier
>>>>>>>>>>>>>>>>> http://aheritier.net
>>>>>>>>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>>>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>>>>>>>>>>>> --**---------
>>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.
>> ****org<
>>>>>>>>>>>>>>> dev-unsubscribe@maven.**apache.org <
>>>>>>>>> dev-unsubscribe@maven.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>> ------------------------------**------------------------------**---------
>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
>>>>>>>>>>> dev-unsubscribe@maven.apache.org>
>>>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> -----
>>>>>>>> Arnaud Héritier
>>>>>>>> 06-89-76-64-24
>>>>>>>> http://aheritier.net
>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
Take your time. It won't be critical to delay the release and I prefer to
have a good solution
If I don't succeed to release it this week I'll see if someone else can do
it later.
I'm not sure I'll be able to do it in next 2 weeks, I'll be on the other
side of the planet where they have some rules about internet less fun than
here.
Arnaud
On Mon, Oct 22, 2012 at 9:39 PM, Paul Gier <pg...@redhat.com> wrote:
> After this change, I'm still seeing the same failures on Jenkins, but
> not seeing them locally :(
>
> I may try the DependencyGraphBuilder as Hervé suggested, but it will
> probably take another day, because I have some day job work to finish
> today.
>
> On 10/22/2012 12:09 PM, Arnaud Héritier wrote:
> > As discussed on IRC for now I don't see a better solution.
> > Someone else has a feedback or some ideas ?
> >
> > Arnaud
> >
> > On Mon, Oct 22, 2012 at 6:21 PM, Paul Gier <pg...@redhat.com> wrote:
> >
> >> I have now split out the manual purge option into a separate mojo, and
> >> added the requiresDependencyResolution annotation to the
> >> purge-local-repository mojo. Hopefully, this will allow the dependency
> >> resolution to happen more predictably.
> >>
> >> The advantage of this is that the code is much simpler, and most of the
> >> ITs seem to work with Maven 2 and 3. Hopefully, all the active ITs will
> >> pass on Jenkins now.
> >>
> >> However, there are a couple of disadvantages to this approach. One is
> >> that the full dependency tree is always resolved before the purge which
> >> makes the plugin inefficient for some use-cases. But hopefully, those
> >> use-cases can be handled by the manual purge goal instead. The other
> >> disadvantage is that the IT which uses a pom with an unresolvable
> >> dependency (bad pom) does not work because Maven fails before the plugin
> >> has a chance to re-resolve it. This seems like a fairly important use
> >> case to me, because one of the reasons for purging might be that you
> >> have a bad pom in the local repo. Unfortunately, I'm not able to figure
> >> out how to get around this in a reliable way.
> >>
> >> Eventually, we should probably just break Maven 2 compatibility, and use
> >> the Aether API for dependency resolution. Maybe this can be done for
> >> version 3.0 of the dependency plugin.
> >>
> >>
> >> On 10/22/2012 08:16 AM, Arnaud Héritier wrote:
> >>> I was looking at the issue and don't really understand what's wrong
> with
> >>> what you did.
> >>> I think you are facing the *fucking bug/feature* in Maven 3 (from
> aether)
> >>> that rejects some dependencies that are available in the local
> repository
> >>> but not in the remote.
> >>> This is because you install manually the artifact in the local repo and
> >>> thus ather doesn't want it and we cannot bypass this control.
> >>> It may explain why ITs are ok with Maven 2 but not Maven 3 on Jenkins.
> >>>
> >>> Arnaud
> >>>
> >>> On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier <pg...@redhat.com> wrote:
> >>>
> >>>> Sorry about that, looks like two of them are failing on Jenkins also.
> >>>> I'm not sure why I don't see the failures locally, I tested with Maven
> >>>> 2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
> >>>>
> >>>> On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
> >>>>> FYI, I will need to release also maven-dependency-analyzer
> >>>>> I need to check its status
> >>>>> Also 3 ITs added by Paul this WE are failing on my laptop. I will
> study
> >>>> if
> >>>>> I have an environment issue of if this is a problem in ITs or the
> code
> >>>>>
> >>>>> cheers
> >>>>>
> >>>>> On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <
> aheritier@gmail.com
> >>>>> wrote:
> >>>>>
> >>>>>> no problem, you're doing the harder work :-)
> >>>>>> I'll launch the release process today.
> >>>>>> I hope to not have too many glitches as I didn't do that for a (too)
> >>>> long
> >>>>>> time..
> >>>>>>
> >>>>>> Arnaud
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com>
> wrote:
> >>>>>>
> >>>>>>> Ok, I'm done working on the purge-local-repositories goal for now,
> >>>>>>> thanks for waiting for me.
> >>>>>>>
> >>>>>>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
> >>>>>>>> Hi Paul,
> >>>>>>>>
> >>>>>>>> Yes no problem I can do it tomorrow or this week end.
> >>>>>>>> I just would like to have it out before the end of next week
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>>
> >>>>>>>> Arnaud
> >>>>>>>>
> >>>>>>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com>
> >> wrote:
> >>>>>>>>
> >>>>>>>>> Hi Arnaud,
> >>>>>>>>>
> >>>>>>>>> Can you hold off one more day? I have a couple of fixes I want
> to
> >>>> get
> >>>>>>>>> in, and I want to do a bit more testing.
> >>>>>>>>>
> >>>>>>>>> Thanks!
> >>>>>>>>>
> >>>>>>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
> >>>>>>>>>> ok thx.
> >>>>>>>>>> I'll do the release tomorrow
> >>>>>>>>>>
> >>>>>>>>>> Arnaud
> >>>>>>>>>>
> >>>>>>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
> >>>>>>> rfscholte@apache.org
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Ok, I'm ready
> >>>>>>>>>>>
> >>>>>>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
> >>>>>>>>>>> aheritier@gmail.com>:
> >>>>>>>>>>>
> >>>>>>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
> >>>>>>> rfscholte@apache.org
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would
> >>>> need
> >>>>>>> to
> >>>>>>>>>>>>> write an IT with a custom packaging type.
> >>>>>>>>>>>>> That would probably take some time, so I'll pick that up for
> >> the
> >>>>>>> 2.7
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>> ok
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue.
> >> It
> >>>>>>> has a
> >>>>>>>>>>>>> good patch, although I think that the useBaseVersion should
> be
> >>>>>>> 'true'
> >>>>>>>>> by
> >>>>>>>>>>>>> default. I can fix that today or tomorrow.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>> ok let me know when it will be good on your side.
> >>>>>>>>>>>>
> >>>>>>>>>>>> thx
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> thanks,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Robert
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
> >>>>>>>>>>>>> stephen.alan.connolly@gmail.****com
> >>>> <stephen.alan.connolly@gmail.
> >>>>>>>>> **com<st...@gmail.com>
> >>>>>>>>>>>>>>> :
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> We should probably close MDEP-124 as WONT FIX given that
> there
> >>>>>>> seems
> >>>>>>>>> no
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> way
> >>>>>>>>>>>>>> to fix it... or at least the addition of a configuration
> >> element
> >>>>>>> to
> >>>>>>>>>>>>>> allow
> >>>>>>>>>>>>>> flagging specific dependencies as used even if they seem
> not.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> MDPE-166 also seems like it should just display a different
> >>>> output
> >>>>>>>>> for
> >>>>>>>>>>>>>> <scope>runtime</scope> namely something like "Unable to
> >>>> determine
> >>>>>>>>>>>>>> whether
> >>>>>>>>>>>>>> used or unused as scope is runtime"
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I think the above two "solutions" would be quick to
> implement
> >>>> and
> >>>>>>>>> would
> >>>>>>>>>>>>>> close the issues out.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <
> >> aheritier@apache.org
> >>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hi all,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> i would like to release the dependency plugin soon.
> >>>>>>>>>>>>>>> There only too old issues not closed attached to the
> >> current
> >>>>>>>>> version
> >>>>>>>>>>>>>>> (
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
> >>>>>>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
> >>>>>>>>>>>>>>>
> >>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
> >>>>>>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
> >>>>>>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>
> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> >>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> )
> >>>>>>>>>>>>>>> but I suppose they are migrated release after release
> without
> >>>> any
> >>>>>>>>> real
> >>>>>>>>>>>>>>> work
> >>>>>>>>>>>>>>> on them.
> >>>>>>>>>>>>>>> I'm interested especially by this fix to use it as
> report (
> >>>>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
> >>>>>>>>> http://jira.codehaus.org/**browse/MDEP-366>
> >>>>>>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
> >>>>>>>>> http://jira.codehaus.org/browse/MDEP-366>
> >>>>>>>>>>>>>>>> )
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> and it has the perf improvement
> >>>>>>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
> >>>>>>>>>>>>>>> browse/MDEP-377 <
> http://jira.codehaus.org/**browse/MDEP-377<
> >>>>>>>>> http://jira.codehaus.org/browse/MDEP-377>
> >>>>>>>>>>>>>>>> )
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Nobody against it ?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Cheers
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> -----
> >>>>>>>>>>>>>>> Arnaud Héritier
> >>>>>>>>>>>>>>> http://aheritier.net
> >>>>>>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>>>>>>>>>>> Twitter/Skype : aheritier
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>> ------------------------------****----------------------------**
> >>>>>>>>>>>>> --**---------
> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.
> ****org<
> >>>>>>>>>>>>> dev-unsubscribe@maven.**apache.org <
> >>>>>>> dev-unsubscribe@maven.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> >>
> ------------------------------**------------------------------**---------
> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
> >>>>>>>>> dev-unsubscribe@maven.apache.org>
> >>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >> ---------------------------------------------------------------------
> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> -----
> >>>>>> Arnaud Héritier
> >>>>>> 06-89-76-64-24
> >>>>>> http://aheritier.net
> >>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>> Twitter/Skype : aheritier
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
After this change, I'm still seeing the same failures on Jenkins, but
not seeing them locally :(
I may try the DependencyGraphBuilder as Hervé suggested, but it will
probably take another day, because I have some day job work to finish today.
On 10/22/2012 12:09 PM, Arnaud Héritier wrote:
> As discussed on IRC for now I don't see a better solution.
> Someone else has a feedback or some ideas ?
>
> Arnaud
>
> On Mon, Oct 22, 2012 at 6:21 PM, Paul Gier <pg...@redhat.com> wrote:
>
>> I have now split out the manual purge option into a separate mojo, and
>> added the requiresDependencyResolution annotation to the
>> purge-local-repository mojo. Hopefully, this will allow the dependency
>> resolution to happen more predictably.
>>
>> The advantage of this is that the code is much simpler, and most of the
>> ITs seem to work with Maven 2 and 3. Hopefully, all the active ITs will
>> pass on Jenkins now.
>>
>> However, there are a couple of disadvantages to this approach. One is
>> that the full dependency tree is always resolved before the purge which
>> makes the plugin inefficient for some use-cases. But hopefully, those
>> use-cases can be handled by the manual purge goal instead. The other
>> disadvantage is that the IT which uses a pom with an unresolvable
>> dependency (bad pom) does not work because Maven fails before the plugin
>> has a chance to re-resolve it. This seems like a fairly important use
>> case to me, because one of the reasons for purging might be that you
>> have a bad pom in the local repo. Unfortunately, I'm not able to figure
>> out how to get around this in a reliable way.
>>
>> Eventually, we should probably just break Maven 2 compatibility, and use
>> the Aether API for dependency resolution. Maybe this can be done for
>> version 3.0 of the dependency plugin.
>>
>>
>> On 10/22/2012 08:16 AM, Arnaud Héritier wrote:
>>> I was looking at the issue and don't really understand what's wrong with
>>> what you did.
>>> I think you are facing the *fucking bug/feature* in Maven 3 (from aether)
>>> that rejects some dependencies that are available in the local repository
>>> but not in the remote.
>>> This is because you install manually the artifact in the local repo and
>>> thus ather doesn't want it and we cannot bypass this control.
>>> It may explain why ITs are ok with Maven 2 but not Maven 3 on Jenkins.
>>>
>>> Arnaud
>>>
>>> On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier <pg...@redhat.com> wrote:
>>>
>>>> Sorry about that, looks like two of them are failing on Jenkins also.
>>>> I'm not sure why I don't see the failures locally, I tested with Maven
>>>> 2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
>>>>
>>>> On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
>>>>> FYI, I will need to release also maven-dependency-analyzer
>>>>> I need to check its status
>>>>> Also 3 ITs added by Paul this WE are failing on my laptop. I will study
>>>> if
>>>>> I have an environment issue of if this is a problem in ITs or the code
>>>>>
>>>>> cheers
>>>>>
>>>>> On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <aheritier@gmail.com
>>>>> wrote:
>>>>>
>>>>>> no problem, you're doing the harder work :-)
>>>>>> I'll launch the release process today.
>>>>>> I hope to not have too many glitches as I didn't do that for a (too)
>>>> long
>>>>>> time..
>>>>>>
>>>>>> Arnaud
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
>>>>>>
>>>>>>> Ok, I'm done working on the purge-local-repositories goal for now,
>>>>>>> thanks for waiting for me.
>>>>>>>
>>>>>>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
>>>>>>>> Hi Paul,
>>>>>>>>
>>>>>>>> Yes no problem I can do it tomorrow or this week end.
>>>>>>>> I just would like to have it out before the end of next week
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Arnaud
>>>>>>>>
>>>>>>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com>
>> wrote:
>>>>>>>>
>>>>>>>>> Hi Arnaud,
>>>>>>>>>
>>>>>>>>> Can you hold off one more day? I have a couple of fixes I want to
>>>> get
>>>>>>>>> in, and I want to do a bit more testing.
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
>>>>>>>>>> ok thx.
>>>>>>>>>> I'll do the release tomorrow
>>>>>>>>>>
>>>>>>>>>> Arnaud
>>>>>>>>>>
>>>>>>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
>>>>>>> rfscholte@apache.org
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Ok, I'm ready
>>>>>>>>>>>
>>>>>>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>>>>>>>>>>> aheritier@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
>>>>>>> rfscholte@apache.org
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would
>>>> need
>>>>>>> to
>>>>>>>>>>>>> write an IT with a custom packaging type.
>>>>>>>>>>>>> That would probably take some time, so I'll pick that up for
>> the
>>>>>>> 2.7
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> ok
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue.
>> It
>>>>>>> has a
>>>>>>>>>>>>> good patch, although I think that the useBaseVersion should be
>>>>>>> 'true'
>>>>>>>>> by
>>>>>>>>>>>>> default. I can fix that today or tomorrow.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> ok let me know when it will be good on your side.
>>>>>>>>>>>>
>>>>>>>>>>>> thx
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Robert
>>>>>>>>>>>>>
>>>>>>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>>>>>>>>>>>>> stephen.alan.connolly@gmail.****com
>>>> <stephen.alan.connolly@gmail.
>>>>>>>>> **com<st...@gmail.com>
>>>>>>>>>>>>>>> :
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We should probably close MDEP-124 as WONT FIX given that there
>>>>>>> seems
>>>>>>>>> no
>>>>>>>>>>>>>
>>>>>>>>>>>>>> way
>>>>>>>>>>>>>> to fix it... or at least the addition of a configuration
>> element
>>>>>>> to
>>>>>>>>>>>>>> allow
>>>>>>>>>>>>>> flagging specific dependencies as used even if they seem not.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> MDPE-166 also seems like it should just display a different
>>>> output
>>>>>>>>> for
>>>>>>>>>>>>>> <scope>runtime</scope> namely something like "Unable to
>>>> determine
>>>>>>>>>>>>>> whether
>>>>>>>>>>>>>> used or unused as scope is runtime"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think the above two "solutions" would be quick to implement
>>>> and
>>>>>>>>> would
>>>>>>>>>>>>>> close the issues out.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <
>> aheritier@apache.org
>>>>>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> i would like to release the dependency plugin soon.
>>>>>>>>>>>>>>> There only too old issues not closed attached to the
>> current
>>>>>>>>> version
>>>>>>>>>>>>>>> (
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
>>>>>>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>>>>>>>>>>>>>>>
>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>>>>>>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>>>>>>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
>>>>>>>>>
>>>>>>>
>>>>
>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>> but I suppose they are migrated release after release without
>>>> any
>>>>>>>>> real
>>>>>>>>>>>>>>> work
>>>>>>>>>>>>>>> on them.
>>>>>>>>>>>>>>> I'm interested especially by this fix to use it as report (
>>>>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
>>>>>>>>> http://jira.codehaus.org/**browse/MDEP-366>
>>>>>>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
>>>>>>>>> http://jira.codehaus.org/browse/MDEP-366>
>>>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> and it has the perf improvement
>>>>>>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>>>>>>>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
>>>>>>>>> http://jira.codehaus.org/browse/MDEP-377>
>>>>>>>>>>>>>>>> )
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Nobody against it ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Cheers
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -----
>>>>>>>>>>>>>>> Arnaud Héritier
>>>>>>>>>>>>>>> http://aheritier.net
>>>>>>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>> ------------------------------****----------------------------**
>>>>>>>>>>>>> --**---------
>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>>>>>>>>>>>>> dev-unsubscribe@maven.**apache.org <
>>>>>>> dev-unsubscribe@maven.apache.org
>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>> ------------------------------**------------------------------**---------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
>>>>>>>>> dev-unsubscribe@maven.apache.org>
>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> -----
>>>>>> Arnaud Héritier
>>>>>> 06-89-76-64-24
>>>>>> http://aheritier.net
>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>> Twitter/Skype : aheritier
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
As discussed on IRC for now I don't see a better solution.
Someone else has a feedback or some ideas ?
Arnaud
On Mon, Oct 22, 2012 at 6:21 PM, Paul Gier <pg...@redhat.com> wrote:
> I have now split out the manual purge option into a separate mojo, and
> added the requiresDependencyResolution annotation to the
> purge-local-repository mojo. Hopefully, this will allow the dependency
> resolution to happen more predictably.
>
> The advantage of this is that the code is much simpler, and most of the
> ITs seem to work with Maven 2 and 3. Hopefully, all the active ITs will
> pass on Jenkins now.
>
> However, there are a couple of disadvantages to this approach. One is
> that the full dependency tree is always resolved before the purge which
> makes the plugin inefficient for some use-cases. But hopefully, those
> use-cases can be handled by the manual purge goal instead. The other
> disadvantage is that the IT which uses a pom with an unresolvable
> dependency (bad pom) does not work because Maven fails before the plugin
> has a chance to re-resolve it. This seems like a fairly important use
> case to me, because one of the reasons for purging might be that you
> have a bad pom in the local repo. Unfortunately, I'm not able to figure
> out how to get around this in a reliable way.
>
> Eventually, we should probably just break Maven 2 compatibility, and use
> the Aether API for dependency resolution. Maybe this can be done for
> version 3.0 of the dependency plugin.
>
>
> On 10/22/2012 08:16 AM, Arnaud Héritier wrote:
> > I was looking at the issue and don't really understand what's wrong with
> > what you did.
> > I think you are facing the *fucking bug/feature* in Maven 3 (from aether)
> > that rejects some dependencies that are available in the local repository
> > but not in the remote.
> > This is because you install manually the artifact in the local repo and
> > thus ather doesn't want it and we cannot bypass this control.
> > It may explain why ITs are ok with Maven 2 but not Maven 3 on Jenkins.
> >
> > Arnaud
> >
> > On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier <pg...@redhat.com> wrote:
> >
> >> Sorry about that, looks like two of them are failing on Jenkins also.
> >> I'm not sure why I don't see the failures locally, I tested with Maven
> >> 2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
> >>
> >> On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
> >>> FYI, I will need to release also maven-dependency-analyzer
> >>> I need to check its status
> >>> Also 3 ITs added by Paul this WE are failing on my laptop. I will study
> >> if
> >>> I have an environment issue of if this is a problem in ITs or the code
> >>>
> >>> cheers
> >>>
> >>> On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <aheritier@gmail.com
> >>> wrote:
> >>>
> >>>> no problem, you're doing the harder work :-)
> >>>> I'll launch the release process today.
> >>>> I hope to not have too many glitches as I didn't do that for a (too)
> >> long
> >>>> time..
> >>>>
> >>>> Arnaud
> >>>>
> >>>>
> >>>>
> >>>> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
> >>>>
> >>>>> Ok, I'm done working on the purge-local-repositories goal for now,
> >>>>> thanks for waiting for me.
> >>>>>
> >>>>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
> >>>>>> Hi Paul,
> >>>>>>
> >>>>>> Yes no problem I can do it tomorrow or this week end.
> >>>>>> I just would like to have it out before the end of next week
> >>>>>>
> >>>>>> Cheers,
> >>>>>>
> >>>>>> Arnaud
> >>>>>>
> >>>>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com>
> wrote:
> >>>>>>
> >>>>>>> Hi Arnaud,
> >>>>>>>
> >>>>>>> Can you hold off one more day? I have a couple of fixes I want to
> >> get
> >>>>>>> in, and I want to do a bit more testing.
> >>>>>>>
> >>>>>>> Thanks!
> >>>>>>>
> >>>>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
> >>>>>>>> ok thx.
> >>>>>>>> I'll do the release tomorrow
> >>>>>>>>
> >>>>>>>> Arnaud
> >>>>>>>>
> >>>>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
> >>>>> rfscholte@apache.org
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Ok, I'm ready
> >>>>>>>>>
> >>>>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
> >>>>>>>>> aheritier@gmail.com>:
> >>>>>>>>>
> >>>>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
> >>>>> rfscholte@apache.org
> >>>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi,
> >>>>>>>>>>>
> >>>>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would
> >> need
> >>>>> to
> >>>>>>>>>>> write an IT with a custom packaging type.
> >>>>>>>>>>> That would probably take some time, so I'll pick that up for
> the
> >>>>> 2.7
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>> ok
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue.
> It
> >>>>> has a
> >>>>>>>>>>> good patch, although I think that the useBaseVersion should be
> >>>>> 'true'
> >>>>>>> by
> >>>>>>>>>>> default. I can fix that today or tomorrow.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>> ok let me know when it will be good on your side.
> >>>>>>>>>>
> >>>>>>>>>> thx
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> thanks,
> >>>>>>>>>>>
> >>>>>>>>>>> Robert
> >>>>>>>>>>>
> >>>>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
> >>>>>>>>>>> stephen.alan.connolly@gmail.****com
> >> <stephen.alan.connolly@gmail.
> >>>>>>> **com<st...@gmail.com>
> >>>>>>>>>>>>> :
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> We should probably close MDEP-124 as WONT FIX given that there
> >>>>> seems
> >>>>>>> no
> >>>>>>>>>>>
> >>>>>>>>>>>> way
> >>>>>>>>>>>> to fix it... or at least the addition of a configuration
> element
> >>>>> to
> >>>>>>>>>>>> allow
> >>>>>>>>>>>> flagging specific dependencies as used even if they seem not.
> >>>>>>>>>>>>
> >>>>>>>>>>>> MDPE-166 also seems like it should just display a different
> >> output
> >>>>>>> for
> >>>>>>>>>>>> <scope>runtime</scope> namely something like "Unable to
> >> determine
> >>>>>>>>>>>> whether
> >>>>>>>>>>>> used or unused as scope is runtime"
> >>>>>>>>>>>>
> >>>>>>>>>>>> I think the above two "solutions" would be quick to implement
> >> and
> >>>>>>> would
> >>>>>>>>>>>> close the issues out.
> >>>>>>>>>>>>
> >>>>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <
> aheritier@apache.org
> >>>
> >>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hi all,
> >>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> i would like to release the dependency plugin soon.
> >>>>>>>>>>>>> There only too old issues not closed attached to the
> current
> >>>>>>> version
> >>>>>>>>>>>>> (
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
> >>>>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
> >>>>>>>>>>>>>
> >> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
> >>>>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
> >>>>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
> >>>>>>>
> >>>>>
> >>
> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> >>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> )
> >>>>>>>>>>>>> but I suppose they are migrated release after release without
> >> any
> >>>>>>> real
> >>>>>>>>>>>>> work
> >>>>>>>>>>>>> on them.
> >>>>>>>>>>>>> I'm interested especially by this fix to use it as report (
> >>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
> >>>>>>> http://jira.codehaus.org/**browse/MDEP-366>
> >>>>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
> >>>>>>> http://jira.codehaus.org/browse/MDEP-366>
> >>>>>>>>>>>>>> )
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> and it has the perf improvement
> >>>>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
> >>>>>>>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
> >>>>>>> http://jira.codehaus.org/browse/MDEP-377>
> >>>>>>>>>>>>>> )
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Nobody against it ?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Cheers
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -----
> >>>>>>>>>>>>> Arnaud Héritier
> >>>>>>>>>>>>> http://aheritier.net
> >>>>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>>>>>>>>> Twitter/Skype : aheritier
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >> ------------------------------****----------------------------**
> >>>>>>>>>>> --**---------
> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
> >>>>>>>>>>> dev-unsubscribe@maven.**apache.org <
> >>>>> dev-unsubscribe@maven.apache.org
> >>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>
> ------------------------------**------------------------------**---------
> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
> >>>>>>> dev-unsubscribe@maven.apache.org>
> >>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> -----
> >>>> Arnaud Héritier
> >>>> 06-89-76-64-24
> >>>> http://aheritier.net
> >>>> Mail/GTalk: aheritier@gmail.com
> >>>> Twitter/Skype : aheritier
> >>>>
> >>>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
I have now split out the manual purge option into a separate mojo, and
added the requiresDependencyResolution annotation to the
purge-local-repository mojo. Hopefully, this will allow the dependency
resolution to happen more predictably.
The advantage of this is that the code is much simpler, and most of the
ITs seem to work with Maven 2 and 3. Hopefully, all the active ITs will
pass on Jenkins now.
However, there are a couple of disadvantages to this approach. One is
that the full dependency tree is always resolved before the purge which
makes the plugin inefficient for some use-cases. But hopefully, those
use-cases can be handled by the manual purge goal instead. The other
disadvantage is that the IT which uses a pom with an unresolvable
dependency (bad pom) does not work because Maven fails before the plugin
has a chance to re-resolve it. This seems like a fairly important use
case to me, because one of the reasons for purging might be that you
have a bad pom in the local repo. Unfortunately, I'm not able to figure
out how to get around this in a reliable way.
Eventually, we should probably just break Maven 2 compatibility, and use
the Aether API for dependency resolution. Maybe this can be done for
version 3.0 of the dependency plugin.
On 10/22/2012 08:16 AM, Arnaud Héritier wrote:
> I was looking at the issue and don't really understand what's wrong with
> what you did.
> I think you are facing the *fucking bug/feature* in Maven 3 (from aether)
> that rejects some dependencies that are available in the local repository
> but not in the remote.
> This is because you install manually the artifact in the local repo and
> thus ather doesn't want it and we cannot bypass this control.
> It may explain why ITs are ok with Maven 2 but not Maven 3 on Jenkins.
>
> Arnaud
>
> On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier <pg...@redhat.com> wrote:
>
>> Sorry about that, looks like two of them are failing on Jenkins also.
>> I'm not sure why I don't see the failures locally, I tested with Maven
>> 2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
>>
>> On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
>>> FYI, I will need to release also maven-dependency-analyzer
>>> I need to check its status
>>> Also 3 ITs added by Paul this WE are failing on my laptop. I will study
>> if
>>> I have an environment issue of if this is a problem in ITs or the code
>>>
>>> cheers
>>>
>>> On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <aheritier@gmail.com
>>> wrote:
>>>
>>>> no problem, you're doing the harder work :-)
>>>> I'll launch the release process today.
>>>> I hope to not have too many glitches as I didn't do that for a (too)
>> long
>>>> time..
>>>>
>>>> Arnaud
>>>>
>>>>
>>>>
>>>> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
>>>>
>>>>> Ok, I'm done working on the purge-local-repositories goal for now,
>>>>> thanks for waiting for me.
>>>>>
>>>>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
>>>>>> Hi Paul,
>>>>>>
>>>>>> Yes no problem I can do it tomorrow or this week end.
>>>>>> I just would like to have it out before the end of next week
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Arnaud
>>>>>>
>>>>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
>>>>>>
>>>>>>> Hi Arnaud,
>>>>>>>
>>>>>>> Can you hold off one more day? I have a couple of fixes I want to
>> get
>>>>>>> in, and I want to do a bit more testing.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
>>>>>>>> ok thx.
>>>>>>>> I'll do the release tomorrow
>>>>>>>>
>>>>>>>> Arnaud
>>>>>>>>
>>>>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
>>>>> rfscholte@apache.org
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Ok, I'm ready
>>>>>>>>>
>>>>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>>>>>>>>> aheritier@gmail.com>:
>>>>>>>>>
>>>>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
>>>>> rfscholte@apache.org
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would
>> need
>>>>> to
>>>>>>>>>>> write an IT with a custom packaging type.
>>>>>>>>>>> That would probably take some time, so I'll pick that up for the
>>>>> 2.7
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> ok
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It
>>>>> has a
>>>>>>>>>>> good patch, although I think that the useBaseVersion should be
>>>>> 'true'
>>>>>>> by
>>>>>>>>>>> default. I can fix that today or tomorrow.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> ok let me know when it will be good on your side.
>>>>>>>>>>
>>>>>>>>>> thx
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> thanks,
>>>>>>>>>>>
>>>>>>>>>>> Robert
>>>>>>>>>>>
>>>>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>>>>>>>>>>> stephen.alan.connolly@gmail.****com
>> <stephen.alan.connolly@gmail.
>>>>>>> **com<st...@gmail.com>
>>>>>>>>>>>>> :
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We should probably close MDEP-124 as WONT FIX given that there
>>>>> seems
>>>>>>> no
>>>>>>>>>>>
>>>>>>>>>>>> way
>>>>>>>>>>>> to fix it... or at least the addition of a configuration element
>>>>> to
>>>>>>>>>>>> allow
>>>>>>>>>>>> flagging specific dependencies as used even if they seem not.
>>>>>>>>>>>>
>>>>>>>>>>>> MDPE-166 also seems like it should just display a different
>> output
>>>>>>> for
>>>>>>>>>>>> <scope>runtime</scope> namely something like "Unable to
>> determine
>>>>>>>>>>>> whether
>>>>>>>>>>>> used or unused as scope is runtime"
>>>>>>>>>>>>
>>>>>>>>>>>> I think the above two "solutions" would be quick to implement
>> and
>>>>>>> would
>>>>>>>>>>>> close the issues out.
>>>>>>>>>>>>
>>>>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <aheritier@apache.org
>>>
>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> i would like to release the dependency plugin soon.
>>>>>>>>>>>>> There only too old issues not closed attached to the current
>>>>>>> version
>>>>>>>>>>>>> (
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
>>>>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>>>>>>>>>>>>>
>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>>>>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>>>>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
>>>>>>>
>>>>>
>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> )
>>>>>>>>>>>>> but I suppose they are migrated release after release without
>> any
>>>>>>> real
>>>>>>>>>>>>> work
>>>>>>>>>>>>> on them.
>>>>>>>>>>>>> I'm interested especially by this fix to use it as report (
>>>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
>>>>>>> http://jira.codehaus.org/**browse/MDEP-366>
>>>>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
>>>>>>> http://jira.codehaus.org/browse/MDEP-366>
>>>>>>>>>>>>>> )
>>>>>>>>>>>>>
>>>>>>>>>>>>> and it has the perf improvement
>>>>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>>>>>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
>>>>>>> http://jira.codehaus.org/browse/MDEP-377>
>>>>>>>>>>>>>> )
>>>>>>>>>>>>>
>>>>>>>>>>>>> Nobody against it ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers
>>>>>>>>>>>>>
>>>>>>>>>>>>> -----
>>>>>>>>>>>>> Arnaud Héritier
>>>>>>>>>>>>> http://aheritier.net
>>>>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>> ------------------------------****----------------------------**
>>>>>>>>>>> --**---------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>>>>>>>>>>> dev-unsubscribe@maven.**apache.org <
>>>>> dev-unsubscribe@maven.apache.org
>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>> ------------------------------**------------------------------**---------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
>>>>>>> dev-unsubscribe@maven.apache.org>
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> -----
>>>> Arnaud Héritier
>>>> 06-89-76-64-24
>>>> http://aheritier.net
>>>> Mail/GTalk: aheritier@gmail.com
>>>> Twitter/Skype : aheritier
>>>>
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
I was looking at the issue and don't really understand what's wrong with
what you did.
I think you are facing the *fucking bug/feature* in Maven 3 (from aether)
that rejects some dependencies that are available in the local repository
but not in the remote.
This is because you install manually the artifact in the local repo and
thus ather doesn't want it and we cannot bypass this control.
It may explain why ITs are ok with Maven 2 but not Maven 3 on Jenkins.
Arnaud
On Mon, Oct 22, 2012 at 2:58 PM, Paul Gier <pg...@redhat.com> wrote:
> Sorry about that, looks like two of them are failing on Jenkins also.
> I'm not sure why I don't see the failures locally, I tested with Maven
> 2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
>
> On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
> > FYI, I will need to release also maven-dependency-analyzer
> > I need to check its status
> > Also 3 ITs added by Paul this WE are failing on my laptop. I will study
> if
> > I have an environment issue of if this is a problem in ITs or the code
> >
> > cheers
> >
> > On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <aheritier@gmail.com
> >wrote:
> >
> >> no problem, you're doing the harder work :-)
> >> I'll launch the release process today.
> >> I hope to not have too many glitches as I didn't do that for a (too)
> long
> >> time..
> >>
> >> Arnaud
> >>
> >>
> >>
> >> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
> >>
> >>> Ok, I'm done working on the purge-local-repositories goal for now,
> >>> thanks for waiting for me.
> >>>
> >>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
> >>>> Hi Paul,
> >>>>
> >>>> Yes no problem I can do it tomorrow or this week end.
> >>>> I just would like to have it out before the end of next week
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Arnaud
> >>>>
> >>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
> >>>>
> >>>>> Hi Arnaud,
> >>>>>
> >>>>> Can you hold off one more day? I have a couple of fixes I want to
> get
> >>>>> in, and I want to do a bit more testing.
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
> >>>>>> ok thx.
> >>>>>> I'll do the release tomorrow
> >>>>>>
> >>>>>> Arnaud
> >>>>>>
> >>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
> >>> rfscholte@apache.org
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Ok, I'm ready
> >>>>>>>
> >>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
> >>>>>>> aheritier@gmail.com>:
> >>>>>>>
> >>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
> >>> rfscholte@apache.org
> >>>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would
> need
> >>> to
> >>>>>>>>> write an IT with a custom packaging type.
> >>>>>>>>> That would probably take some time, so I'll pick that up for the
> >>> 2.7
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>> ok
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It
> >>> has a
> >>>>>>>>> good patch, although I think that the useBaseVersion should be
> >>> 'true'
> >>>>> by
> >>>>>>>>> default. I can fix that today or tomorrow.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>> ok let me know when it will be good on your side.
> >>>>>>>>
> >>>>>>>> thx
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> thanks,
> >>>>>>>>>
> >>>>>>>>> Robert
> >>>>>>>>>
> >>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
> >>>>>>>>> stephen.alan.connolly@gmail.****com
> <stephen.alan.connolly@gmail.
> >>>>> **com<st...@gmail.com>
> >>>>>>>>>>> :
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> We should probably close MDEP-124 as WONT FIX given that there
> >>> seems
> >>>>> no
> >>>>>>>>>
> >>>>>>>>>> way
> >>>>>>>>>> to fix it... or at least the addition of a configuration element
> >>> to
> >>>>>>>>>> allow
> >>>>>>>>>> flagging specific dependencies as used even if they seem not.
> >>>>>>>>>>
> >>>>>>>>>> MDPE-166 also seems like it should just display a different
> output
> >>>>> for
> >>>>>>>>>> <scope>runtime</scope> namely something like "Unable to
> determine
> >>>>>>>>>> whether
> >>>>>>>>>> used or unused as scope is runtime"
> >>>>>>>>>>
> >>>>>>>>>> I think the above two "solutions" would be quick to implement
> and
> >>>>> would
> >>>>>>>>>> close the issues out.
> >>>>>>>>>>
> >>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <aheritier@apache.org
> >
> >>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi all,
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> i would like to release the dependency plugin soon.
> >>>>>>>>>>> There only too old issues not closed attached to the current
> >>>>> version
> >>>>>>>>>>> (
> >>>>>>>>>>>
> >>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
> >>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
> >>>>>>>>>>>
> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
> >>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
> >>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
> >>>>>
> >>>
> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> >>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> )
> >>>>>>>>>>> but I suppose they are migrated release after release without
> any
> >>>>> real
> >>>>>>>>>>> work
> >>>>>>>>>>> on them.
> >>>>>>>>>>> I'm interested especially by this fix to use it as report (
> >>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
> >>>>> http://jira.codehaus.org/**browse/MDEP-366>
> >>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
> >>>>> http://jira.codehaus.org/browse/MDEP-366>
> >>>>>>>>>>>> )
> >>>>>>>>>>>
> >>>>>>>>>>> and it has the perf improvement
> >>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
> >>>>>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
> >>>>> http://jira.codehaus.org/browse/MDEP-377>
> >>>>>>>>>>>> )
> >>>>>>>>>>>
> >>>>>>>>>>> Nobody against it ?
> >>>>>>>>>>>
> >>>>>>>>>>> Cheers
> >>>>>>>>>>>
> >>>>>>>>>>> -----
> >>>>>>>>>>> Arnaud Héritier
> >>>>>>>>>>> http://aheritier.net
> >>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>>>>>>> Twitter/Skype : aheritier
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> ------------------------------****----------------------------**
> >>>>>>>>> --**---------
> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
> >>>>>>>>> dev-unsubscribe@maven.**apache.org <
> >>> dev-unsubscribe@maven.apache.org
> >>>>>>>
> >>>>>>>>>
> >>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> ------------------------------**------------------------------**---------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
> >>>>> dev-unsubscribe@maven.apache.org>
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>
> >>
> >> --
> >> -----
> >> Arnaud Héritier
> >> 06-89-76-64-24
> >> http://aheritier.net
> >> Mail/GTalk: aheritier@gmail.com
> >> Twitter/Skype : aheritier
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
Sorry about that, looks like two of them are failing on Jenkins also.
I'm not sure why I don't see the failures locally, I tested with Maven
2.2.1 and 3 and java 5 and 6. I'll see if I can figure out the cause.
On 10/22/2012 05:25 AM, Arnaud Héritier wrote:
> FYI, I will need to release also maven-dependency-analyzer
> I need to check its status
> Also 3 ITs added by Paul this WE are failing on my laptop. I will study if
> I have an environment issue of if this is a problem in ITs or the code
>
> cheers
>
> On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <ah...@gmail.com>wrote:
>
>> no problem, you're doing the harder work :-)
>> I'll launch the release process today.
>> I hope to not have too many glitches as I didn't do that for a (too) long
>> time..
>>
>> Arnaud
>>
>>
>>
>> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
>>
>>> Ok, I'm done working on the purge-local-repositories goal for now,
>>> thanks for waiting for me.
>>>
>>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
>>>> Hi Paul,
>>>>
>>>> Yes no problem I can do it tomorrow or this week end.
>>>> I just would like to have it out before the end of next week
>>>>
>>>> Cheers,
>>>>
>>>> Arnaud
>>>>
>>>> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
>>>>
>>>>> Hi Arnaud,
>>>>>
>>>>> Can you hold off one more day? I have a couple of fixes I want to get
>>>>> in, and I want to do a bit more testing.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
>>>>>> ok thx.
>>>>>> I'll do the release tomorrow
>>>>>>
>>>>>> Arnaud
>>>>>>
>>>>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
>>> rfscholte@apache.org
>>>>>> wrote:
>>>>>>
>>>>>>> Ok, I'm ready
>>>>>>>
>>>>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>>>>>>> aheritier@gmail.com>:
>>>>>>>
>>>>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
>>> rfscholte@apache.org
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would need
>>> to
>>>>>>>>> write an IT with a custom packaging type.
>>>>>>>>> That would probably take some time, so I'll pick that up for the
>>> 2.7
>>>>>>>>>
>>>>>>>>>
>>>>>>>> ok
>>>>>>>>
>>>>>>>>
>>>>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It
>>> has a
>>>>>>>>> good patch, although I think that the useBaseVersion should be
>>> 'true'
>>>>> by
>>>>>>>>> default. I can fix that today or tomorrow.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> ok let me know when it will be good on your side.
>>>>>>>>
>>>>>>>> thx
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>>
>>>>>>>>> Robert
>>>>>>>>>
>>>>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>>>>>>>>> stephen.alan.connolly@gmail.****com <stephen.alan.connolly@gmail.
>>>>> **com<st...@gmail.com>
>>>>>>>>>>> :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We should probably close MDEP-124 as WONT FIX given that there
>>> seems
>>>>> no
>>>>>>>>>
>>>>>>>>>> way
>>>>>>>>>> to fix it... or at least the addition of a configuration element
>>> to
>>>>>>>>>> allow
>>>>>>>>>> flagging specific dependencies as used even if they seem not.
>>>>>>>>>>
>>>>>>>>>> MDPE-166 also seems like it should just display a different output
>>>>> for
>>>>>>>>>> <scope>runtime</scope> namely something like "Unable to determine
>>>>>>>>>> whether
>>>>>>>>>> used or unused as scope is runtime"
>>>>>>>>>>
>>>>>>>>>> I think the above two "solutions" would be quick to implement and
>>>>> would
>>>>>>>>>> close the issues out.
>>>>>>>>>>
>>>>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org>
>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> i would like to release the dependency plugin soon.
>>>>>>>>>>> There only too old issues not closed attached to the current
>>>>> version
>>>>>>>>>>> (
>>>>>>>>>>>
>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
>>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>>>>>>>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>>>>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>>>>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
>>>>>
>>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> )
>>>>>>>>>>> but I suppose they are migrated release after release without any
>>>>> real
>>>>>>>>>>> work
>>>>>>>>>>> on them.
>>>>>>>>>>> I'm interested especially by this fix to use it as report (
>>>>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
>>>>> http://jira.codehaus.org/**browse/MDEP-366>
>>>>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
>>>>> http://jira.codehaus.org/browse/MDEP-366>
>>>>>>>>>>>> )
>>>>>>>>>>>
>>>>>>>>>>> and it has the perf improvement
>>>>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>>>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
>>>>> http://jira.codehaus.org/browse/MDEP-377>
>>>>>>>>>>>> )
>>>>>>>>>>>
>>>>>>>>>>> Nobody against it ?
>>>>>>>>>>>
>>>>>>>>>>> Cheers
>>>>>>>>>>>
>>>>>>>>>>> -----
>>>>>>>>>>> Arnaud Héritier
>>>>>>>>>>> http://aheritier.net
>>>>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> ------------------------------****----------------------------**
>>>>>>>>> --**---------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>>>>>>>>> dev-unsubscribe@maven.**apache.org <
>>> dev-unsubscribe@maven.apache.org
>>>>>>>
>>>>>>>>>
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>> ------------------------------**------------------------------**---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
>>>>> dev-unsubscribe@maven.apache.org>
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> -----
>> Arnaud Héritier
>> 06-89-76-64-24
>> http://aheritier.net
>> Mail/GTalk: aheritier@gmail.com
>> Twitter/Skype : aheritier
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
FYI, I will need to release also maven-dependency-analyzer
I need to check its status
Also 3 ITs added by Paul this WE are failing on my laptop. I will study if
I have an environment issue of if this is a problem in ITs or the code
cheers
On Mon, Oct 22, 2012 at 9:45 AM, Arnaud Héritier <ah...@gmail.com>wrote:
> no problem, you're doing the harder work :-)
> I'll launch the release process today.
> I hope to not have too many glitches as I didn't do that for a (too) long
> time..
>
> Arnaud
>
>
>
> On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
>
>> Ok, I'm done working on the purge-local-repositories goal for now,
>> thanks for waiting for me.
>>
>> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
>> > Hi Paul,
>> >
>> > Yes no problem I can do it tomorrow or this week end.
>> > I just would like to have it out before the end of next week
>> >
>> > Cheers,
>> >
>> > Arnaud
>> >
>> > On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
>> >
>> >> Hi Arnaud,
>> >>
>> >> Can you hold off one more day? I have a couple of fixes I want to get
>> >> in, and I want to do a bit more testing.
>> >>
>> >> Thanks!
>> >>
>> >> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
>> >>> ok thx.
>> >>> I'll do the release tomorrow
>> >>>
>> >>> Arnaud
>> >>>
>> >>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <
>> rfscholte@apache.org
>> >>> wrote:
>> >>>
>> >>>> Ok, I'm ready
>> >>>>
>> >>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>> >>>> aheritier@gmail.com>:
>> >>>>
>> >>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
>> rfscholte@apache.org
>> >>>>>> wrote:
>> >>>>>
>> >>>>> Hi,
>> >>>>>>
>> >>>>>> I noticed that my MDEP-300 should be easy to fix, but I would need
>> to
>> >>>>>> write an IT with a custom packaging type.
>> >>>>>> That would probably take some time, so I'll pick that up for the
>> 2.7
>> >>>>>>
>> >>>>>>
>> >>>>> ok
>> >>>>>
>> >>>>>
>> >>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It
>> has a
>> >>>>>> good patch, although I think that the useBaseVersion should be
>> 'true'
>> >> by
>> >>>>>> default. I can fix that today or tomorrow.
>> >>>>>>
>> >>>>>>
>> >>>>> ok let me know when it will be good on your side.
>> >>>>>
>> >>>>> thx
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>> thanks,
>> >>>>>>
>> >>>>>> Robert
>> >>>>>>
>> >>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>> >>>>>> stephen.alan.connolly@gmail.****com <stephen.alan.connolly@gmail.
>> >> **com<st...@gmail.com>
>> >>>>>>>> :
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> We should probably close MDEP-124 as WONT FIX given that there
>> seems
>> >> no
>> >>>>>>
>> >>>>>>> way
>> >>>>>>> to fix it... or at least the addition of a configuration element
>> to
>> >>>>>>> allow
>> >>>>>>> flagging specific dependencies as used even if they seem not.
>> >>>>>>>
>> >>>>>>> MDPE-166 also seems like it should just display a different output
>> >> for
>> >>>>>>> <scope>runtime</scope> namely something like "Unable to determine
>> >>>>>>> whether
>> >>>>>>> used or unused as scope is runtime"
>> >>>>>>>
>> >>>>>>> I think the above two "solutions" would be quick to implement and
>> >> would
>> >>>>>>> close the issues out.
>> >>>>>>>
>> >>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org>
>> >> wrote:
>> >>>>>>>
>> >>>>>>> Hi all,
>> >>>>>>>
>> >>>>>>>>
>> >>>>>>>> i would like to release the dependency plugin soon.
>> >>>>>>>> There only too old issues not closed attached to the current
>> >> version
>> >>>>>>>> (
>> >>>>>>>>
>> >>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
>> >> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>> >>>>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>> >>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>> >>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
>> >>
>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>> >>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>> )
>> >>>>>>>> but I suppose they are migrated release after release without any
>> >> real
>> >>>>>>>> work
>> >>>>>>>> on them.
>> >>>>>>>> I'm interested especially by this fix to use it as report (
>> >>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
>> >> http://jira.codehaus.org/**browse/MDEP-366>
>> >>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
>> >> http://jira.codehaus.org/browse/MDEP-366>
>> >>>>>>>>> )
>> >>>>>>>>
>> >>>>>>>> and it has the perf improvement
>> >>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>> >>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
>> >> http://jira.codehaus.org/browse/MDEP-377>
>> >>>>>>>>> )
>> >>>>>>>>
>> >>>>>>>> Nobody against it ?
>> >>>>>>>>
>> >>>>>>>> Cheers
>> >>>>>>>>
>> >>>>>>>> -----
>> >>>>>>>> Arnaud Héritier
>> >>>>>>>> http://aheritier.net
>> >>>>>>>> Mail/GTalk: aheritier@gmail.com
>> >>>>>>>> Twitter/Skype : aheritier
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>> ------------------------------****----------------------------**
>> >>>>>> --**---------
>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>> >>>>>> dev-unsubscribe@maven.**apache.org <
>> dev-unsubscribe@maven.apache.org
>> >>>>
>> >>>>>>
>> >>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>
>> ------------------------------**------------------------------**---------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
>> >> dev-unsubscribe@maven.apache.org>
>> >>>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: dev-help@maven.apache.org
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
no problem, you're doing the harder work :-)
I'll launch the release process today.
I hope to not have too many glitches as I didn't do that for a (too) long
time..
Arnaud
On Mon, Oct 22, 2012 at 6:25 AM, Paul Gier <pg...@redhat.com> wrote:
> Ok, I'm done working on the purge-local-repositories goal for now,
> thanks for waiting for me.
>
> On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
> > Hi Paul,
> >
> > Yes no problem I can do it tomorrow or this week end.
> > I just would like to have it out before the end of next week
> >
> > Cheers,
> >
> > Arnaud
> >
> > On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
> >
> >> Hi Arnaud,
> >>
> >> Can you hold off one more day? I have a couple of fixes I want to get
> >> in, and I want to do a bit more testing.
> >>
> >> Thanks!
> >>
> >> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
> >>> ok thx.
> >>> I'll do the release tomorrow
> >>>
> >>> Arnaud
> >>>
> >>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <rfscholte@apache.org
> >>> wrote:
> >>>
> >>>> Ok, I'm ready
> >>>>
> >>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
> >>>> aheritier@gmail.com>:
> >>>>
> >>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <
> rfscholte@apache.org
> >>>>>> wrote:
> >>>>>
> >>>>> Hi,
> >>>>>>
> >>>>>> I noticed that my MDEP-300 should be easy to fix, but I would need
> to
> >>>>>> write an IT with a custom packaging type.
> >>>>>> That would probably take some time, so I'll pick that up for the 2.7
> >>>>>>
> >>>>>>
> >>>>> ok
> >>>>>
> >>>>>
> >>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It
> has a
> >>>>>> good patch, although I think that the useBaseVersion should be
> 'true'
> >> by
> >>>>>> default. I can fix that today or tomorrow.
> >>>>>>
> >>>>>>
> >>>>> ok let me know when it will be good on your side.
> >>>>>
> >>>>> thx
> >>>>>
> >>>>>
> >>>>>
> >>>>>> thanks,
> >>>>>>
> >>>>>> Robert
> >>>>>>
> >>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
> >>>>>> stephen.alan.connolly@gmail.****com <stephen.alan.connolly@gmail.
> >> **com<st...@gmail.com>
> >>>>>>>> :
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> We should probably close MDEP-124 as WONT FIX given that there
> seems
> >> no
> >>>>>>
> >>>>>>> way
> >>>>>>> to fix it... or at least the addition of a configuration element to
> >>>>>>> allow
> >>>>>>> flagging specific dependencies as used even if they seem not.
> >>>>>>>
> >>>>>>> MDPE-166 also seems like it should just display a different output
> >> for
> >>>>>>> <scope>runtime</scope> namely something like "Unable to determine
> >>>>>>> whether
> >>>>>>> used or unused as scope is runtime"
> >>>>>>>
> >>>>>>> I think the above two "solutions" would be quick to implement and
> >> would
> >>>>>>> close the issues out.
> >>>>>>>
> >>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org>
> >> wrote:
> >>>>>>>
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>>>
> >>>>>>>> i would like to release the dependency plugin soon.
> >>>>>>>> There only too old issues not closed attached to the current
> >> version
> >>>>>>>> (
> >>>>>>>>
> >>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
> >> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
> >>>>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
> >>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
> >>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
> >>
> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> >>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> )
> >>>>>>>> but I suppose they are migrated release after release without any
> >> real
> >>>>>>>> work
> >>>>>>>> on them.
> >>>>>>>> I'm interested especially by this fix to use it as report (
> >>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
> >> http://jira.codehaus.org/**browse/MDEP-366>
> >>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
> >> http://jira.codehaus.org/browse/MDEP-366>
> >>>>>>>>> )
> >>>>>>>>
> >>>>>>>> and it has the perf improvement
> >>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
> >>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
> >> http://jira.codehaus.org/browse/MDEP-377>
> >>>>>>>>> )
> >>>>>>>>
> >>>>>>>> Nobody against it ?
> >>>>>>>>
> >>>>>>>> Cheers
> >>>>>>>>
> >>>>>>>> -----
> >>>>>>>> Arnaud Héritier
> >>>>>>>> http://aheritier.net
> >>>>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>>>> Twitter/Skype : aheritier
> >>>>>>>>
> >>>>>>>>
> >>>>>>> ------------------------------****----------------------------**
> >>>>>> --**---------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
> >>>>>> dev-unsubscribe@maven.**apache.org <
> dev-unsubscribe@maven.apache.org
> >>>>
> >>>>>>
> >>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> ------------------------------**------------------------------**---------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
> >> dev-unsubscribe@maven.apache.org>
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
Ok, I'm done working on the purge-local-repositories goal for now,
thanks for waiting for me.
On 10/18/2012 02:31 AM, Arnaud Héritier wrote:
> Hi Paul,
>
> Yes no problem I can do it tomorrow or this week end.
> I just would like to have it out before the end of next week
>
> Cheers,
>
> Arnaud
>
> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
>
>> Hi Arnaud,
>>
>> Can you hold off one more day? I have a couple of fixes I want to get
>> in, and I want to do a bit more testing.
>>
>> Thanks!
>>
>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
>>> ok thx.
>>> I'll do the release tomorrow
>>>
>>> Arnaud
>>>
>>> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <rfscholte@apache.org
>>> wrote:
>>>
>>>> Ok, I'm ready
>>>>
>>>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>>>> aheritier@gmail.com>:
>>>>
>>>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <rfscholte@apache.org
>>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> I noticed that my MDEP-300 should be easy to fix, but I would need to
>>>>>> write an IT with a custom packaging type.
>>>>>> That would probably take some time, so I'll pick that up for the 2.7
>>>>>>
>>>>>>
>>>>> ok
>>>>>
>>>>>
>>>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
>>>>>> good patch, although I think that the useBaseVersion should be 'true'
>> by
>>>>>> default. I can fix that today or tomorrow.
>>>>>>
>>>>>>
>>>>> ok let me know when it will be good on your side.
>>>>>
>>>>> thx
>>>>>
>>>>>
>>>>>
>>>>>> thanks,
>>>>>>
>>>>>> Robert
>>>>>>
>>>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>>>>>> stephen.alan.connolly@gmail.****com <stephen.alan.connolly@gmail.
>> **com<st...@gmail.com>
>>>>>>>> :
>>>>>>
>>>>>>
>>>>>>
>>>>>> We should probably close MDEP-124 as WONT FIX given that there seems
>> no
>>>>>>
>>>>>>> way
>>>>>>> to fix it... or at least the addition of a configuration element to
>>>>>>> allow
>>>>>>> flagging specific dependencies as used even if they seem not.
>>>>>>>
>>>>>>> MDPE-166 also seems like it should just display a different output
>> for
>>>>>>> <scope>runtime</scope> namely something like "Unable to determine
>>>>>>> whether
>>>>>>> used or unused as scope is runtime"
>>>>>>>
>>>>>>> I think the above two "solutions" would be quick to implement and
>> would
>>>>>>> close the issues out.
>>>>>>>
>>>>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org>
>> wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>>>
>>>>>>>> i would like to release the dependency plugin soon.
>>>>>>>> There only too old issues not closed attached to the current
>> version
>>>>>>>> (
>>>>>>>>
>>>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>>>>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>>>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>>>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> )
>>>>>>>> but I suppose they are migrated release after release without any
>> real
>>>>>>>> work
>>>>>>>> on them.
>>>>>>>> I'm interested especially by this fix to use it as report (
>>>>>>>> http://jira.codehaus.org/****browse/MDEP-366<
>> http://jira.codehaus.org/**browse/MDEP-366>
>>>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
>> http://jira.codehaus.org/browse/MDEP-366>
>>>>>>>>> )
>>>>>>>>
>>>>>>>> and it has the perf improvement
>>>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
>> http://jira.codehaus.org/browse/MDEP-377>
>>>>>>>>> )
>>>>>>>>
>>>>>>>> Nobody against it ?
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>>
>>>>>>>> -----
>>>>>>>> Arnaud Héritier
>>>>>>>> http://aheritier.net
>>>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>
>>>>>>>>
>>>>>>> ------------------------------****----------------------------**
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>>>>>> dev-unsubscribe@maven.**apache.org <dev-unsubscribe@maven.apache.org
>>>>
>>>>>>
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
>> dev-unsubscribe@maven.apache.org>
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
Hi
I saw many activity on the plugin this WE ( and I didn't have the time to
release it)
Paul, MDEP-290 and MDEP-272 are always in progress ?
Any ETA for them ?
Arnaud
On Thu, Oct 18, 2012 at 9:31 AM, Arnaud Héritier <ah...@gmail.com>wrote:
> Hi Paul,
>
> Yes no problem I can do it tomorrow or this week end.
> I just would like to have it out before the end of next week
>
> Cheers,
>
> Arnaud
>
>
> On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
>
>> Hi Arnaud,
>>
>> Can you hold off one more day? I have a couple of fixes I want to get
>> in, and I want to do a bit more testing.
>>
>> Thanks!
>>
>> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
>> > ok thx.
>> > I'll do the release tomorrow
>> >
>> > Arnaud
>> >
>> > On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <rfscholte@apache.org
>> >wrote:
>> >
>> >> Ok, I'm ready
>> >>
>> >> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>> >> aheritier@gmail.com>:
>> >>
>> >> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <rfscholte@apache.org
>> >>>> wrote:
>> >>>
>> >>> Hi,
>> >>>>
>> >>>> I noticed that my MDEP-300 should be easy to fix, but I would need to
>> >>>> write an IT with a custom packaging type.
>> >>>> That would probably take some time, so I'll pick that up for the 2.7
>> >>>>
>> >>>>
>> >>> ok
>> >>>
>> >>>
>> >>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has
>> a
>> >>>> good patch, although I think that the useBaseVersion should be
>> 'true' by
>> >>>> default. I can fix that today or tomorrow.
>> >>>>
>> >>>>
>> >>> ok let me know when it will be good on your side.
>> >>>
>> >>> thx
>> >>>
>> >>>
>> >>>
>> >>>> thanks,
>> >>>>
>> >>>> Robert
>> >>>>
>> >>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>> >>>> stephen.alan.connolly@gmail.****com <stephen.alan.connolly@gmail.
>> **com<st...@gmail.com>
>> >>>>>> :
>> >>>>
>> >>>>
>> >>>>
>> >>>> We should probably close MDEP-124 as WONT FIX given that there
>> seems no
>> >>>>
>> >>>>> way
>> >>>>> to fix it... or at least the addition of a configuration element to
>> >>>>> allow
>> >>>>> flagging specific dependencies as used even if they seem not.
>> >>>>>
>> >>>>> MDPE-166 also seems like it should just display a different output
>> for
>> >>>>> <scope>runtime</scope> namely something like "Unable to determine
>> >>>>> whether
>> >>>>> used or unused as scope is runtime"
>> >>>>>
>> >>>>> I think the above two "solutions" would be quick to implement and
>> would
>> >>>>> close the issues out.
>> >>>>>
>> >>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org>
>> wrote:
>> >>>>>
>> >>>>> Hi all,
>> >>>>>
>> >>>>>>
>> >>>>>> i would like to release the dependency plugin soon.
>> >>>>>> There only too old issues not closed attached to the current
>> version
>> >>>>>> (
>> >>>>>>
>> >>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>> >>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>> >>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>> >>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>> >
>> >>>>>>>
>> >>>>>>
>> >>>>>> )
>> >>>>>> but I suppose they are migrated release after release without any
>> real
>> >>>>>> work
>> >>>>>> on them.
>> >>>>>> I'm interested especially by this fix to use it as report (
>> >>>>>> http://jira.codehaus.org/****browse/MDEP-366<
>> http://jira.codehaus.org/**browse/MDEP-366>
>> >>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
>> http://jira.codehaus.org/browse/MDEP-366>
>> >>>>>>> )
>> >>>>>>
>> >>>>>> and it has the perf improvement
>> >>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>> >>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
>> http://jira.codehaus.org/browse/MDEP-377>
>> >>>>>>> )
>> >>>>>>
>> >>>>>> Nobody against it ?
>> >>>>>>
>> >>>>>> Cheers
>> >>>>>>
>> >>>>>> -----
>> >>>>>> Arnaud Héritier
>> >>>>>> http://aheritier.net
>> >>>>>> Mail/GTalk: aheritier@gmail.com
>> >>>>>> Twitter/Skype : aheritier
>> >>>>>>
>> >>>>>>
>> >>>>> ------------------------------****----------------------------**
>> >>>> --**---------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>> >>>> dev-unsubscribe@maven.**apache.org <dev-unsubscribe@maven.apache.org
>> >>
>> >>>>
>> >>>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >>
>> ------------------------------**------------------------------**---------
>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
>> dev-unsubscribe@maven.apache.org>
>> >> For additional commands, e-mail: dev-help@maven.apache.org
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
Hi Paul,
Yes no problem I can do it tomorrow or this week end.
I just would like to have it out before the end of next week
Cheers,
Arnaud
On Thu, Oct 18, 2012 at 5:06 AM, Paul Gier <pg...@redhat.com> wrote:
> Hi Arnaud,
>
> Can you hold off one more day? I have a couple of fixes I want to get
> in, and I want to do a bit more testing.
>
> Thanks!
>
> On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
> > ok thx.
> > I'll do the release tomorrow
> >
> > Arnaud
> >
> > On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <rfscholte@apache.org
> >wrote:
> >
> >> Ok, I'm ready
> >>
> >> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
> >> aheritier@gmail.com>:
> >>
> >> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <rfscholte@apache.org
> >>>> wrote:
> >>>
> >>> Hi,
> >>>>
> >>>> I noticed that my MDEP-300 should be easy to fix, but I would need to
> >>>> write an IT with a custom packaging type.
> >>>> That would probably take some time, so I'll pick that up for the 2.7
> >>>>
> >>>>
> >>> ok
> >>>
> >>>
> >>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
> >>>> good patch, although I think that the useBaseVersion should be 'true'
> by
> >>>> default. I can fix that today or tomorrow.
> >>>>
> >>>>
> >>> ok let me know when it will be good on your side.
> >>>
> >>> thx
> >>>
> >>>
> >>>
> >>>> thanks,
> >>>>
> >>>> Robert
> >>>>
> >>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
> >>>> stephen.alan.connolly@gmail.****com <stephen.alan.connolly@gmail.
> **com<st...@gmail.com>
> >>>>>> :
> >>>>
> >>>>
> >>>>
> >>>> We should probably close MDEP-124 as WONT FIX given that there seems
> no
> >>>>
> >>>>> way
> >>>>> to fix it... or at least the addition of a configuration element to
> >>>>> allow
> >>>>> flagging specific dependencies as used even if they seem not.
> >>>>>
> >>>>> MDPE-166 also seems like it should just display a different output
> for
> >>>>> <scope>runtime</scope> namely something like "Unable to determine
> >>>>> whether
> >>>>> used or unused as scope is runtime"
> >>>>>
> >>>>> I think the above two "solutions" would be quick to implement and
> would
> >>>>> close the issues out.
> >>>>>
> >>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org>
> wrote:
> >>>>>
> >>>>> Hi all,
> >>>>>
> >>>>>>
> >>>>>> i would like to release the dependency plugin soon.
> >>>>>> There only too old issues not closed attached to the current
> version
> >>>>>> (
> >>>>>>
> >>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<
> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
> >>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
> >>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
> >>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<
> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> >
> >>>>>>>
> >>>>>>
> >>>>>> )
> >>>>>> but I suppose they are migrated release after release without any
> real
> >>>>>> work
> >>>>>> on them.
> >>>>>> I'm interested especially by this fix to use it as report (
> >>>>>> http://jira.codehaus.org/****browse/MDEP-366<
> http://jira.codehaus.org/**browse/MDEP-366>
> >>>>>> <http://jira.**codehaus.org/browse/MDEP-366<
> http://jira.codehaus.org/browse/MDEP-366>
> >>>>>>> )
> >>>>>>
> >>>>>> and it has the perf improvement
> >>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
> >>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<
> http://jira.codehaus.org/browse/MDEP-377>
> >>>>>>> )
> >>>>>>
> >>>>>> Nobody against it ?
> >>>>>>
> >>>>>> Cheers
> >>>>>>
> >>>>>> -----
> >>>>>> Arnaud Héritier
> >>>>>> http://aheritier.net
> >>>>>> Mail/GTalk: aheritier@gmail.com
> >>>>>> Twitter/Skype : aheritier
> >>>>>>
> >>>>>>
> >>>>> ------------------------------****----------------------------**
> >>>> --**---------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
> >>>> dev-unsubscribe@maven.**apache.org <dev-unsubscribe@maven.apache.org
> >>
> >>>>
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>>>
> >>>
> >>
> ------------------------------**------------------------------**---------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<
> dev-unsubscribe@maven.apache.org>
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Paul Gier <pg...@redhat.com>.
Hi Arnaud,
Can you hold off one more day? I have a couple of fixes I want to get
in, and I want to do a bit more testing.
Thanks!
On 10/17/2012 01:34 AM, Arnaud Héritier wrote:
> ok thx.
> I'll do the release tomorrow
>
> Arnaud
>
> On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <rf...@apache.org>wrote:
>
>> Ok, I'm ready
>>
>> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
>> aheritier@gmail.com>:
>>
>> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <rfscholte@apache.org
>>>> wrote:
>>>
>>> Hi,
>>>>
>>>> I noticed that my MDEP-300 should be easy to fix, but I would need to
>>>> write an IT with a custom packaging type.
>>>> That would probably take some time, so I'll pick that up for the 2.7
>>>>
>>>>
>>> ok
>>>
>>>
>>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
>>>> good patch, although I think that the useBaseVersion should be 'true' by
>>>> default. I can fix that today or tomorrow.
>>>>
>>>>
>>> ok let me know when it will be good on your side.
>>>
>>> thx
>>>
>>>
>>>
>>>> thanks,
>>>>
>>>> Robert
>>>>
>>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>>>> stephen.alan.connolly@gmail.****com <st...@gmail.com>
>>>>>> :
>>>>
>>>>
>>>>
>>>> We should probably close MDEP-124 as WONT FIX given that there seems no
>>>>
>>>>> way
>>>>> to fix it... or at least the addition of a configuration element to
>>>>> allow
>>>>> flagging specific dependencies as used even if they seem not.
>>>>>
>>>>> MDPE-166 also seems like it should just display a different output for
>>>>> <scope>runtime</scope> namely something like "Unable to determine
>>>>> whether
>>>>> used or unused as scope is runtime"
>>>>>
>>>>> I think the above two "solutions" would be quick to implement and would
>>>>> close the issues out.
>>>>>
>>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>>>
>>>>>> i would like to release the dependency plugin soon.
>>>>>> There only too old issues not closed attached to the current version
>>>>>> (
>>>>>>
>>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel>
>>>>>>>
>>>>>>
>>>>>> )
>>>>>> but I suppose they are migrated release after release without any real
>>>>>> work
>>>>>> on them.
>>>>>> I'm interested especially by this fix to use it as report (
>>>>>> http://jira.codehaus.org/****browse/MDEP-366<http://jira.codehaus.org/**browse/MDEP-366>
>>>>>> <http://jira.**codehaus.org/browse/MDEP-366<http://jira.codehaus.org/browse/MDEP-366>
>>>>>>> )
>>>>>>
>>>>>> and it has the perf improvement
>>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<http://jira.codehaus.org/browse/MDEP-377>
>>>>>>> )
>>>>>>
>>>>>> Nobody against it ?
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> -----
>>>>>> Arnaud Héritier
>>>>>> http://aheritier.net
>>>>>> Mail/GTalk: aheritier@gmail.com
>>>>>> Twitter/Skype : aheritier
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>>>> dev-unsubscribe@maven.**apache.org <de...@maven.apache.org>>
>>>>
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
ok thx.
I'll do the release tomorrow
Arnaud
On Tue, Oct 16, 2012 at 11:31 PM, Robert Scholte <rf...@apache.org>wrote:
> Ok, I'm ready
>
> Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier <
> aheritier@gmail.com>:
>
> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <rfscholte@apache.org
>> >wrote:
>>
>> Hi,
>>>
>>> I noticed that my MDEP-300 should be easy to fix, but I would need to
>>> write an IT with a custom packaging type.
>>> That would probably take some time, so I'll pick that up for the 2.7
>>>
>>>
>> ok
>>
>>
>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
>>> good patch, although I think that the useBaseVersion should be 'true' by
>>> default. I can fix that today or tomorrow.
>>>
>>>
>> ok let me know when it will be good on your side.
>>
>> thx
>>
>>
>>
>>> thanks,
>>>
>>> Robert
>>>
>>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>>> stephen.alan.connolly@gmail.****com <st...@gmail.com>
>>> >>:
>>>
>>>
>>>
>>> We should probably close MDEP-124 as WONT FIX given that there seems no
>>>
>>>> way
>>>> to fix it... or at least the addition of a configuration element to
>>>> allow
>>>> flagging specific dependencies as used even if they seem not.
>>>>
>>>> MDPE-166 also seems like it should just display a different output for
>>>> <scope>runtime</scope> namely something like "Unable to determine
>>>> whether
>>>> used or unused as scope is runtime"
>>>>
>>>> I think the above two "solutions" would be quick to implement and would
>>>> close the issues out.
>>>>
>>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org> wrote:
>>>>
>>>> Hi all,
>>>>
>>>>>
>>>>> i would like to release the dependency plugin soon.
>>>>> There only too old issues not closed attached to the current version
>>>>> (
>>>>>
>>>>> http://jira.codehaus.org/****browse/MDEP#selectedTab=com.**<http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**>
>>>>> atlassian.jira.plugin.system.****project%3Aroadmap-panel<http:**
>>>>> //jira.codehaus.org/browse/**MDEP#selectedTab=com.**
>>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel>
>>>>> >
>>>>>
>>>>> )
>>>>> but I suppose they are migrated release after release without any real
>>>>> work
>>>>> on them.
>>>>> I'm interested especially by this fix to use it as report (
>>>>> http://jira.codehaus.org/****browse/MDEP-366<http://jira.codehaus.org/**browse/MDEP-366>
>>>>> <http://jira.**codehaus.org/browse/MDEP-366<http://jira.codehaus.org/browse/MDEP-366>
>>>>> >)
>>>>>
>>>>> and it has the perf improvement
>>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>>> browse/MDEP-377 <http://jira.codehaus.org/**browse/MDEP-377<http://jira.codehaus.org/browse/MDEP-377>
>>>>> >)
>>>>>
>>>>> Nobody against it ?
>>>>>
>>>>> Cheers
>>>>>
>>>>> -----
>>>>> Arnaud Héritier
>>>>> http://aheritier.net
>>>>> Mail/GTalk: aheritier@gmail.com
>>>>> Twitter/Skype : aheritier
>>>>>
>>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
>>> dev-unsubscribe@maven.**apache.org <de...@maven.apache.org>>
>>>
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Robert Scholte <rf...@apache.org>.
Ok, I'm ready
Op Tue, 16 Oct 2012 19:07:29 +0200 schreef Arnaud Héritier
<ah...@gmail.com>:
> On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte
> <rf...@apache.org>wrote:
>
>> Hi,
>>
>> I noticed that my MDEP-300 should be easy to fix, but I would need to
>> write an IT with a custom packaging type.
>> That would probably take some time, so I'll pick that up for the 2.7
>>
>
> ok
>
>
>> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
>> good patch, although I think that the useBaseVersion should be 'true' by
>> default. I can fix that today or tomorrow.
>>
>
> ok let me know when it will be good on your side.
>
> thx
>
>
>>
>> thanks,
>>
>> Robert
>>
>> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
>> stephen.alan.connolly@gmail.**com <st...@gmail.com>>:
>>
>>
>> We should probably close MDEP-124 as WONT FIX given that there seems no
>>> way
>>> to fix it... or at least the addition of a configuration element to
>>> allow
>>> flagging specific dependencies as used even if they seem not.
>>>
>>> MDPE-166 also seems like it should just display a different output for
>>> <scope>runtime</scope> namely something like "Unable to determine
>>> whether
>>> used or unused as scope is runtime"
>>>
>>> I think the above two "solutions" would be quick to implement and would
>>> close the issues out.
>>>
>>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org> wrote:
>>>
>>> Hi all,
>>>>
>>>> i would like to release the dependency plugin soon.
>>>> There only too old issues not closed attached to the current
>>>> version (
>>>>
>>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**
>>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel>
>>>> )
>>>> but I suppose they are migrated release after release without any real
>>>> work
>>>> on them.
>>>> I'm interested especially by this fix to use it as report (
>>>> http://jira.codehaus.org/**browse/MDEP-366<http://jira.codehaus.org/browse/MDEP-366>)
>>>> and it has the perf improvement
>>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>>> browse/MDEP-377 <http://jira.codehaus.org/browse/MDEP-377>)
>>>> Nobody against it ?
>>>>
>>>> Cheers
>>>>
>>>> -----
>>>> Arnaud Héritier
>>>> http://aheritier.net
>>>> Mail/GTalk: aheritier@gmail.com
>>>> Twitter/Skype : aheritier
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail:
>> dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
On Tue, Oct 16, 2012 at 6:55 PM, Robert Scholte <rf...@apache.org>wrote:
> Hi,
>
> I noticed that my MDEP-300 should be easy to fix, but I would need to
> write an IT with a custom packaging type.
> That would probably take some time, so I'll pick that up for the 2.7
>
ok
> I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
> good patch, although I think that the useBaseVersion should be 'true' by
> default. I can fix that today or tomorrow.
>
ok let me know when it will be good on your side.
thx
>
> thanks,
>
> Robert
>
> Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly <
> stephen.alan.connolly@gmail.**com <st...@gmail.com>>:
>
>
> We should probably close MDEP-124 as WONT FIX given that there seems no
>> way
>> to fix it... or at least the addition of a configuration element to allow
>> flagging specific dependencies as used even if they seem not.
>>
>> MDPE-166 also seems like it should just display a different output for
>> <scope>runtime</scope> namely something like "Unable to determine whether
>> used or unused as scope is runtime"
>>
>> I think the above two "solutions" would be quick to implement and would
>> close the issues out.
>>
>> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org> wrote:
>>
>> Hi all,
>>>
>>> i would like to release the dependency plugin soon.
>>> There only too old issues not closed attached to the current version (
>>>
>>> http://jira.codehaus.org/**browse/MDEP#selectedTab=com.**
>>> atlassian.jira.plugin.system.**project%3Aroadmap-panel<http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel>
>>> )
>>> but I suppose they are migrated release after release without any real
>>> work
>>> on them.
>>> I'm interested especially by this fix to use it as report (
>>> http://jira.codehaus.org/**browse/MDEP-366<http://jira.codehaus.org/browse/MDEP-366>)
>>> and it has the perf improvement
>>> with the plexus-utils upgrade (http://jira.codehaus.org/**
>>> browse/MDEP-377 <http://jira.codehaus.org/browse/MDEP-377>)
>>> Nobody against it ?
>>>
>>> Cheers
>>>
>>> -----
>>> Arnaud Héritier
>>> http://aheritier.net
>>> Mail/GTalk: aheritier@gmail.com
>>> Twitter/Skype : aheritier
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Robert Scholte <rf...@apache.org>.
Hi,
I noticed that my MDEP-300 should be easy to fix, but I would need to
write an IT with a custom packaging type.
That would probably take some time, so I'll pick that up for the 2.7
I do like to add MDEP-380, a typical Maven3 + SNAPSHOT issue. It has a
good patch, although I think that the useBaseVersion should be 'true' by
default. I can fix that today or tomorrow.
thanks,
Robert
Op Tue, 16 Oct 2012 15:28:10 +0200 schreef Stephen Connolly
<st...@gmail.com>:
> We should probably close MDEP-124 as WONT FIX given that there seems no
> way
> to fix it... or at least the addition of a configuration element to allow
> flagging specific dependencies as used even if they seem not.
>
> MDPE-166 also seems like it should just display a different output for
> <scope>runtime</scope> namely something like "Unable to determine whether
> used or unused as scope is runtime"
>
> I think the above two "solutions" would be quick to implement and would
> close the issues out.
>
> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org> wrote:
>
>> Hi all,
>>
>> i would like to release the dependency plugin soon.
>> There only too old issues not closed attached to the current version (
>>
>> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
>> )
>> but I suppose they are migrated release after release without any real
>> work
>> on them.
>> I'm interested especially by this fix to use it as report (
>> http://jira.codehaus.org/browse/MDEP-366) and it has the perf
>> improvement
>> with the plexus-utils upgrade (http://jira.codehaus.org/browse/MDEP-377)
>> Nobody against it ?
>>
>> Cheers
>>
>> -----
>> Arnaud Héritier
>> http://aheritier.net
>> Mail/GTalk: aheritier@gmail.com
>> Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release of the dependency plugin 2.6
Posted by Arnaud Héritier <ah...@gmail.com>.
On Tue, Oct 16, 2012 at 3:28 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> We should probably close MDEP-124 as WONT FIX given that there seems no way
> to fix it... or at least the addition of a configuration element to allow
> flagging specific dependencies as used even if they seem not.
>
either we close it as WON't Fix or we reclassify it as enhancement and
we'll had some additionnal config entries to allow to ignore some deps
(more a workaround than a fix but a clean fix doesn't exist)
>
> MDPE-166 also seems like it should just display a different output for
> <scope>runtime</scope> namely something like "Unable to determine whether
> used or unused as scope is runtime"
>
I can have a look at it but if it's not solved since several years I think
it isn't so easy. I'm not sure we already filter dependencies by scope. I
need to check.
>
> I think the above two "solutions" would be quick to implement and would
> close the issues out.
>
> On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org> wrote:
>
> > Hi all,
> >
> > i would like to release the dependency plugin soon.
> > There only too old issues not closed attached to the current version (
> >
> >
> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> > )
> > but I suppose they are migrated release after release without any real
> work
> > on them.
> > I'm interested especially by this fix to use it as report (
> > http://jira.codehaus.org/browse/MDEP-366) and it has the perf
> improvement
> > with the plexus-utils upgrade (http://jira.codehaus.org/browse/MDEP-377)
> > Nobody against it ?
> >
> > Cheers
> >
> > -----
> > Arnaud Héritier
> > http://aheritier.net
> > Mail/GTalk: aheritier@gmail.com
> > Twitter/Skype : aheritier
> >
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: Release of the dependency plugin 2.6
Posted by Stephen Connolly <st...@gmail.com>.
We should probably close MDEP-124 as WONT FIX given that there seems no way
to fix it... or at least the addition of a configuration element to allow
flagging specific dependencies as used even if they seem not.
MDPE-166 also seems like it should just display a different output for
<scope>runtime</scope> namely something like "Unable to determine whether
used or unused as scope is runtime"
I think the above two "solutions" would be quick to implement and would
close the issues out.
On 16 October 2012 14:18, Arnaud HERITIER <ah...@apache.org> wrote:
> Hi all,
>
> i would like to release the dependency plugin soon.
> There only too old issues not closed attached to the current version (
>
> http://jira.codehaus.org/browse/MDEP#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> )
> but I suppose they are migrated release after release without any real work
> on them.
> I'm interested especially by this fix to use it as report (
> http://jira.codehaus.org/browse/MDEP-366) and it has the perf improvement
> with the plexus-utils upgrade (http://jira.codehaus.org/browse/MDEP-377)
> Nobody against it ?
>
> Cheers
>
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
>