[jbosstools-issues] [JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26283: ------------------------------------ If we want to skip these issues for now and be forced to be more vigilant closer to GA, I can make Tycho report a warning instead of an error, eg., {code}[WARNING] Baseline and reactor have same fully qualified version, but with different content [WARNING] Baseline /home/nboldt/.m2/repository1/p2/osgi/bundle/org.jboss.tools.aesh.runtime/2.0.203.v20180614-0303/org.jboss.tools.aesh.runtime-2.0.203.v20180614-0303.jar and reactor /home/nboldt/tru/jbosstools-forge/plugins/org.jboss.tools.aesh.runtime/target/org.jboss.tools.aesh.runtime-2.0.203-SNAPSHOT.jar are made of different bytes {code} and the builds will be green again. I've also added some parent pom properties to support this override option. https://github.com/jbosstools/jbosstools-build/commit/1008598b14f9e8fe306... But I think when we start 4.10.0.AM1, we should NOT bump the parent pom version automatically for all the projects, as some may not actually have changes in that release. Better to wait until a Real Commit happens in master, and then move to new parent pom then. -- This message was sent by Atlassian JIRA (v7.5.0#75005)