Hey Max -
I think it's okay to add this to the IS TP for Mars and then the core JBT TP
for Neon. That
gives us both a near term solution to the issue for Fuse Tooling and the correct long
term solution.
QE should catch any base devstudio/ jbosstools issues - I do appreciate the support!
--paull
----- Original Message -----
From: "Max Rydahl Andersen" <manderse(a)redhat.com>
To: "Nick Boldt" <nboldt(a)redhat.com>
Cc: "Aurelien Pupier" <apupier(a)redhat.com>, "Fred Bricon"
<fbricon(a)redhat.com>, jbosstools-dev(a)lists.jboss.org, "Paul
Leacu" <pleacu(a)redhat.com>
Sent: Thursday, August 25, 2016 7:16:10 PM
Subject: Re: [jbosstools-dev] [m2e-wtp] Workaround or new release or patched plugin?
On 25 Aug 2016, at 19:14, Nick Boldt wrote:
Some background: I sent Aurelien here when I saw him mention he was
pondering doing a feature patch
and I said I'm sure we as maintainers of m2e-wtp and the one including
it in the base could do better than that.
> Just realized this is for Mars, not Neon.
>
> There's no plan to release a new devstudio or jbosstools release for
> Mars, so even if I update the TP that won't automatically get into the
> Integration Stack.
We always said JBoss Tools/Devstudio would react to emergency releases
if IS needs it.
Thus saying a release is not planned then that is not a valid reason if
it is the only one.
Can we not do a basic TP update without a big overhead ?
> Perhaps the better solution here is to have Paul pull in the updated
> bits to the IS TP.
Please remember that even if this is put into the IS TP then it affects
base devstudio and jbosstools too.
Thus some basic testing/verification would be relevant for
jbosstools/devstudio no matter
if the update is put in base TP or in IS TP.
/max
> Paul, WDYT?
>
> On Thu, Aug 25, 2016 at 1:05 PM, Aurelien Pupier <apupier(a)redhat.com>
> wrote:
>> I created a new JIRA issue following the pattern in the right
>> project:
>>
https://issues.jboss.org/browse/JBIDE-23044
>>
>> I still cannot assign the issue to you.
>>
>> On Thu, Aug 25, 2016 at 6:48 PM, Aurelien Pupier <apupier(a)redhat.com>
>> wrote:
>>>
>>> Hi Nick,
>>>
>>> thanks for the answer, I created a JIRA for you but I don't have the
>>> right
>>> to assign it:
https://issues.jboss.org/browse/JBDS-4018
>>>
>>> Please notice that it is for the Mars-based Target Platform.
>>>
>>> regards,
>>>
>>> On Thu, Aug 25, 2016 at 6:31 PM, Nick Boldt <nboldt(a)redhat.com>
>>> wrote:
>>>>
>>>> Standard process is:
>>>>
>>>> a) open a JIRA, assigned to me
>>>> b) ping me if I haven't responded within a day or two, or if urgent
>>>> c) if the issue is raised BEFORE the target platform freeze (Aug
>>>> 31)
>>>> it can be resolved on/before that date.
>>>> d) if the issue is raised after the target platform freeze, it
>>>> requires escalation/approval from Alexey as it jeopardizes the code
>>>> freeze on Sept 1.
>>>>
>>>> So the short answer is "I can do it next week, on/before Aug 31,
>>>> unless you need it sooner."
>>>>
>>>> On Thu, Aug 25, 2016 at 10:33 AM, Fred Bricon
<fbricon(a)redhat.com>
>>>> wrote:
>>>>> So we could cut a m2e-wtp 1.2.2 release, but you'd need to
provide
>>>>> a
>>>>> patch
>>>>> that doesn't use java 1.8. I'll most likely be able to do it
on
>>>>> saturday or
>>>>> monday. Then it depends when can Nick mirror it
>>>>>
>>>>> On Wed, Aug 24, 2016 at 6:59 PM, Aurelien Pupier
>>>>> <apupier(a)redhat.com>
>>>>> wrote:
>>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> I hit this issue today
>>>>>>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=500197
>>>>>> "WTPProjectsUtil.removeConflictingFacets(IFacetedProject,
>>>>>> IProjectFacetVersion, Set<Action>) is not taking care of
actions
>>>>>> given
>>>>>> as
>>>>>> parameter"
>>>>>> I provided a fix proposal:
https://git.eclipse.org/r/#/c/79617/
>>>>>>
>>>>>> I detected it while writing an integration test. While playing
>>>>>> manually, i
>>>>>> think that some jobs are not played at the same time and it
works
>>>>>> *almost*
>>>>>> every time.
>>>>>>
>>>>>> I'm wondering if someone has an idea for a workaround to
this
>>>>>> issue.
>>>>>>
>>>>>> If not, is it possible to create a new release? What is the
>>>>>> timeframe
>>>>>> for
>>>>>> that? The goal is to be able to use it in Fuse Tooling 8.0.0;
The
>>>>>> current
>>>>>> code freeze date is the 29th August (which is very very close).
>>>>>> This
>>>>>> version
>>>>>> is based on JBDS 9.1 (Eclipse Mars)
>>>>>>
>>>>>> If not possible, do you have an idea of the impact of creating
a
>>>>>> patch
>>>>>> plugin for org.eclipse.m2e.wtp inside Fuse Tooling based on the
>>>>>> content of
>>>>>> provided gerrit change proposal
>>>>>>
https://git.eclipse.org/r/#/c/79617/
>>>>>> I'm aware that all others JBDS and JBDIS features will be
>>>>>> "affected"
>>>>>> by
>>>>>> this patched plugin if Fuse Tooling is installed.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Aurelien Pupier
>>>>>> Senior Software Engineer in JBoss Fuse Tooling team
>>>>>> @apupier
>>>>>>
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev(a)lists.jboss.org
>>>>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>>
http://nick.divbyzero.com
>>>
>>>
>>>
>>>
>>> --
>>> Aurelien Pupier
>>> Senior Software Engineer in JBoss Fuse Tooling team
>>> @apupier
>>
>>
>>
>>
>> --
>> Aurelien Pupier
>> Senior Software Engineer in JBoss Fuse Tooling team
>> @apupier
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
>
http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen