<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;">Yes to all of you. Just one point and that is No matter what technical solution is done this kind of "cross-updating" that affects both side deserves mention on 5x5 but even then make QE aware of it with proposals to what part of devstudio should be given a hopeful quick test using the tp update from is.</div><div style="direction: inherit;"><br></div><div style="direction: inherit;">P.S. Paul/alexey, this situation is funny enough exactly the thing would rarely happen when talking about limits of the rPM approach. I.e. Users on rpm would not get this update. </div><div style="direction: inherit;"><br></div>/max<div><a href="https://about.me/maxandersen">https://about.me/maxandersen</a></div></div><div><br>On 26 Aug 2016, at 16:07, Alexey Kazakov <<a href="mailto:alkazako@redhat.com">alkazako@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<p>If it works for you guys then I would keep this update in the IS
TP only for Mars. And sure, it's needed to be tested if works fine
with JBDS when installed. <br>
</p>
Thanks.<br>
<br>
<div class="moz-cite-prefix">On 08/26/2016 06:53 AM, Aurelien Pupier
wrote:<br>
</div>
<blockquote cite="mid:CAFNb52cHZJv1L1+JjWn2Mjn-W-K14QXTpGonKB+Y-u1d2jeB6g@mail.gmail.com" type="cite">
<div dir="ltr">Hi,<br>
<br>
having it in the IS only is fine for me but keep it mind that
after Fuse Tooling is installed, the new plugin will be used by
all other JBDS plugins as the version will be higher.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Aug 26, 2016 at 3:46 PM, Nick
Boldt <span dir="ltr"><<a moz-do-not-send="true" href="mailto:nboldt@redhat.com" target="_blank">nboldt@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">If we need
to update the Mars TP, or simply add another child URL into<br>
the devstudio 9.x download site (which contains the m2e-wtp
update) we<br>
can do so. We could also add a connector to Central to
announce this<br>
patch/fix is available so everyone with JBT 4.3.x /
devstudio 9.x sees<br>
it.<br>
<br>
All I said was that no release was currently PLANNED.<br>
<br>
If we need to fix this for jbt 4.3 / devstudio 9.x (rather
than just<br>
fixing it in the IS releases), then that should be brought
to the 5x5<br>
call, and scheduled, so that PgM is aware of this need and
its impact<br>
on devsudio 10.x scheduling. I leave making such a decision
to<br>
project/program managers, and will react to any JIRAs of
sufficient<br>
urgency/priority should they cross my desk.<br>
<br>
TL;DR: "if you want it in jbosstools 4.3 / devstudio 9.x,
open a<br>
Trello card + JIRA issue w/ PgM approval".<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
On Fri, Aug 26, 2016 at 8:57 AM, Paul Leacu <<a moz-do-not-send="true" href="mailto:pleacu@redhat.com">pleacu@redhat.com</a>>
wrote:<br>
><br>
> Hey Max -<br>
> I think it's okay to add this to the IS TP
for Mars and then the core JBT TP for Neon. That<br>
> gives us both a near term solution to the issue
for Fuse Tooling and the correct long term solution.<br>
> QE should catch any base devstudio/ jbosstools
issues - I do appreciate the support!<br>
><br>
> --paull<br>
><br>
><br>
> ----- Original Message -----<br>
>> From: "Max Rydahl Andersen" <<a moz-do-not-send="true" href="mailto:manderse@redhat.com">manderse@redhat.com</a>><br>
>> To: "Nick Boldt" <<a moz-do-not-send="true" href="mailto:nboldt@redhat.com">nboldt@redhat.com</a>><br>
>> Cc: "Aurelien Pupier" <<a moz-do-not-send="true" href="mailto:apupier@redhat.com">apupier@redhat.com</a>>,
"Fred Bricon" <<a moz-do-not-send="true" href="mailto:fbricon@redhat.com">fbricon@redhat.com</a>>,
<a moz-do-not-send="true" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><wbr>,
"Paul<br>
>> Leacu" <<a moz-do-not-send="true" href="mailto:pleacu@redhat.com">pleacu@redhat.com</a>><br>
>> Sent: Thursday, August 25, 2016 7:16:10 PM<br>
>> Subject: Re: [jbosstools-dev] [m2e-wtp]
Workaround or new release or patched plugin?<br>
>><br>
>> On 25 Aug 2016, at 19:14, Nick Boldt wrote:<br>
>><br>
>> Some background: I sent Aurelien here when I
saw him mention he was<br>
>> pondering doing a feature patch<br>
>> and I said I'm sure we as maintainers of
m2e-wtp and the one including<br>
>> it in the base could do better than that.<br>
>><br>
>> > Just realized this is for Mars, not Neon.<br>
>> ><br>
>> > There's no plan to release a new devstudio
or jbosstools release for<br>
>> > Mars, so even if I update the TP that
won't automatically get into the<br>
>> > Integration Stack.<br>
>><br>
>> We always said JBoss Tools/Devstudio would
react to emergency releases<br>
>> if IS needs it.<br>
>> Thus saying a release is not planned then that
is not a valid reason if<br>
>> it is the only one.<br>
>><br>
>> Can we not do a basic TP update without a big
overhead ?<br>
>><br>
>> > Perhaps the better solution here is to
have Paul pull in the updated<br>
>> > bits to the IS TP.<br>
>><br>
>> Please remember that even if this is put into
the IS TP then it affects<br>
>> base devstudio and jbosstools too.<br>
>><br>
>> Thus some basic testing/verification would be
relevant for<br>
>> jbosstools/devstudio no matter<br>
>> if the update is put in base TP or in IS TP.<br>
>><br>
>> /max<br>
>><br>
>> > Paul, WDYT?<br>
>> ><br>
>> > On Thu, Aug 25, 2016 at 1:05 PM, Aurelien
Pupier <<a moz-do-not-send="true" href="mailto:apupier@redhat.com">apupier@redhat.com</a>><br>
>> > wrote:<br>
>> >> I created a new JIRA issue following
the pattern in the right<br>
>> >> project:<br>
>> >> <a moz-do-not-send="true" href="https://issues.jboss.org/browse/JBIDE-23044" rel="noreferrer" target="_blank">https://issues.jboss.org/<wbr>browse/JBIDE-23044</a><br>
>> >><br>
>> >> I still cannot assign the issue to
you.<br>
>> >><br>
>> >> On Thu, Aug 25, 2016 at 6:48 PM,
Aurelien Pupier <<a moz-do-not-send="true" href="mailto:apupier@redhat.com">apupier@redhat.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> Hi Nick,<br>
>> >>><br>
>> >>> thanks for the answer, I created a
JIRA for you but I don't have the<br>
>> >>> right<br>
>> >>> to assign it: <a moz-do-not-send="true" href="https://issues.jboss.org/browse/JBDS-4018" rel="noreferrer" target="_blank">https://issues.jboss.org/<wbr>browse/JBDS-4018</a><br>
>> >>><br>
>> >>> Please notice that it is for the
Mars-based Target Platform.<br>
>> >>><br>
>> >>> regards,<br>
>> >>><br>
>> >>> On Thu, Aug 25, 2016 at 6:31 PM,
Nick Boldt <<a moz-do-not-send="true" href="mailto:nboldt@redhat.com">nboldt@redhat.com</a>><br>
>> >>> wrote:<br>
>> >>>><br>
>> >>>> Standard process is:<br>
>> >>>><br>
>> >>>> a) open a JIRA, assigned to me<br>
>> >>>> b) ping me if I haven't
responded within a day or two, or if urgent<br>
>> >>>> c) if the issue is raised
BEFORE the target platform freeze (Aug<br>
>> >>>> 31)<br>
>> >>>> it can be resolved on/before
that date.<br>
>> >>>> d) if the issue is raised
after the target platform freeze, it<br>
>> >>>> requires escalation/approval
from Alexey as it jeopardizes the code<br>
>> >>>> freeze on Sept 1.<br>
>> >>>><br>
>> >>>> So the short answer is "I can
do it next week, on/before Aug 31,<br>
>> >>>> unless you need it sooner."<br>
>> >>>><br>
>> >>>> On Thu, Aug 25, 2016 at 10:33
AM, Fred Bricon <<a moz-do-not-send="true" href="mailto:fbricon@redhat.com">fbricon@redhat.com</a>><br>
>> >>>> wrote:<br>
>> >>>>> So we could cut a m2e-wtp
1.2.2 release, but you'd need to provide<br>
>> >>>>> a<br>
>> >>>>> patch<br>
>> >>>>> that doesn't use java 1.8.
I'll most likely be able to do it on<br>
>> >>>>> saturday or<br>
>> >>>>> monday. Then it depends
when can Nick mirror it<br>
>> >>>>><br>
>> >>>>> On Wed, Aug 24, 2016 at
6:59 PM, Aurelien Pupier<br>
>> >>>>> <<a moz-do-not-send="true" href="mailto:apupier@redhat.com">apupier@redhat.com</a>><br>
>> >>>>> wrote:<br>
>> >>>>>><br>
>> >>>>>> Hello all,<br>
>> >>>>>><br>
>> >>>>>> I hit this issue today<br>
>> >>>>>> <a moz-do-not-send="true" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=500197" rel="noreferrer" target="_blank">https://bugs.eclipse.org/bugs/<wbr>show_bug.cgi?id=500197</a><br>
>> >>>>>> "WTPProjectsUtil.<wbr>removeConflictingFacets(<wbr>IFacetedProject,<br>
>> >>>>>> IProjectFacetVersion,
Set<Action>) is not taking care of actions<br>
>> >>>>>> given<br>
>> >>>>>> as<br>
>> >>>>>> parameter"<br>
>> >>>>>> I provided a fix
proposal: <a moz-do-not-send="true" href="https://git.eclipse.org/r/#/c/79617/" rel="noreferrer" target="_blank">https://git.eclipse.org/r/#/c/<wbr>79617/</a><br>
>> >>>>>><br>
>> >>>>>> I detected it while
writing an integration test. While playing<br>
>> >>>>>> manually, i<br>
>> >>>>>> think that some jobs
are not played at the same time and it works<br>
>> >>>>>> *almost*<br>
>> >>>>>> every time.<br>
>> >>>>>><br>
>> >>>>>> I'm wondering if
someone has an idea for a workaround to this<br>
>> >>>>>> issue.<br>
>> >>>>>><br>
>> >>>>>> If not, is it possible
to create a new release? What is the<br>
>> >>>>>> timeframe<br>
>> >>>>>> for<br>
>> >>>>>> that? The goal is to
be able to use it in Fuse Tooling 8.0.0; The<br>
>> >>>>>> current<br>
>> >>>>>> code freeze date is
the 29th August (which is very very close).<br>
>> >>>>>> This<br>
>> >>>>>> version<br>
>> >>>>>> is based on JBDS 9.1
(Eclipse Mars)<br>
>> >>>>>><br>
>> >>>>>> If not possible, do
you have an idea of the impact of creating a<br>
>> >>>>>> patch<br>
>> >>>>>> plugin for
org.eclipse.m2e.wtp inside Fuse Tooling based on the<br>
>> >>>>>> content of<br>
>> >>>>>> provided gerrit change
proposal<br>
>> >>>>>> <a moz-do-not-send="true" href="https://git.eclipse.org/r/#/c/79617/" rel="noreferrer" target="_blank">https://git.eclipse.org/r/#/c/<wbr>79617/</a><br>
>> >>>>>> I'm aware that all
others JBDS and JBDIS features will be<br>
>> >>>>>> "affected"<br>
>> >>>>>> by<br>
>> >>>>>> this patched plugin if
Fuse Tooling is installed.<br>
>> >>>>>><br>
>> >>>>>> Regards,<br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>> --<br>
>> >>>>>> Aurelien Pupier<br>
>> >>>>>> Senior Software
Engineer in JBoss Fuse Tooling team<br>
>> >>>>>> @apupier<br>
>> >>>>>><br>
>> >>>>>>
______________________________<wbr>_________________<br>
>> >>>>>> jbosstools-dev mailing
list<br>
>> >>>>>> <a moz-do-not-send="true" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>> >>>>>> <a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/jbosstools-<wbr>dev</a><br>
>> >>>>><br>
>> >>>>><br>
>> >>>>><br>
>> >>>>>
______________________________<wbr>_________________<br>
>> >>>>> jbosstools-dev mailing
list<br>
>> >>>>> <a moz-do-not-send="true" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>> >>>>> <a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/jbosstools-<wbr>dev</a><br>
>> >>>><br>
>> >>>><br>
>> >>>><br>
>> >>>> --<br>
>> >>>> Nick Boldt :: JBoss by Red Hat<br>
>> >>>> Productization Lead :: JBoss
Tools & Dev Studio<br>
>> >>>> <a moz-do-not-send="true" href="http://nick.divbyzero.com" rel="noreferrer" target="_blank">http://nick.divbyzero.com</a><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> --<br>
>> >>> Aurelien Pupier<br>
>> >>> Senior Software Engineer in JBoss
Fuse Tooling team<br>
>> >>> @apupier<br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> Aurelien Pupier<br>
>> >> Senior Software Engineer in JBoss Fuse
Tooling team<br>
>> >> @apupier<br>
>> ><br>
>> > --<br>
>> > Nick Boldt :: JBoss by Red Hat<br>
>> > Productization Lead :: JBoss Tools &
Dev Studio<br>
>> > <a moz-do-not-send="true" href="http://nick.divbyzero.com" rel="noreferrer" target="_blank">http://nick.divbyzero.com</a><br>
>> > ______________________________<wbr>_________________<br>
>> > jbosstools-dev mailing list<br>
>> > <a moz-do-not-send="true" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>> > <a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/jbosstools-<wbr>dev</a><br>
>><br>
>><br>
>> /max<br>
>> <a moz-do-not-send="true" href="http://about.me/maxandersen" rel="noreferrer" target="_blank">http://about.me/maxandersen</a><br>
>><br>
<br>
<br>
<br>
--<br>
Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools & Dev Studio<br>
<a moz-do-not-send="true" href="http://nick.divbyzero.com" rel="noreferrer" target="_blank">http://nick.divbyzero.com</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Aurelien Pupier
<div>Senior Software Engineer in JBoss Fuse Tooling team</div>
<div>@apupier</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>jbosstools-dev mailing list</span><br><span><a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></span></div></blockquote></body></html>