[jbosstools-issues] [JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

[Nick Boldt (JIRA)]

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

Nick Boldt updated JBIDE-19025:
-------------------------------
    Description: 
Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them.
This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/8.0/JBT42_Staging_For_QE.adoc#rebuild-target-platforms-for-central-and-early-access ), whereas this is a JBDS need.

So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS.

Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT.

  was:
Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them.
This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/8.0/JBT42_Staging_For_QE.adoc#rebuild-target-platforms-for-central-and-early-access ), whereas this is a JBDS need.

So we should split the content of Central/EA for JBT and JBDS, and have them separated in dinstinct .target: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS.

Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT.



> Separate JBT and JBDS Central and EA sites
> ------------------------------------------
>
>                 Key: JBIDE-19025
>                 URL: https://issues.jboss.org/browse/JBIDE-19025
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: discovery
>            Reporter: Mickael Istria
>
> Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them.
> This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/8.0/JBT42_Staging_For_QE.adoc#rebuild-target-platforms-for-central-and-early-access ), whereas this is a JBDS need.
> So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS.
> Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)