[jbosstools-issues] [JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022074#comment-13022074 ] 

Nick Boldt commented on JBDS-3191:
----------------------------------

If I understand the user stories correctly, you have:

Alice installs JBDS 8.0.0.Beta3, gets /updates/8.0/ and /updates/8.0-development/ because it's a development milestone.
Bob installs JBDS 8.0.0.GA, gets only /updates/8.0/ because it's a GA release.
Carol installs JBDS 8.0.0.Beta3, gets /updates/8.0/ and /updates/8.0-development/ because it's a development milestone. Then updates to GA and... keeps both? Loses 8.0-development?

How does the code that builds the p2.inf or feature.xml or .product file know to insert ONE or TWO URLs in there? 

How are you going to programmatically toggle the inclusion of the 8.0-development site based on BUILD_ALIAS=GA ?



> 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)