please ignore my last reply - no one had responded to my request to add a 
backport and had missed that it was actually done (oh for an stable-rc 
changelog!)

On Thursday, 29 August 2013 23:22:35 UTC+1, Dominik Bartholdi wrote:
>
> Yeah, specially as this one is such an easy fix...
> But if we are not going to fix anything more, what are we waiting for with 
> the release?
>
> Am 29.08.2013 um 10:11 schrieb "Christoph Kutzinski" 
> <[email protected]<javascript:>
> >:
>
> I understand your pain. I've been waiting for a usable 1.509 LTS also for 
> some time.
> Luckily .3 seems now usable for me as we've recently switched completely 
> to maven 3.x
>   
> *Gesendet:* Donnerstag, 29. August 2013 um 05:06 Uhr
> *Von:* Domi <[email protected] <javascript:>>
> *An:* "[email protected] <javascript:>" <
> [email protected] <javascript:>>
> *Betreff:* Re: 1.509.3 RC1 posted
> Only with Maven 2.x...
> I understand, it's just because I'waiting for a usable version of this LTS 
> since its first release and every time there is another blocker for me. And 
> as we have to follow strict release cycles to get anything into production. 
> I'll have to wait another 3-4months months now :(
>
> Am 28.08.2013 um 23:53 schrieb Christoph Kutzinski <[email protected]<javascript:>
> >:
>
> > With 'only seen with maven2' you mean it's only happening with Maven 2.x 
> (and okay with Maven 3.x) or do you mean the maven2 job type?
> >
> > Am 28.08.2013 19:41, schrieb domi:
> >> Seems not to be the case...
> >> I have only seen it with maven2 - but unfortunately we do still have 
> many of them.
> >> ...
> >>
> >> On 28.08.2013, at 19:37, Jesse Glick <[email protected]<javascript:>> 
> wrote:
> >>
> >>> On Wed, Aug 28, 2013 at 1:25 PM, domi <[email protected] <javascript:>> 
> wrote:
> >>>> the logs are full with this:
> >>>> https://issues.jenkins-ci.org/browse/JENKINS-18441
> >>>
> >>> My understanding was that this bug was a regression well after 1.509.
> >>> But perhaps not; may be specific to Maven version, in which case
> >>> lts-candidate would be appropriate.
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google 
> Groups "Jenkins Developers" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>.
> >>> For more options, visit https://groups.google.com/groups/opt_out.
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>.
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/groups/opt_out.
>   
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to