July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16407) Decouple openshift from legacy astools code

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16407?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16407. --------------------------------- Start/stop/restart disable in (verified in JBDS 8.0.0.Beta3c). > Decouple openshift from legacy astools code > ------------------------------------------- > > Key: JBIDE-16407 > URL: https://issues.jboss.org/browse/JBIDE-16407 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha2 > > > With coming changes to astools, openshift depends on classes that will most likely be deprecated and removed. > Even if its not, openshift is currently using an astools framework that is really geared for servers that can change behavior heavily based on various settings. It's not quite appropriate for openshift which has only one core behavior in terms of publishing etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16683) For JBIDE 4.1.2.CR1: Prepare for CR1 release [OpenShift]

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16683?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16683. --------------------------------- > For JBIDE 4.1.2.CR1: Prepare for CR1 release [OpenShift] > -------------------------------------------------------- > > Key: JBIDE-16683 > URL: https://issues.jboss.org/browse/JBIDE-16683 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: task > Fix For: 4.1.2.CR1 > > > For JBIDE 4.1.2.CR1 [OpenShift]: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.1.1.Final or JBDS 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.2.CR1 or 7.1.1.CR1 > [Unresolved JIRAs with fixVersion = 4.1.2.CR1, 4.1.2.Final, 7.1.1.CR1, 7.1.1.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.2.Final-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.30.6.Final > mvn clean verify -Dtpc.version=4.32.0.Final > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17623) Remove "Experimental" label from Openshift features when no longer incubating

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17623?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17623. --------------------------------- Verified. > Remove "Experimental" label from Openshift features when no longer incubating > ----------------------------------------------------------------------------- > > Key: JBIDE-17623 > URL: https://issues.jboss.org/browse/JBIDE-17623 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Fix For: 4.2.0.Beta3 > > > OpenShift has 1 feature which append " (Experimental)" onto its description. > If these features are ready for prime-time, this qualifier should be removed. > Affected file: > https://github.com/jbosstools/jbosstools-openshift/blob/master/features/o... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2499) Not able to resize the preferences window in JDBS 6

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2499?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-2499: -------------------------------- Affects Version/s: 8.0.0.Beta3 > Not able to resize the preferences window in JDBS 6 > --------------------------------------------------- > > Key: JBDS-2499 > URL: https://issues.jboss.org/browse/JBDS-2499 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 6.0.0.GA, 8.0.0.Beta3 > Environment: Fedora 17 > jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855 > Reporter: Sande Gilda > Assignee: Denis Golovin > Attachments: JDBS6-01.png, JDBS6-02.png, JDBS6-03.png, JDBS6-04.png > > > To recreate: > Start JDBS. > Choose menu: Window --> Preferences > Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar. > When I hover over the edges, I get the arrow resize icon, but I can't resize it. > At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17892) NPE during verify connection when password left empty

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17892?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-17892. ------------------------------------- Resolution: Done > NPE during verify connection when password left empty > ----------------------------------------------------- > > Key: JBIDE-17892 > URL: https://issues.jboss.org/browse/JBIDE-17892 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Pavol Srna > Assignee: Lincoln Baxter III > Fix For: 4.2.0.CR1 > > > {code} > java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:459) > at java.util.Properties.setProperty(Properties.java:166) > at org.jboss.forge.addon.database.tools.connections.AbstractConnectionProfileDetailsPage$5.validate(AbstractConnectionProfileDetailsPage.java:142) > at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.validate(AbstractInputComponent.java:203) > at sun.reflect.GeneratedMethodAccessor155.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81) > at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_b39bae21-43b3-449c-852c-58ed002be5ee.validate(AbstractFaceted_$$_javassist_b39bae21-43b3-449c-852c-58ed002be5ee.java) > at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.validate(SingleCommandControllerImpl.java:152) > at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.isValid(SingleCommandControllerImpl.java:162) > at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.isValid(WizardCommandControllerImpl.java:220) > at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.canMoveToNextStep(WizardCommandControllerImpl.java:279) > at org.jboss.forge.addon.ui.impl.controller.NoUIWizardControllerDecorator.next(NoUIWizardControllerDecorator.java:113) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_2b11ffb0-58fe-4ba7-9de6-ff12e26edcd5.next(CommandController_$$_javassist_2b11ffb0-58fe-4ba7-9de6-ff12e26edcd5.java) > at org.jboss.tools.forge.ui.internal.ext.dialog.ForgeWizardDialog.nextPressed(ForgeWizardDialog.java:49) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:434) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:158) > at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:187) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:326) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:316) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$6.mouseUp(QuickAccessContents.java:465) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-17989 at 7/29/14 9:43 PM: ---------------------------------------------------------------- Just tested locally and it is true. After creating branding plugin for CDI, usage in preferences says: "Version: 2.0.0.Beta3-v20140718-0436-B48 Components: CDI-" was (Author: dgolovin): Just tested locally and it is true. > keyword used for plugin tracking is missing majority of times on GA > ------------------------------------------------------------------- > > Key: JBIDE-17989 > URL: https://issues.jboss.org/browse/JBIDE-17989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.2.0.CR1 > > > looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result. > Meaning we can't see how many have installed the various plugins. > What is weird *some* do and others do not have it. > Need to track down the reason for that being missed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17989) keyword used for plugin tracking is missing majority of times on GA

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17989: --------------------------------------- Just tested locally and it is true. > keyword used for plugin tracking is missing majority of times on GA > ------------------------------------------------------------------- > > Key: JBIDE-17989 > URL: https://issues.jboss.org/browse/JBIDE-17989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.2.0.CR1 > > > looking at tracking numbers i'm seeing more and more requests where the keywords are not making it into the result. > Meaning we can't see how many have installed the various plugins. > What is weird *some* do and others do not have it. > Need to track down the reason for that being missed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Karl Pietrzak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Karl Pietrzak commented on JBIDE-17960: --------------------------------------- Seems to be OK on Windows, but I originally came across this on Mac OS X. I imagine it'll be the same, but I'll confirm on Mac OS X tomorrow. > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17996) Server Runtime Environment wizard says "C:standalone" even if corrected

by Karl Pietrzak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17996?page=com.atlassian.jira.plugi... ] Karl Pietrzak updated JBIDE-17996: ---------------------------------- Environment: Eclipse Luna JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70 Windows 7 x64 Java 8u11 was: Eclipse Luna JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70 > Server Runtime Environment wizard says "C:standalone" even if corrected > ----------------------------------------------------------------------- > > Key: JBIDE-17996 > URL: https://issues.jboss.org/browse/JBIDE-17996 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: Eclipse Luna > JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70 > Windows 7 x64 > Java 8u11 > Reporter: Karl Pietrzak > > h3. What > For some reason, the Server Environment Runtime wizard for Wildfly (probably JBoss too) auto-detects the "Configuration Base Directory" as "C:standalone". > Even if I try to overwrite it to just "standalone", it overwrites it to "C:standalone". > h3. Screencast > http://screencast.com/t/1wC8B2loj4H > h3. Found Bug location? > My guess is {{org.jboss.ide.eclipse.as.core.util.ServerUtil::makeRelative}}, but I'm not sure why. > At first I thought it had something to do with the fact that I originally put my Wildfly install into {{c:\program files}} (note the space), but then I moved it to a location that does not have spaces and the same thing occurred. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17996) Server Runtime Environment wizard says "C:standalone" even if corrected

by Karl Pietrzak (JIRA)

Karl Pietrzak created JBIDE-17996: ------------------------------------- Summary: Server Runtime Environment wizard says "C:standalone" even if corrected Key: JBIDE-17996 URL: https://issues.jboss.org/browse/JBIDE-17996 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Beta3 Environment: Eclipse Luna JBossAS Tools 3.0.0.Beta3-v20140718-1832-B70 Reporter: Karl Pietrzak h3. What For some reason, the Server Environment Runtime wizard for Wildfly (probably JBoss too) auto-detects the "Configuration Base Directory" as "C:standalone". Even if I try to overwrite it to just "standalone", it overwrites it to "C:standalone". h3. Screencast http://screencast.com/t/1wC8B2loj4H h3. Found Bug location? My guess is {{org.jboss.ide.eclipse.as.core.util.ServerUtil::makeRelative}}, but I'm not sure why. At first I thought it had something to do with the fact that I originally put my Wildfly install into {{c:\program files}} (note the space), but then I moved it to a location that does not have spaces and the same thing occurred. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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