[jbosstools-dev] m2e 1.6.2 RC1 and m2e 1.7.0 M1 are available

[Max Rydahl Andersen]

On 19 Aug 2015, at 23:14, Paul Leacu wrote:

> Hey Max -
>     I've got the updated JBTIS TP about ready to go.  I've mirrored 
> the m2e 1.6.2 and I'm picking
> up graphiti 0.13.0 from a mirror as well.  I'm trying to get the TP 
> put together so Brian can try
> building Switchyard tomorrow.  Then I should be able to handoff to QE 
> the JBDSIS 9.0.0.Alpha1 on
> Friday.  The TP changes are well marked and will definitely get 
> removed as soon as the 4.50.0 JBDS
> core TP is ready.
>
> Here's the Jira:
> https://issues.jboss.org/browse/JBTIS-472
> https://issues.jboss.org/browse/JBIDE-20384

Thanks Paul! That was the missing link :)

Good we found a way, but lets not make a habit of doing overrides in 
JBDS-IS TP.

Another example where if we had a fully automated way of doing 
updates/builds we could react
much faster and sane to these kind of things which no matter our good 
intentions will always pop up.

/max

>
> --paull
>
>
> ----- Original Message -----
>> From: "Max Rydahl Andersen" <manderse at redhat.com>
>> To: "Nick Boldt" <nboldt at redhat.com>
>> Cc: "Paul Leacu" <pleacu at redhat.com>, "Fred Bricon" 
>> <fbricon at gmail.com>, "jbosstools-dev"
>> <jbosstools-dev at lists.jboss.org>
>> Sent: Wednesday, August 19, 2015 4:58:44 PM
>> Subject: Re: [jbosstools-dev] m2e 1.6.2 RC1 and m2e 1.7.0 M1 are 
>> available
>>
>> On 19 Aug 2015, at 17:34, Nick Boldt wrote:
>>
>>> Yes, but we won't be updating our 4.50.0.CR1-SNPASHOT tp for another 
>>> 2
>>> weeks, in order to collect more Mars.1 (previously called Mars SR1)
>>> changes at the same time.
>>>
>>> Paul's agreed to simply pull the 1.6.2 bits into his TP directly
>>> (since he needs it for his Alpha release this week). He's already
>>> doing that w/ Graphiti 0.13, so it's no big whoop to do it for 
>>> another
>>> almost-in-Mars.1 project, too.
>>
>> eh..wat? did not see any notice about this m2e issue being related to
>> JBDS-IS ?
>>
>> In past having JBDS-IS duplicate/change core dependencies was a big
>> no-no
>> and are we sure this will actually work when running an 
>> update/install
>> on top ?
>>
>> Just seems it would be way simpler we respun our TP with the right 
>> bits
>> rather
>> than we have to remember to retract this from the JBTIS/JBDS-IS TP in
>> their next
>> update.
>>
>>> We can of course update it sooner / a few times, but less churn is
>>> better, unless you're worried that devs need to start using 
>>> something
>>> from Mars.1 SOONER than 2 weeks from now?
>>
>> well, you just mentioned JBDS-IS apparently needs it now not later ?
>>
>> /max
>> http://about.me/maxandersen
>>


/max
http://about.me/maxandersen