[
https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-3191:
-------------------------------------------
No, the suggestion is:
Alice installs JBDS 8.0.0.Beta3 it will default include /updates/8.0 as updatesite since
declared in .product file and this updatesite will be empty. No magic needed in
p2.inf/feature.xml or .product.
during startup we lookup in ide.properties based on the version you are running and apply
settings defined in here. i.e. we could have property to define development sites and a
flag for wether they should be on or on. We could even ask the user during startup if he
wants to get updates to development content or not..and vice versa, if he ends up
upgrading to a GA and we can see he still have the list of sites from the development
property installed we can ask if he wants to continue receiving these updates or not - if
not, we clear out the development sites from his list of updatesites.
Meaning
* GA users will not see or be affecting of any of this. (only those actually running
development versions will see it)
* it does not matter what updatesite you got content from
* none of this affects the build time settings.
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
Fix For: 8.0.1.GA
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.8#6338)