July 2014 - jbosstools-issues - Jboss List Archives

[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 reassigned JBIDE-17689: --------------------------------- Assignee: Koen Aers > 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.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.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-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 updated JBIDE-17751: ---------------------------------- Description: 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...] was: 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.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.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...] > 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-17078) JAX-RS Problems doesn't appears after the JAX-RS Support is activated

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17078?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17078: --------------------------------------- I opened JBIDE-17771 to see what can be done for 4.2.0.CR1 > JAX-RS Problems doesn't appears after the JAX-RS Support is activated > --------------------------------------------------------------------- > > Key: JBIDE-17078 > URL: https://issues.jboss.org/browse/JBIDE-17078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > > JAX-RS validation runs when there is a change in the project with JAX-RS Support. However, it doesn't run right after the JAX-RS Support is enabled. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17771) Trigger validation when JAX-RS nature is added on a project

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-17771: ------------------------------------- Summary: Trigger validation when JAX-RS nature is added on a project Key: JBIDE-17771 URL: https://issues.jboss.org/browse/JBIDE-17771 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: webservices Affects Versions: 4.2.0.Beta3 Reporter: Xavier Coulon Assignee: Xavier Coulon After [~akazakov]'s suggestion in JBIDE-17078, see how the current way to trigger a full validation on the JAX-RS metamodel can be performed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17078) JAX-RS Problems doesn't appears after the JAX-RS Support is activated

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17078?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17078: --------------------------------------- [~akazakov], Well, I got a work-around for 4.2.0.Beta3: if the only file that changed was '.project', I trigger a full validation. By chance, my JAX-RS model is already available, so I dont't need to trigger a full build. I'll see if I can improve this for 4.2.0.CR1. > JAX-RS Problems doesn't appears after the JAX-RS Support is activated > --------------------------------------------------------------------- > > Key: JBIDE-17078 > URL: https://issues.jboss.org/browse/JBIDE-17078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > > JAX-RS validation runs when there is a change in the project with JAX-RS Support. However, it doesn't run right after the JAX-RS Support is enabled. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17025) Patching EAP 6.2 breaks classpath jar files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17025?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17025: ------------------------------------ There is currently no 4.1.x stream maintenance release planned. Can you use a 4.2.x stream build instead? With Eclipse 4.4 Luna released last week, there's a brand-new Eclipse to use w/ the latest JBoss Tools 4.2.0.Beta2 or JBDS 8.0.0.Beta2. > Patching EAP 6.2 breaks classpath jar files > ------------------------------------------- > > Key: JBIDE-17025 > URL: https://issues.jboss.org/browse/JBIDE-17025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.Final > Environment: Windows 7, Kepler SR2 > Reporter: Jesper Skov > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > Using the JBoss CLI command 'patch apply .../eap-6.2.2.zip' breaks some of the module jars (the files become invalid ZIP-archives). > This is apparently done as a way to mark the modules off-limits for the container, while still allowing roll-back if necessary. > See https://access.redhat.com/site/discussions/726623 > Unfortunately, Eclipse includes these jars in the JBossTools-defined classpath. When scanned, these will be found corrupt, and the project classpath marked as broken. > On my installation, the first few files to trigger this problem are: > * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar > * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar > I guess it might be possible to adjust the server definition's Default Classpath Entries in Eclipse preferences. But I decided to just copy the original EAP 6.2 files on top of the runtime and get on with work... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17465) Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17465?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-17465 at 7/2/14 3:50 PM: ------------------------------------------------------------ Set to Beta3 target so this can be seen/triaged as important for this release. If NOT important, close and explain why so we avoid "reopen for clarification" churn. :D Perhaps old tests for old runtimes can be moved to https://github.com/jbosstools/jbosstools-integration-tests/ so they're not run as part of every Server Tools build, but downstream later on a more weekly schedule? was (Author: nickboldt): Set to Beta3 target so this can be seen/triaged as important for this release. If NOT important, close and explain why so we avoid "reopen for clarification" churn. :D > Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3? > --------------------------------------------------------- > > Key: JBIDE-17465 > URL: https://issues.jboss.org/browse/JBIDE-17465 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > Looking in org.jboss.tools.as.test.core/pom.xml I see you test for & with EAP 6.1 but not 6.2 or 6.3. > https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.... > Should that be updated to include 6.2 (now available) and 6.3 (in a month or so when it's released) ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17465) Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17465?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17465: ------------------------------- Fix Version/s: 4.2.0.Beta3 > Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3? > --------------------------------------------------------- > > Key: JBIDE-17465 > URL: https://issues.jboss.org/browse/JBIDE-17465 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > Looking in org.jboss.tools.as.test.core/pom.xml I see you test for & with EAP 6.1 but not 6.2 or 6.3. > https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.... > Should that be updated to include 6.2 (now available) and 6.3 (in a month or so when it's released) ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17465) Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17465?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17465: ------------------------------------ Set to Beta3 target so this can be seen/triaged as important for this release. If NOT important, close and explain why so we avoid "reopen for clarification" churn. :D > Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3? > --------------------------------------------------------- > > Key: JBIDE-17465 > URL: https://issues.jboss.org/browse/JBIDE-17465 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > Looking in org.jboss.tools.as.test.core/pom.xml I see you test for & with EAP 6.1 but not 6.2 or 6.3. > https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.... > Should that be updated to include 6.2 (now available) and 6.3 (in a month or so when it's released) ? -- 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