July 2014 - jbosstools-issues - Jboss List Archives

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17769?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-17769. --------------------------------- Resolution: Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Freemarker] > -------------------------------------------------------- > > Key: JBIDE-17769 > URL: https://issues.jboss.org/browse/JBIDE-17769 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [Freemarker]: 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 Freemarker 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-3086) Change Central Discovery URLs?

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3086: -------------------------------- Summary: 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] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-3085: -------------------------------------- We can't support Alpha/Beta users it's simple as that. And customers probably wouldn't appreciate being shunted to an unsupported version without prior knowledge. So they should not upgrade unless they know specifically they are going to be moving to an unsupported version of the product. So in summary, if we can't bring up a pop up that give users this option and a warning then no, users should not be able to upgrade to Alpha releases.... however, they should be able to go from 8.0.0.GA to 8.1.0.GA as normal. > 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] (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 reassigned JBIDE-17809: ---------------------------------- Assignee: Nick Boldt > 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 > > 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] (JBIDE-17809) update site index.html lists duplicate entries when both jar and pack.gz artifacts are found

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-17809: ---------------------------------- Summary: 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 Reporter: Nick Boldt 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] (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: ------------------------------- Component/s: build updatesite > 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 > Reporter: Nick Boldt > > 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] (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: ------------------------------- Affects Version/s: 4.2.0.Beta3 > 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 > > 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] (JBIDE-17787) GWT New and Noteworthy for 4.2.0.Beta3

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17787?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-17787. --------------------------------- Resolution: Rejected > GWT New and Noteworthy for 4.2.0.Beta3 > -------------------------------------- > > Key: JBIDE-17787 > URL: https://issues.jboss.org/browse/JBIDE-17787 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: gwt > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.0.Beta3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If GWT is not listed here check if there are issues that should be added and add them. > Document the ones relevant for GWT by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17807) index.html of HTML5 kitchensink example is not displayed in VPE visual part

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17807?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-17807: ---------------------------------------------- Assignee: Konstantin Marmalyukov > index.html of HTML5 kitchensink example is not displayed in VPE visual part > --------------------------------------------------------------------------- > > Key: JBIDE-17807 > URL: https://issues.jboss.org/browse/JBIDE-17807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3-v20140706-0939-B172 > Linux > SWT_GTK3=0 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.CR1 > > > 1. Import HTML5 kitchensink project from JBoss Central > 2. Open index.html in VPE > ERROR: Visual part of VPE is blank > HTML Preview is showing page properly. > 3. Run JBT with arguments -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false > ASSERT: Page is displayed correctly in Visual part of VPE -- 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 Nick Boldt (JIRA)

Nick Boldt created JBDS-3085: -------------------------------- Summary: 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