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 <herve.bout...@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 > <bimargul...@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 <aherit...@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 < > bimargul...@gmail.com > > >>> > > >>> wrote: > > >>>> On Wed, Oct 24, 2012 at 7:30 AM, Benson Margulies < > > >> > > >> bimargul...@gmail.com> > > >> > > >>>> wrote: > > >>>>> On Wed, Oct 24, 2012 at 4:57 AM, Arnaud Héritier < > aherit...@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.bout...@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-unsubscr...@maven.apache.org > > >>>>>>> For additional commands, e-mail: dev-h...@maven.apache.org > > >>>>>> > > >>>>>> -- > > >>>>>> ----- > > >>>>>> Arnaud Héritier > > >>>>>> 06-89-76-64-24 > > >>>>>> http://aheritier.net > > >>>>>> Mail/GTalk: aherit...@gmail.com > > >>>>>> Twitter/Skype : aheritier > > >>>> > > >>>> > --------------------------------------------------------------------- > > >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > >>>> For additional commands, e-mail: dev-h...@maven.apache.org > > >>> > > >>> -- > > >>> ----- > > >>> Arnaud Héritier > > >>> 06-89-76-64-24 > > >>> http://aheritier.net > > >>> Mail/GTalk: aherit...@gmail.com > > >>> Twitter/Skype : aheritier > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > >> For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- ----- Arnaud Héritier 06-89-76-64-24 http://aheritier.net Mail/GTalk: aherit...@gmail.com Twitter/Skype : aheritier
