[
https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3191:
----------------------------------
Current flow:
Alphax: points at 8.0-development
Betax: points at 8.0-development
CRx: points at 8.0-development
*MANUAL CHANGE TO SWITCH properties files*
GA: points at 8.0, with p2.inf to remove any old refs to 8.0-development
Max's proposed flow:
Alphax: points at 8.0-development and empty 8.0
Betax: points at 8.0-development and empty 8.0
CRx: points at 8.0-development and empty 8.0
*MANUAL CHANGE TO SWITCH properties files*
GA: points at 8.0, with p2.inf to remove any old refs to 8.0-development
So in both cases there's a manual change required to switch pre-GA builds to include
the correct GA URL. I don't see how including an empty 8.0 in the list improves the
situation.
--
p2.inf works great *at install time only* to add/remove sites to the Available Software
Sites list in Eclipse.
If there's a way to do that *at plugin runtime* that's even better, because it can
happen to an existing JBDS install w/o having to first be updated. It could for example
ping /8.0/ looking for actual content (non-empty content*.xml files, with actual
children). But I don't know if you can have a plugin remove 8.0-development/ from the
list programmatically while Eclipse/JBDS is running.
Improve the way we switch between development and GA
----------------------------------------------------
Key: JBDS-3191
URL:
https://issues.jboss.org/browse/JBDS-3191
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: build
Reporter: Mickael Istria
JBDS-3190 has shown that there are too many changes to perform when willing to create a
GA candidate, and it's almost certain that we'll forever forget to change one or
some of them when switching between GA and development stream.
We need to improve that.
Changes are necessary in:
* features/com.jboss.devstudio.core/feature/p2.inf
* site/associate.properties
* results/pom.xml
As an alternative, I suggest that the final site be ALWAYS added to the referenced site,
even if it's empty. This has no cost for build nor user, and this would simplify a few
things here and there.
Also, instead of a p2.inf, we could think a a "startup" extension that would
add reference to development site in case qualifier for the feature doesn't contain
GA.
The property to the "current site" (GA or development) could be factorized in
JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of
associateSites.properties).
CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)