July 2014 - jbosstools-issues - Jboss List Archives

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

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17752?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-17752. --------------------------------- Resolution: Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Webservices] > --------------------------------------------------------- > > Key: JBIDE-17752 > URL: https://issues.jboss.org/browse/JBIDE-17752 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta2 > > > For JBIDE 4.2.0.Beta3 [Webservices]: 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.Beta2 > [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.Beta4 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta4-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.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-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.CR1-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 Webservices 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] (JBIDE-17751) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17751?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-17751. --------------------------------- Resolution: Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [LiveReload] > -------------------------------------------------------- > > Key: JBIDE-17751 > URL: https://issues.jboss.org/browse/JBIDE-17751 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta2 > > > For JBIDE 4.2.0.Beta2 [LiveReload]: 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.Beta2 > [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.Beta4-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta4 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta4-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.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-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.CR1-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 LiveReload 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] (JBIDE-17296) Missing warning decorator on the "JAX-RS Web Services" node when no application is defined

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17296?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17296: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) Description: Moving to 4.2.0.CR1. The problem decorator on the "JAX-RS Web Services" node is not refresh as it should, but a call to the "refresh" action on that node fixes the problem. > Missing warning decorator on the "JAX-RS Web Services" node when no application is defined > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17296 > URL: https://issues.jboss.org/browse/JBIDE-17296 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > Moving to 4.2.0.CR1. The problem decorator on the "JAX-RS Web Services" node is not refresh as it should, but a call to the "refresh" action on that node fixes the problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17650) Find better way to enable Tern cordova module for cordova projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17650?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17650: ------------------------------------ All 0.4.0 builds are missing the linux gtk x86 plugin (and your requested earlier version has the same bug in its update site / feature.xml). See https://github.com/angelozerr/tern.java/pull/96 and https://github.com/angelozerr/tern.java/pull/95 for two options to fix that. So... we need a newer 0.4.0 from [~azerr] before we can proceed here. > Find better way to enable Tern cordova module for cordova projects > ------------------------------------------------------------------ > > Key: JBIDE-17650 > URL: https://issues.jboss.org/browse/JBIDE-17650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17748) Update TP with Tern.java v.0.4.0.201407021311

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17748?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17748: ------------------------------------ Yeah, just figured that out here too. :) https://github.com/angelozerr/tern.java/pull/96 > Update TP with Tern.java v.0.4.0.201407021311 > --------------------------------------------- > > Key: JBIDE-17748 > URL: https://issues.jboss.org/browse/JBIDE-17748 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Fix For: 4.2.0.Beta3 > > > *Need to switch jst.jsdt to the latest tested Tern v.0.3.0. It contains few important fixes regarding cintent assist initialization and Node.js preferences like:* > - https://github.com/angelozerr/tern.java/pull/72 -NPE in ImageResource.registerImageDescriptor() > - https://github.com/angelozerr/tern.java/pull/80 - An embedded install of Node.js should be used by default > - https://github.com/angelozerr/tern.java/pull/87 - Find a way to configure Tern Modules that are default for Nature Adapters defined on a project > *Reason:* > jbosstools-jst is going to provide integration between torn.java and jsdt. torn.java is going to be used to improve JavaScript support > *License and owner:* > - Root License is EPL. Owner is Angelo ZERR. > -- core > --- org.json.simple - EPL (included into torn-feature below) > ---- lib/json-simple-1.1.1.jar - Apache License 2.0 (see http://www.apache.org/licenses/LICENSE-2.0.txt) > --- org.mozilla.javascript > ---- lib/js.jar - Mozilla Public License Version 2.0 (see http://mozilla.org/MPL/2.0/) > --- tern.core - EPL (included into tern-feature below) > --- tern.server.nodejs - EPL (included into tern-server-nodejs-feature below) > ---- tern.server.nodejs/node_modules/tern/LICENSE > ----- node_modules/acorn/LICENSE > ------ node_modules/codemirror/LICENSE > ------ node_modules/glob/LICENSE > ------- node_modules/inherits/LICENSE > ------ node_modules/minimatch/LICENSE > ------- node_modules/lru-cache/LICENSE > ------- node_modules/sigmund/LICENSE > ----- node_modules/typescript/LICENSE - Apache License v. 2.0 > --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below) > -- eclipse > --- tern.eclipse.ide.core - EPL (included into tern-feature below) > --- tern.eclipse.ide.jsdt - EPL (included into tern-jsdt-feature below) > --- tern.eclipse.ide.server.nodejs.core - EPL (included into tern-server-nodejs-feature below) > --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below) > --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 - Supposed to be EPL but it is not included anywhere yet > ---- node-v0.10.22-linux-x86.zip has several LICENSE files inside (download) > ----- LICENSE > ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0 > ----- lib/node_modules/npm/node_modules/*/LICENSE > --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 - EPL (included into tern.eclipse.linux.gtk.x86.feature below) > ---- node-v0.10.22-linux-x86_64.zip has several LICENSE files inside (download) > ----- LICENSE > ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0 > ----- lib/node_modules/npm/node_modules/*/LICENSE > --- tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 - EPL (included into tern.eclipse.macosx.cocoa.x86_64.feature below) > ---- node-v0.10.22-macosx-x86_64.zip has several LICENSE files inside (download) > ----- LICENSE > ----- lib/node_modules/npm - The Artistic License 2.0 > ----- lib/node_modules/npm/node_modules/*/LICENSE > --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 - EPL (include into tern.eclipse.win32.win32.x86.feature below) > ---- node-v0.10.22-win32-x86.zip has no LICENSE files inside (download) > ----- node-v0.10.22-win32-x86/node.exe - see http://nodejs.org/download/ for licensing information for node.exe. > --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 - EPL (include into tern.eclipse.win32.win32.x86.feature below) > ---- node-v0.10.22-win32-x86_64.zip has no LICENSE files inside (download) > ----- node-v0.10.22-win32-x86_64/node.exe - see http://nodejs.org/download/ for licensing information for node.exe. > --- tern.eclipse.ide.tools.core - EPL (included into tern.eclipse.ide.tools.feature below) > --- tern.eclipse.ide.tools.ui - EPL (included into tern.eclipse.ide.tools.feature below) > --- tern.eclipse.ide.ui - EPL (included into tern-feature below) > --- tern.eclipse - EPL (included into tern-feature below) > -- update-site > --- tern-feature - EPL (see licens.httml) > --- tern-jsdt-feature - EPL (see licens.httml) > --- tern-server-nodejs-feature - EPL (see licens.httml) > --- tern.eclipse.ide.tools.feature - EPL (see plicense.html) > --- tern.eclipse.linux.gtk.x86_64.feature - EPL (see license.html) > --- tern.eclipse.macosx.cocoa.x86_64.feature - EPL (see license.html) > --- tern.eclipse.win32.win32.x86.feature - EPL (see license.html) > *Original repo:* > http://oss.opensagres.fr/tern.repository/0.4.0-SNAPSHOT/ > *JBoss mirror:* > http://downloads.jboss.org/jbosstools/updates/requirements/tern.java-0.4.... > *Sources:* > https://github.com/angelozerr/tern.java > *Affected projects:* > jbosstools-jst > jbosstools-aerogear > > *Include in JBDS:* > No > *Type of dependency:* > distribution > *List of bundles added/removed:* > TBD: need to update PR to use features -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17688) show context for cmd+4 in the menu

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17688?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-17688. ------------------------------- Resolution: Duplicate Issue This issue is included in the work for JBIDE-17702 > show context for cmd+4 in the menu > ----------------------------------- > > Key: JBIDE-17688 > URL: https://issues.jboss.org/browse/JBIDE-17688 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.2.0.Beta3 > > > to let the user know what context is active cmd+4 should show it in its UI -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17688) show context for cmd+4 in the menu

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17688?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-17688: --------------------------------- Assignee: Koen Aers > show context for cmd+4 in the menu > ----------------------------------- > > Key: JBIDE-17688 > URL: https://issues.jboss.org/browse/JBIDE-17688 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.2.0.Beta3 > > > to let the user know what context is active cmd+4 should show it in its UI -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17688) show context for cmd+4 in the menu

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17688?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17688: ------------------------------ Fix Version/s: 4.2.0.Beta3 > show context for cmd+4 in the menu > ----------------------------------- > > Key: JBIDE-17688 > URL: https://issues.jboss.org/browse/JBIDE-17688 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.2.0.Beta3 > > > to let the user know what context is active cmd+4 should show it in its UI -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17689) forge wizards should show what context they are running in

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17689?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-17689. ------------------------------- Resolution: Duplicate Issue This issue is included in the work for JBIDE-17702 > forge wizards should show what context they are running in > ---------------------------------------------------------- > > Key: JBIDE-17689 > URL: https://issues.jboss.org/browse/JBIDE-17689 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.2.0.Beta2 > > > wizards should show what context they are running in ("current selected project/resource") > *must* be using workspace names, not full resource paths :) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17689) forge wizards should show what context they are running in

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17689?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17689: ------------------------------ Fix Version/s: 4.2.0.Beta3 (was: 4.2.0.Beta2) > forge wizards should show what context they are running in > ---------------------------------------------------------- > > Key: JBIDE-17689 > URL: https://issues.jboss.org/browse/JBIDE-17689 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.2.0.Beta3 > > > wizards should show what context they are running in ("current selected project/resource") > *must* be using workspace names, not full resource paths :) -- 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