[jbosstools-issues] [JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
Nick Boldt (JIRA)
issues at jboss.org
Fri Jan 30 08:59:49 EST 2015
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-19025:
-------------------------------
Affects Version/s: 4.2.2.Final
> 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
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Fix For: 4.3.0.Alpha1
>
>
> 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)
More information about the jbosstools-issues
mailing list