July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3085: ---------------------------------- {quote}Do we already allow to update between 8.0.0.GA and 8.1.0 in any way? if so, I think we already have answers for b and c. {quote} Yes but GA -> GA can be done from Help > Check for updates. This user story is "GA -> pre-GA" via JBoss Central > Software/Updates tab > [x] Enable Early Access > popup to confirm > select JBDS features > Install > Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access? > --------------------------------------------------------------------------- > > Key: JBDS-3085 > URL: https://issues.jboss.org/browse/JBDS-3085 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Max brought up a question on a call today: > *Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?* > This was supposedly in the original scope for the creation of a Early Access site, but I never saw that. So, in order to get some eyeballs on this idea, and to get buy-in from QE/doc/dev/PM/PgM/PL, I'm cc:'ing some people here so we can discuss the cons and cons of this idea. > cc: [~mmusaji] [~mmurray] [~mmalina] [~maxandersen] [~mickael_istria][~ldimaggio] [~burrsutter] [~jpallich] [~rruss] [~fbricon] > (Aside: has anyone noticed that there's an plethora of people with "M" names on this team?) > Things to consider: > a) what happens if an 8.0.0.GA user suddenly finds they've updated to an Alpha or Beta release? Can they uninstall? (Probably not, if they started with the installer; probably yes if they started from BYOE / Marketplace.) > b) how will GSS support these "I was on GA but not I'm on Beta" users? > c) What about project examples that might / might not be compatible between 8.0 and 8.x, eg., because of changes in Eclipse Luna or a new default runtime (EAP 6.3, 6.4) ? > d) what could possibly go wrong? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3086: ---------------------------------- Yes, the change would be to make updates/8.0 also include the latest Central TP in the composite, so that we don't need two different URLs for update vs. for Central discovery plugin. > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Today, the Central discovery plugin for JBDS is points to this URL: > https://devstudio.jboss.com/updates/8.0-staging/central/core/ > https://devstudio.jboss.com/updates/8.0-development/central/core/ > https://devstudio.jboss.com/updates/8.0/central/core/ > and for Early Access discovery: > https://devstudio.jboss.com/updates/8.0-staging/central/earlyaccess/ > https://devstudio.jboss.com/updates/8.0-development/central/earlyaccess/ > https://devstudio.jboss.com/updates/8.0/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17809) update site index.html lists duplicate entries when both jar and pack.gz artifacts are found

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17809?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17809: ------------------------------- Priority: Minor (was: Major) > update site index.html lists duplicate entries when both jar and pack.gz artifacts are found > -------------------------------------------------------------------------------------------- > > Key: JBIDE-17809 > URL: https://issues.jboss.org/browse/JBIDE-17809 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > > update site index.html lists duplicate entries when both jar and pack.gz artifacts are found > eg., look for `org.eclipse.jst.server_ui.feature` on > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3087) Consider new installer packages

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3087: -------------------------------- Summary: Consider new installer packages Key: JBDS-3087 URL: https://issues.jboss.org/browse/JBDS-3087 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: installer Affects Versions: 8.0.0.Beta2 Reporter: Nick Boldt Today we have two installers: * Stand-alone Installer (504M) * Installer with EAP (642M) Both can be used for offline install, but both are large downloads. When installing JBDS IS offline, a user must download several archives: * JBDS installer jar (or update site zip) * JBDS target platform zip * JBDS IS zip And, there's no "stub installer for online" which would simply fetch the content needed to do the install from the update site, making the installer a much smaller (initial) download footprint. Therefore Max has suggested that we might want to add two new installers, resulting in this list: * Stand-alone Installer (504M) * Installer with EAP (642M) * Installer with Integration Stack (~750M) * Stub Installer (~10M) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3086: -------------------------------------- Aren't the first set of URLs (updates/8.0) already taken by the actual content of JBDS 8.0 ? Is the suggestion to merge both site ? > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Today, the Central discovery plugin for JBDS is points to this URL: > https://devstudio.jboss.com/updates/8.0-staging/central/core/ > https://devstudio.jboss.com/updates/8.0-development/central/core/ > https://devstudio.jboss.com/updates/8.0/central/core/ > and for Early Access discovery: > https://devstudio.jboss.com/updates/8.0-staging/central/earlyaccess/ > https://devstudio.jboss.com/updates/8.0-development/central/earlyaccess/ > https://devstudio.jboss.com/updates/8.0/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17804) Missing Seam preference page when running on Java 6

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17804?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-17804: ------------------------------------- Assignee: Denis Golovin > Missing Seam preference page when running on Java 6 > --------------------------------------------------- > > Key: JBIDE-17804 > URL: https://issues.jboss.org/browse/JBIDE-17804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, seam2 > Affects Versions: 4.2.0.Beta3 > Environment: java-6-openjdk-amd64, Ubuntu 12.04 > Reporter: Radoslav Rábara > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > Seam preference page is missing when JBDS is running on Java 6. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17804) Missing Seam preference page when running on Java 6

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17804?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17804: --------------------------------------- JBDS does not support Java 6 anymore. > Missing Seam preference page when running on Java 6 > --------------------------------------------------- > > Key: JBIDE-17804 > URL: https://issues.jboss.org/browse/JBIDE-17804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, seam2 > Affects Versions: 4.2.0.Beta3 > Environment: java-6-openjdk-amd64, Ubuntu 12.04 > Reporter: Radoslav Rábara > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > Seam preference page is missing when JBDS is running on Java 6. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17804) Missing Seam preference page when running on Java 6

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17804?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-17804. ----------------------------------- Resolution: Won't Fix > Missing Seam preference page when running on Java 6 > --------------------------------------------------- > > Key: JBIDE-17804 > URL: https://issues.jboss.org/browse/JBIDE-17804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, seam2 > Affects Versions: 4.2.0.Beta3 > Environment: java-6-openjdk-amd64, Ubuntu 12.04 > Reporter: Radoslav Rábara > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > Seam preference page is missing when JBDS is running on Java 6. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17755) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JST]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17755?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-17755. --------------------------------- Resolution: Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JST] > ------------------------------------------------- > > Key: JBIDE-17755 > URL: https://issues.jboss.org/browse/JBIDE-17755 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [JST]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 > [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Beta3x > git push origin jbosstools-4.2.0.Beta3x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and > * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3085: -------------------------------------- Do we already allow to update between 8.0.0.GA and 8.1.0 in any way? if so, I think we already have answers for b and c. Some thoughts that make that thing complicated from a Central POV: * We'd need 2 different entries for in the catalog: 1 for installer and one for BYOB, as installer containes 1 extra-IU (the branded product) that we don't want in BYOE. Then we'd need to filter out one or the other depending on the target application (JBDS or Eclipse) * Since we'd still want the original feature, we'd need a "Downgrade" or "Restore" operation, as we don't want to uninstall JBDS. So this request would introduce new concepts that are not already available, it's not just a matter of adding a new JBDS to catalog. > Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access? > --------------------------------------------------------------------------- > > Key: JBDS-3085 > URL: https://issues.jboss.org/browse/JBDS-3085 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Max brought up a question on a call today: > *Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?* > This was supposedly in the original scope for the creation of a Early Access site, but I never saw that. So, in order to get some eyeballs on this idea, and to get buy-in from QE/doc/dev/PM/PgM/PL, I'm cc:'ing some people here so we can discuss the cons and cons of this idea. > cc: [~mmusaji] [~mmurray] [~mmalina] [~maxandersen] [~mickael_istria][~ldimaggio] [~burrsutter] [~jpallich] [~rruss] [~fbricon] > (Aside: has anyone noticed that there's an plethora of people with "M" names on this team?) > Things to consider: > a) what happens if an 8.0.0.GA user suddenly finds they've updated to an Alpha or Beta release? Can they uninstall? (Probably not, if they started with the installer; probably yes if they started from BYOE / Marketplace.) > b) how will GSS support these "I was on GA but not I'm on Beta" users? > c) What about project examples that might / might not be compatible between 8.0 and 8.x, eg., because of changes in Eclipse Luna or a new default runtime (EAP 6.3, 6.4) ? > d) what could possibly go wrong? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014