[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19025:
----------------------------------------
Another benefit is that currently, we're only validating the Central/EA .target against the jbosstools one, which doesn't guarantee anything about compatibility with JBDS. Splitting them would allow to have a real validation against JBDS TP.
> 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_gui... ), 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)
11 years, 3 months
[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19025:
------------------------------------
Seems to me too that if we're splitting JBT [discovery + central update] and JBDS [discovery + central update] we could migrate this content out of jbosstools-discovery and into jbdevstudio-product + jbosstools-build-sites.
> 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_gui... ), 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)
11 years, 3 months
[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19025:
------------------------------------
Since EA only contains things from JBT, there's no need to build it as a target platform. We can simplify by building it as a simple update site.
See JBIDE-18984.
> 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_gui... ), 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)
11 years, 3 months
[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
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_gui... ), 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_gui... ), 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_gui... ), 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)
11 years, 3 months
[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19025:
-------------------------------
Summary: Separate JBT and JBDS Central and EA sites (was: Separate JBT and JBDS discovery)
> 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_gui... ), 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.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months