[
https://issues.jboss.org/browse/JBIDE-24010?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-24010:
------------------------------------------
[~nickboldt] [~jeffmaury] in the jbosstools-4.4.x branch o.j.t.openshift.client and
o.j.t.openshift.core changed and thus need to be bumped. As consequence the
o.j.t.openshift.feature then also had to get bumped.
Maven expects me to explicitly state the plugin version in the pom, too since it would
otherwise complain about the 3.3.2-SNAPSHOT version it would inherit from parent. Annoying
and error-prone, but so be it.
Nevertheless, the baseline check now still complains about
o.j.t.openshift.egit.integration.feature because - as it states it - that the source
feature changed but has the same version:
https://github.com/jbosstools/jbosstools-openshift/pull/1432#issuecomment...
Can you please enlighten me?
build: bump plugin version to comply with baseline check
--------------------------------------------------------
Key: JBIDE-24010
URL:
https://issues.jboss.org/browse/JBIDE-24010
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.0.AM1
Reporter: Nick Boldt
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 4.4.4.AM1, 4.5.0.AM1
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: 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.openshift.client: Version have moved backwards for
(org.jboss.tools.openshift.client/3.3.2.AM1-v20170224-1533-B1868).
Baseline has 3.3.2.Final-v20170217-1414-B33) with delta: 0.0.0
{code} --
https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
Solution: upversion your client plugin or make it not use the BUILD_ALIAS in its version
(so it's only got a timestamp).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)