March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19464) m2e-apt doesnt delete old build path

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19464?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19464: -------------------------------- Component/s: upstream > m2e-apt doesnt delete old build path > ------------------------------------ > > Key: JBIDE-19464 > URL: https://issues.jboss.org/browse/JBIDE-19464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Attachments: apt.png > > > m2e-apt sometimes doesnt delete old build path resulting in having two (or more) same classes in build path. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19464) m2e-apt doesnt delete old build path

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19464?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19464: ----------------------------------- Assignee: Fred Bricon > m2e-apt doesnt delete old build path > ------------------------------------ > > Key: JBIDE-19464 > URL: https://issues.jboss.org/browse/JBIDE-19464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Attachments: apt.png > > > m2e-apt sometimes doesnt delete old build path resulting in having two (or more) same classes in build path. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18901) git clone + cordova import

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18901?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-18901. ------------------------------ It was rejected. Closing. > git clone + cordova import > -------------------------- > > Key: JBIDE-18901 > URL: https://issues.jboss.org/browse/JBIDE-18901 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 4.2.3.Final, 4.3.0.Beta1 > > > Currently, the git clone wizard does not work with the Cordova project import. The end-user must run the git clone wizard to a point, then cancel out, then start the cordova project import wizard. > In addition, the git clone wizard is fairly "hard to use". > Feature proposal: add git clone support to the Cordova project import - so it can import from file system AND import from a git URL. > Current UI: http://www.screencast.com/t/2bjzPI6EuEgl -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19194. ------------------------------ Verified in JBT 4.2.3.CR1. > FeedHenry requires minimal-json, but it was removed from TP > ----------------------------------------------------------- > > Key: JBIDE-19194 > URL: https://issues.jboss.org/browse/JBIDE-19194 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, target-platform > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it. > But turns out that Feedhenry (Aerogear) also needs minimal-json. > So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3). > [~maxandersen] [~gercan] [~dgolovin] [~akazakov] > In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1. > In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1. > In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2. > Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19275) Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19275?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19275. ------------------------------------ > Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19275 > URL: https://issues.jboss.org/browse/JBIDE-19275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The tooling currently causes the following CoreException at startup: > {code} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19275) Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19275?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19275. -------------------------------------- Resolution: Rejected > Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19275 > URL: https://issues.jboss.org/browse/JBIDE-19275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The tooling currently causes the following CoreException at startup: > {code} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19113) wf mgmt jars not working for ipv6: Update wf jars to 8.2 jars

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19113?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19113. --------------------------------- Everything seems to work fine with this. Closing. > wf mgmt jars not working for ipv6: Update wf jars to 8.2 jars > -------------------------------------------------------------- > > Key: JBIDE-19113 > URL: https://issues.jboss.org/browse/JBIDE-19113 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > The current jars for wf do not work for ip6 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19275) Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19275?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19275 at 3/17/15 9:26 AM: ------------------------------------------------------------------- The bogus startup is contributed by "org.eclipse.jst.ws.jaxws.utils" https://bugs.eclipse.org/bugs/show_bug.cgi?id=459620 It's not an OpenShift issue. was (Author: adietish): The bogus startup is contributed by "org.eclipse.jst.ws.jaxws.utils" https://bugs.eclipse.org/bugs/show_bug.cgi?id=459620 > Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19275 > URL: https://issues.jboss.org/browse/JBIDE-19275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The tooling currently causes the following CoreException at startup: > {code} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19275) Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19275?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19275: ---------------------------------------- Assignee: Andre Dietisheim Component/s: upstream > Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19275 > URL: https://issues.jboss.org/browse/JBIDE-19275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The tooling currently causes the following CoreException at startup: > {code} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19275) Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19275?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19275: ------------------------------------- Forum Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=459620 > Fix CoreException "CoreException: Executable extension definition for "class" not found." at startup > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19275 > URL: https://issues.jboss.org/browse/JBIDE-19275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The tooling currently causes the following CoreException at startup: > {code} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015