Hello, I'm surprised that tycho m2e 0.9.0 is upgraded, in the previous release we released a 0.8.1 especially to avoid the 0.9.0 see https://issues.jboss.org/browse/FUSETOOLS-2353 regards, On Thu, Sep 7, 2017 at 4:13 PM, <nboldt(a)redhat.com&gt; wrote: > Here is a proposal for change(s) to the JBoss Tools / Red Hat JBoss > Developer Studio / Red Hat Central target platforms. > > Affected Versions: > > jbosstools 4.5.0.AM2 > devstudio 11.0.0.AM2 > > jbt/ds TPs 4.71.0.AM2-SNAPSHOT > central TPs 4.70.0.Final-SNAPSHOT > > Detail / Summary: > > Oxygen.1.RC3, Red Deer 2.0, Docker Tools 3.1.1, m2e.tycho 0.9.0, m2e > 1.8.1, Launchbar 2.1.2 and refactoring to remove jbdevstudio target > platform, now that it's identical to the jbosstools one > > Related JIRA(s): > > https://issues.jboss.org/browse/JBIDE-24939 (plus linked issues & sub > tasks) > > Pull Request(s): > > https://github.com/jbosstools/jbosstools-target-platforms/pull/275 - > Oxygen.1.RC3 > https://github.com/jbosstools/jbosstools-target-platforms/pull/274 - Red > Deer 2.0 / Docker Tools 3.1.1 > https://github.com/jbosstools/jbosstools-target-platforms/pull/272 - > Refactoring - remove jbdevstudio target platform > https://github.com/jbosstools/jbosstools-target-platforms/pull/271 - > m2e.tycho 0.9.0 > https://github.com/jbosstools/jbosstools-target-platforms/pull/270 - m2e > 1.8.1 > https://github.com/jbosstools/jbosstools-target-platforms/pull/269 - > Launchbar 2.1.2 > > p2diff Report(s): > > (will attach to JIRA when available) > > ---------- > > Please review the above changes, as they have been applied and are > building today. > > Once the target platform is built, jobs and parent pom will be updated to > point > TARGET_PLATFORM_VERSION_MAX at the new version, 4.71.0.AM2-SNAPSHOT. > > You can use the following to build & test the target platforms locally > against > your component(s). > > Build target-platform: > > cd /path/to/jbosstools-target-platforms > git fetch origin pull/<pull-request-number>/head && git checkout > FETCH_HEAD > # or, using hub for git > git checkout <pull-request-URL> > > mvn clean install -f jbosstools/multiple/pom.xml > > Then, to test the new multiple target platform against your component's > build: > > cd /path/to/your/jbosstools-component > > mvn clean verify -Dtpc.version=4.71.0.AM2-SNAPSHOT > -Dtpc.targetKind=multiple > > For Central, fetch sources from jbosstools-discovery, then build as above. > > ---------- > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- AURÉLIEN PUPIER SENIOR SOFTWARE ENGINEER, FUSE TOOLING Red Hat France <https://www.redhat.com/> apupier(a)redhat.com IM: apupier <https://red.ht/sig>

TP is now live in the parent pom and the jobs' configurations, using: -DTARGET_PLATFORM_VERSION_MAX=4.71.0.AM2-SNAPSHOT Here are the p2diffs, if you're curious what changed: https://issues.jboss.org/browse/JBIDE-24939?focusedCommentId=13461055& page=com.atlassian.jira.plugin.system.issuetabpanels: comment-tabpanel#comment-13461055 On Thu, Sep 7, 2017 at 1:16 PM, Nick Boldt <nboldt(a)redhat.com&gt; wrote: > I've reverted the update to 0.9.0 [1], and have also added this > additional change [2] suggested by Fred to move to the latest m2e.wtp 1.3.3: > > [1] https://issues.jboss.org/browse/JBIDE-24974 > [2] https://issues.jboss.org/browse/JBDS-4533 -> > https://github.com/jbosstools/jbosstools-target-platforms/pull/276 > > On Thu, Sep 7, 2017 at 10:00 AM, Aurélien Pupier <apupier(a)redhat.com&gt; > wrote: > >> Hello, >> >> I'm surprised that tycho m2e 0.9.0 is upgraded, in the previous release >> we released a 0.8.1 especially to avoid the 0.9.0 see >> https://issues.jboss.org/browse/FUSETOOLS-2353 >> >> regards, >> >> On Thu, Sep 7, 2017 at 4:13 PM, <nboldt(a)redhat.com&gt; wrote: >> >>> Here is a proposal for change(s) to the JBoss Tools / Red Hat JBoss >>> Developer Studio / Red Hat Central target platforms. >>> >>> Affected Versions: >>> >>> jbosstools 4.5.0.AM2 >>> devstudio 11.0.0.AM2 >>> >>> jbt/ds TPs 4.71.0.AM2-SNAPSHOT >>> central TPs 4.70.0.Final-SNAPSHOT >>> >>> Detail / Summary: >>> >>> Oxygen.1.RC3, Red Deer 2.0, Docker Tools 3.1.1, m2e.tycho 0.9.0, m2e >>> 1.8.1, Launchbar 2.1.2 and refactoring to remove jbdevstudio target >>> platform, now that it's identical to the jbosstools one >>> >>> Related JIRA(s): >>> >>> https://issues.jboss.org/browse/JBIDE-24939 (plus linked issues & sub >>> tasks) >>> >>> Pull Request(s): >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/275 - >>> Oxygen.1.RC3 >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/274 - >>> Red Deer 2.0 / Docker Tools 3.1.1 >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/272 - >>> Refactoring - remove jbdevstudio target platform >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/271 - >>> m2e.tycho 0.9.0 >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/270 - >>> m2e 1.8.1 >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/269 - >>> Launchbar 2.1.2 >>> >>> p2diff Report(s): >>> >>> (will attach to JIRA when available) >>> >>> ---------- >>> >>> Please review the above changes, as they have been applied and are >>> building today. >>> >>> Once the target platform is built, jobs and parent pom will be updated >>> to point >>> TARGET_PLATFORM_VERSION_MAX at the new version, 4.71.0.AM2-SNAPSHOT. >>> >>> You can use the following to build & test the target platforms locally >>> against >>> your component(s). >>> >>> Build target-platform: >>> >>> cd /path/to/jbosstools-target-platforms >>> git fetch origin pull/<pull-request-number>/head && git checkout >>> FETCH_HEAD >>> # or, using hub for git >>> git checkout <pull-request-URL> >>> >>> mvn clean install -f jbosstools/multiple/pom.xml >>> >>> Then, to test the new multiple target platform against your component's >>> build: >>> >>> cd /path/to/your/jbosstools-component >>> >>> mvn clean verify -Dtpc.version=4.71.0.AM2-SNAPSHOT >>> -Dtpc.targetKind=multiple >>> >>> For Central, fetch sources from jbosstools-discovery, then build as >>> above. >>> >>> ---------- >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >> >> >> >> -- >> >> AURÉLIEN PUPIER >> >> SENIOR SOFTWARE ENGINEER, FUSE TOOLING >> >> Red Hat France <https://www.redhat.com/> >> >> apupier(a)redhat.com IM: apupier >> <https://red.ht/sig> >> > > > > -- > > Nick Boldt > > Senior Software Engineer, RHCSA > > Productization Lead :: JBoss Tools & Dev Studio > > IM: @nickboldt / @nboldt / http://nick.divbyzero.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > @ @redhatnews <https://twitter.com/redhatnews> Red Hat > <https://www.facebook.com/RedHatInc> > -- Nick Boldt Senior Software Engineer, RHCSA Productization Lead :: JBoss Tools & Dev Studio IM: @nickboldt / @nboldt / http://nick.divbyzero.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @ @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.facebook.com/RedHatInc>