August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-12532: ------------------------------------ Description: As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. To reproduce, type the following in the Forge console: {code} open http://forge.jboss.org {code} was: As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. To reproduce, type the following in the Forge console: {code} open http://www.google.com {code} > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.1.Final, 4.3.x > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > To reproduce, type the following in the Forge console: > {code} > open http://forge.jboss.org > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18066) JAX-RS is not enabled by default on javaee7-samples

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18066?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18066: ---------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 (was: 4.2.0.CR1) Postponing since it does not happen on 'standard' maven projects (ie, without Groovy compiler required) > JAX-RS is not enabled by default on javaee7-samples > --------------------------------------------------- > > Key: JBIDE-18066 > URL: https://issues.jboss.org/browse/JBIDE-18066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, webservices > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > When importing the JAX-RS examples of javaee7-samples (https://github.com/javaee-samples/javaee7-samples/), the JAX-RS support is not automatically enabled, whereas it should be. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18171) Remove F1 related wizards

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18171?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18171: ------------------------------ Assignee: Koen Aers > Remove F1 related wizards > ------------------------- > > Key: JBIDE-18171 > URL: https://issues.jboss.org/browse/JBIDE-18171 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > > These are now replaced by F2 functionality -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17822) Launch shortcut enablement expression caused exception

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17822?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17822: ---------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 (was: 4.2.0.CR1) > Launch shortcut enablement expression caused exception > ------------------------------------------------------ > > Key: JBIDE-17822 > URL: https://issues.jboss.org/browse/JBIDE-17822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: error1, error2, error3, error4, error5 > > > Sometimes when expanding JAX-RS Explorer, a bunch of errors appears in Error Log. > There are 5 similar errors: > {code} > Launch shortcut 'org.testng.eclipse.shortcut' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.testng.eclipse.shortcut.testngSuite' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.jboss.tools.maven.actions.LifeCycleCleanVerify' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.jboss.tools.maven.ui.isCleanVerifyMenuEnabled to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.eclipse.ant.ui.antShortcutWithDialog' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.eclipse.ant.ui.antShortcut' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12532: --------------------------------------------- forge2 shuold be configured to use the default browser eclipse has > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.1.Final, 4.3.x > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > To reproduce, type the following in the Forge console: > {code} > open http://www.google.com > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12532: ---------------------------------------- Fix Version/s: 4.2.1.Final 4.3.x (was: 4.2.x) > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.1.Final, 4.3.x > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-12532: ------------------------------------ Description: As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. To reproduce, type the following in the Forge console: {code} open http://www.google.com {code} was: As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.1.Final, 4.3.x > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > To reproduce, type the following in the Forge console: > {code} > open http://www.google.com > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-12532: ------------------------------------ Summary: Open command doesn't open URLs in JBoss Tools (was: OpenPlugin doesn't open URLs in JBoss Tools) > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.x > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-12532: ------------------------------------ Description: As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. was:As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.x > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18155) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18155?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-18155. ------------------------------- Assignee: Rob Stryker Resolution: Done Branched > For JBIDE 4.2.0.CR1: Code Freeze + Branch [Server] > -------------------------------------------------- > > Key: JBIDE-18155 > URL: https://issues.jboss.org/browse/JBIDE-18155 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Mickael Istria > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Server]: 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.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 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.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {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.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-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 Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 August 2014