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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBDS-3191:
-------------------------------------------

I'm not following your example Nick.

Why would it be bad if users continue to see the additonal updatesites in his install IFF he have been using developments build ?

The problem we have is that the -development/staging etc. sites is *always* added - but if we add the stable/released updatesite   and only add the -development site when users are running development versions I think we should be fine.

Yes, I complain about too many updatessites in here when they are *wrong*. If the user been running development versions he is expected to be okey getting more development content so there it is not a problem, and if a new user installs the stable one he will not get the development site so the list will be correct in both cases.

Is there a case where the list will be wrong/incorrect in this suggested approach ?

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