[jbosstools-issues] [JBoss JIRA] (JBIDE-24772) Refactoring: eliminate devstudio target platform; reuse jbosstools target platform

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-24772:
-------------------------------
    Description: 
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

  was:
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
* 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-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



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)