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

[Mickael Istria (JIRA)]

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

Mickael Istria edited comment on JBDS-3191 at 11/24/14 12:32 PM:
-----------------------------------------------------------------

{code}Eclipse is often described as being too slow (because of lots of background tasks and listeners). Do we really need to add another one to the pile, simply to work around having 2 (or 1) update sites listed in the Avail Software Sites list?{code}
Those jobs would be fully asynchronous, no listeners, I don't expect them to slow down startup or usage.
Also, doing additional computation to avoid people doing additional stuff is the exact purpose of a dev tools ;)

{code}What happens if Dave 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, then wants to try 8.1.0.Alpha1? If you removed the /8.0-development/ site, he'd have to re-add it even though he STARTED there, and is therefore a user who wants dev milestones.{code}
I believe it's acceptable to require an additional effort to test a dev milestone instead of requiring an additional effort to those who want to use the GA.

Or what if Edgar installs 8.0.0.GA from the /8.0-development/ site (because he's been following dev milestones, and used the same bookmarked URL instead of the /8.0/ one). Would you then remove his access to future milestones from /8.0-development because the com.jboss.devstudio.core plugin thinks that it's a GA verison, and assumes the the user therefore doesn't want milestones, only GA releases?




was (Author: nickboldt):
Sounds a bit like using a nuclear warhead to kill a mosquito... Eclipse is often described as being too slow (because of lots of background tasks and listeners). Do we really need to add another one to the pile, simply to work around having 2 (or 1) update sites listed in the Avail Software Sites list?

What happens if Dave 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, then wants to try 8.1.0.Alpha1? If you removed the /8.0-development/ site, he'd have to re-add it even though he STARTED there, and is therefore a user who wants dev milestones.

Or what if Edgar installs 8.0.0.GA from the /8.0-development/ site (because he's been following dev milestones, and used the same bookmarked URL instead of the /8.0/ one). Would you then remove his access to future milestones from /8.0-development because the com.jboss.devstudio.core plugin thinks that it's a GA verison, and assumes the the user therefore doesn't want milestones, only GA releases?



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