July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20369) "Early Access enabled/installed" sign is not visible after restart

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20369?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20369: -------------------------------- Steps to Reproduce: 1. Install JBossTools Central and restart eclipse 2. Enable EA 3. ASSERT: Yellow sign is visible on first tab 4. Restart Eclipse 5. ASSERT: Yellow sign is visible on first tab Now at step #5 there is no sign about EA being enabled after restart. was: 1. Install JBossTools Central and restart eclipse 2. Enable EA 3. ASSERT: Yellow sine is visible on first tab 4. Restart Eclipse 5. ASSERT: Yellow sine is visible on first tab Now at step #5 there is no sign about EA being enabled after restart. > "Early Access enabled/installed" sign is not visible after restart > ------------------------------------------------------------------ > > Key: JBIDE-20369 > URL: https://issues.jboss.org/browse/JBIDE-20369 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > Yellow sign "Early Access enabled/installed" is not visible after restart with "Enable Early Access" check box selected. It appears after disable/enable early access again. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20369) "Early Access enabled/installed" sign is not visible after restart

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20369?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20369: ----------------------------------- Assignee: Fred Bricon > "Early Access enabled/installed" sign is not visible after restart > ------------------------------------------------------------------ > > Key: JBIDE-20369 > URL: https://issues.jboss.org/browse/JBIDE-20369 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > Yellow sign "Early Access enabled/installed" is not visible after restart with "Enable Early Access" check box selected. It appears after disable/enable early access again. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20369) "Early Access enabled/installed" sign is not visible after restart

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20369?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20369: -------------------------------- Fix Version/s: 4.3.0.CR1 > "Early Access enabled/installed" sign is not visible after restart > ------------------------------------------------------------------ > > Key: JBIDE-20369 > URL: https://issues.jboss.org/browse/JBIDE-20369 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > Yellow sign "Early Access enabled/installed" is not visible after restart with "Enable Early Access" check box selected. It appears after disable/enable early access again. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18709) EAP alpha releases not require credentials; verify downloadRuntimes works

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18709?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-18709: ----------------------------------- Assignee: Rob Stryker Resolution: Done Closing as resolved... our existing tools *can* handle urls as above so long as they have the ?workflow=direct. > EAP alpha releases not require credentials; verify downloadRuntimes works > ------------------------------------------------------------------------- > > Key: JBIDE-18709 > URL: https://issues.jboss.org/browse/JBIDE-18709 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > A new requirement by the EAP team is asking for anonymous downloads of alpha releases. If such url's made it into stacks.yaml it *could* break our recent release. > We'll need to verify that if such a new url made it into stacks, it wouldn't break our download runtimes at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18709) EAP alpha releases not require credentials; verify downloadRuntimes works

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18709?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18709: ------------------------------------- I've just verified that if a URL like http://www.jboss.org/download-manager/jdf/file/jboss-eap-6.4.0.Alpha.zip?... makes it into stacks.yaml, there is no issue with downloading it. A wget works fine, and it also works fine from tools. I'm closing this issue. More information / future changes can be discussed at JBIDE-19948 about what download-manager and dlruntimes should look like in the future. ORG-2414 is also relevant for those doing a deep-dive of history. > EAP alpha releases not require credentials; verify downloadRuntimes works > ------------------------------------------------------------------------- > > Key: JBIDE-18709 > URL: https://issues.jboss.org/browse/JBIDE-18709 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Affects Versions: 4.2.0.Final, 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Rob Stryker > Fix For: 4.3.0.Beta2 > > > A new requirement by the EAP team is asking for anonymous downloads of alpha releases. If such url's made it into stacks.yaml it *could* break our recent release. > We'll need to verify that if such a new url made it into stacks, it wouldn't break our download runtimes at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-3384. ------------------------------- Resolution: Done Everything looks fine for b2 as far as I can see. > Investigate how the terminal changes in Mars will/should affect us > ------------------------------------------------------------------- > > Key: JBDS-3384 > URL: https://issues.jboss.org/browse/JBDS-3384 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, forge, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Terminal (console) support in eclipse mars is changing and we should > make sure we adjust for it. > Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html > Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now. > This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new. > As we find what it entails we should link those issues to this jira. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20324) Unhandled event loop exception when trying to delete a deployment on a server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20324?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20324: ------------------------------------- [~mmalina] is the action visible on jiri's machine, but just doesn't NPE? Or does it not show up at all? > Unhandled event loop exception when trying to delete a deployment on a server > ----------------------------------------------------------------------------- > > Key: JBIDE-20324 > URL: https://issues.jboss.org/browse/JBIDE-20324 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Andre Dietisheim > Attachments: remove-deployment.png > > > When I click a module (e.g. dynamic web project) deployed to a running server and then hit the Del key on my keyboard, I will always get an exception in the Error Log: > {code} > Unhandled event loop exception > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558) > at org.eclipse.e4.ui.bindings.keys.OutOfOrderListener.handleEvent(OutOfOrderListener.java:72) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1528) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Tree.sendKeyEvent(Tree.java:2592) > at org.eclipse.swt.widgets.Control.keyDown(Control.java:2402) > at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:607) > at org.eclipse.swt.widgets.Tree.keyDown(Tree.java:1991) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5694) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2130) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5756) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5193) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5342) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > Caused by: java.lang.NullPointerException > at org.jboss.tools.openshift.internal.common.ui.command.RemoveConnectionHandler$1.toString(RemoveConnectionHandler.java:44) > at org.jboss.tools.openshift.internal.common.ui.command.RemoveConnectionHandler$1.toString(RemoveConnectionHandler.java:1) > at org.jboss.tools.openshift.common.core.utils.StringUtils.toString(StringUtils.java:69) > at org.jboss.tools.openshift.internal.common.ui.command.RemoveConnectionHandler.execute(RemoveConnectionHandler.java:38) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > ... 55 more > {code} > This looks like an upstream bug :-\ Let me know if I should report this. > Note that this probably only happens on Mac - Jirka Peterka tried this for me on Linux and it worked fine. > Also, one indicator of the problem is that when you right-click a deployed module in the Servers view, you can't see the shortcut there next to Remove. > !remove-deployment.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-643) Document Maven Tools functionality in User Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-643?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-643: ------------------------------- Sprint: 2015/S6 (16-Mar > 29-Mar), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 2015/S6 (16-Mar > 29-Mar), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT) > Document Maven Tools functionality in User Guide > ------------------------------------------------ > > Key: TOOLSDOC-643 > URL: https://issues.jboss.org/browse/TOOLSDOC-643 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Michelle Murray > Assignee: Misha Ali > Labels: JBDS80_Approved_Scope > Fix For: 4.3.0.Final > > > Add a chapter to the JBDS User Guide on Maven Tools. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-669) Document the consequences of creating a remote server without a runtime

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-669?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-669: ------------------------------- Sprint: 20-Jul >> 02-Aug 2015-JBDS/JBT Component/s: General documentation issues > Document the consequences of creating a remote server without a runtime > ----------------------------------------------------------------------- > > Key: TOOLSDOC-669 > URL: https://issues.jboss.org/browse/TOOLSDOC-669 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Misha Ali > > In a recent discussion in JBIDE-19463, we talked about some limitations that result from creating of a remote server without a runtime. > For example, the jmx connection does not work because we use libs from the runtime to connect via jmx. > We have this document about setting up a remote server: > https://access.redhat.com/articles/1515503 > There is this: > {quote} > d. A remote server can now be created without assigning a runtime to it. Depending on the requirements, select the Assign a runtime to this server check box (and select an existing runtime or create a new one) or leave the box unselected and then click Next. > {quote} > So I think it would make sense to add these details somewhere in there. > From JBIDE-19463: > {quote} > Autodetection of ports by scanning your standalone.xml (or your selected configuration file). Since there's no local runtime, and no local standalone.xml, we can't notice that you've modified your ports to be non-standard. > Also, without a local runtime, some small behavior changes might be default values. For example, sometimes we hard-code different behavior between minor or micro versions if we notice there's a bug in some previous release. For example, some of the early jboss-7 releases didn't support the -b flag. > Without a local runtime to scan, we can't know the exact version you're running against, and can't customize args (or other things) to work around bugs in those specific runtime versions. > {quote} > On top of that, you won't be able to create a JMX connection to the server. > I'll leave it to you to decide how much details we need in the article. Maybe it's not necessary to talk about early versions of jboss-7 and that part. But it makes sense to at least mention that some things may be missing, mainly JMX connection, detection of ports from standalone.xml and perhaps several more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3490) Include capabilities preference page into target-platform

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3490: -------------------------------- Story Points: 3 Sprint: Sprint #7 July 2015 > Include capabilities preference page into target-platform > --------------------------------------------------------- > > Key: JBDS-3490 > URL: https://issues.jboss.org/browse/JBDS-3490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: javascript, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.CR1 > > > Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug tern related issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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