[
https://issues.jboss.org/browse/JBIDE-16971?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-16971.
--------------------------------
Fix Version/s: 4.2.0.Beta2
Resolution: Done
This is working and has exposed a new problem, which I've now fixed by removing
openshift-java-client 2.3 from the JBT staging composite site:
https://github.com/jbosstools/jbosstools-download.jboss.org/commit/18db90...
The problem was that we've never tried to install EVERYTHING in the composite, only a
specific list of features which are included in the JBT Aggregate site's
"Abridged JBT" category.
So, we never noticed that openshift-java-client 2.3 and jbosstools-openshift 2.6 can't
be co-installed due to conflicting version deps.
Anyway, having removed the old stuff, the install now works:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
>= 8476
update installAndDisplayCompositeSiteContent.sh to use p2director
-list instead of hardcoded feature list
---------------------------------------------------------------------------------------------------------
Key: JBIDE-16971
URL:
https://issues.jboss.org/browse/JBIDE-16971
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Affects Versions: 4.2.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.2.0.Beta2
Currently, installAndDisplayCompositeSiteContent.sh requires a hardcoded list of
features, which means it breaks if a feature is removed (eg., o.j.t.gwt.feature).
Instead we should use the new functionality in directory.xml to fetch the complete list
of features/plugins and install everything.
See
https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal...
Note too that
https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal...
needs its doc updated on line 3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira