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

Nick Boldt (JIRA) issues at jboss.org
Wed Apr 22 12:14:33 EDT 2015


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

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

[~fbricon] I'll need you help w/ this some time. Need a mechanism to make JBDS see *jboss.discovery.site.url* as the site from which to pull updates, rather than the hardcoded  https://devstudio.redhat.com/9.0/stable/updates/. But only for development milestones. 

Probably want the same functionality in JBT too -- again, only for pre-GA milestones.

Currently we force this value into JBDS via https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/associate.properties#L4 but in future we could remove this and have it loaded entirely from *jboss.discovery.site.url* instead. 

> 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
>            Assignee: Fred Bricon
>             Fix For: 9.0.0.Beta1
>
>
> 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.15#6346)


More information about the jbosstools-issues mailing list