-
Bug
-
Resolution: Done
-
Major
-
4.5.0.Final
-
None
-
devex #137 September 2017
-
10
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places.
Changes:
- MERGED jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272
- DONE job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that
- DONE job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb6accd6b83e1ba761b596
- DONE jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one:
JBDS-4440- https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff40566875d8506fce275d32a060 - DONE refactoring as per
JBDS-3894 - DONE documentation as per
JBIDE-23510
- is related to
-
JBIDE-22305 automate process for fetching latest target platform mirrors
-
- Closed
-
-
-
- Closed
-
-
JBDS-3894 Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio
-
- Closed
-
- relates to
-
-
- Closed
-
-
JBIDE-19911 Create a (manual) job to update a given 3rd-party project on TP
-
- Closed
-