Once I move the baselines from Neon to Oxygen [1], you'll start to see more errors like this, suggesting that a plugin or feature needs bumping to a higher version: [ERROR] Failed to execute goal org.eclipse.tycho.extras: tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.license.feature: Duplicate version but different content found for (org.jboss.tools.foundation. license.feature.feature.jar/1.4.0.v20170517-1834). Also exists in baseline, but its content is different. -> [Help 1] [ERROR] Failed to execute goal org.eclipse.tycho.extras: tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.jmx.core: Duplicate version but different content found for (org.jboss.tools.jmx.core/1.10.0.v20170719-1741). Also exists in baseline, but its content is different. -> [Help 1] But since I'll be on PTO next week Aug 12-20, I'll postpone this *big breaking change* until I'm back so there's more time to absorb the version bump requirements and avoid lots of red balls & Jenkins spam. [1] https://github.com/jbosstools/jbosstools-build/pull/259 On Fri, Aug 11, 2017 at 11:34 AM, Nick Boldt <nboldt(a)redhat.com&gt; wrote: > As you no doubt heard, master branch is unfrozen and dev of 4.5.1 / 11.1 > can start in earnest. Only 12 weeks until the next GA in October! > > I've automatically updated all your jbosstools-* project root poms to use > the new 4.5.1.AM1-SNAPSHOT parent pom. > > When you make changes to any plugins or features, make sure you bump the > plugins/features to a larger maintenance version. If you want to bump the > whole project, run something like this in your root folder: > > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:1.0.0:set-version -DnewVersion=3.4.1-SNAPSHOT > > Or if you want to bump a single plugin (and its containing feature) then > you'll have to run the above command that in the individual plugin and > feature folders. > > To verify your local changes will work, run like this: > > mvn clean verify -DskipBaselineComparison=false > > Not sure which version to increment to? Generally the rule is x.y.0 -> > x.y.1. But if you're already at x.y.100, you'll want to move to x.y.101 or > x.y.200. > > See also https://wiki.eclipse.org/Version_Numbering#When_to_change_ > the_service_segment > > Cheers, > > -- > > 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>