[
https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-24772:
-------------------------------
Description:
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can
eliminate one of them and simply reuse the same artifact in two places.
Changes:
* jbosstools-discovery repo - remove unneeded configuration / folders:
https://github.com/jbosstools/jbosstools-target-platforms/pull/272
* 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
** update releng/publish scripts to look for
https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2...
instead of jbdevstudiotarget-\*.zip: DONE in
https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* job(s) / release guide steps that rename/copy target platforms to staging / development
/ stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts:
DONE in
https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: DONE
in JBDS-4440 -
https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
* refactoring as per JBDS-3894
* documentation as per JBIDE-23510
was:
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can
eliminate one of them and simply reuse the same artifact in two places.
Changes:
* jbosstools-discovery repo - remove unneeded configuration / folders:
https://github.com/jbosstools/jbosstools-target-platforms/pull/272
* 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
** update releng/publish scripts to look for
https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2...
instead of jbdevstudiotarget-\*.zip
* job(s) / release guide steps that rename/copy target platforms to staging / development
/ stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts
* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one
* refactoring as per JBDS-3894
* documentation as per JBIDE-23510
Refactoring: eliminate devstudio target platform; reuse jbosstools
target platform
----------------------------------------------------------------------------------
Key: JBIDE-24772
URL:
https://issues.jboss.org/browse/JBIDE-24772
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, target-platform
Affects Versions: 4.5.0.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.5.1.AM2
Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can
eliminate one of them and simply reuse the same artifact in two places.
Changes:
* jbosstools-discovery repo - remove unneeded configuration / folders:
https://github.com/jbosstools/jbosstools-target-platforms/pull/272
* 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
** update releng/publish scripts to look for
https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2...
instead of jbdevstudiotarget-\*.zip: DONE in
https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* job(s) / release guide steps that rename/copy target platforms to staging / development
/ stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts:
DONE in
https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb...
* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one:
DONE in JBDS-4440 -
https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4...
* refactoring as per JBDS-3894
* documentation as per JBIDE-23510
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)