July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Rich DiCroce (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Rich DiCroce commented on JBIDE-17986: -------------------------------------- [~maxandersen] The problem occurred on all of the Maven projects I looked at, except the ones with WAR packaging because m2e-wtp has special handling for those. You should be able to reproduce the problem by setting up a stock Luna install and then installing the Abridged JBoss Tools package. The result is not a failure exactly, in that there's no error message. The pom.properties file just isn't generated. > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16597) OpenShift Server Adapter: Open launch configuration cause error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16597?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16597: ------------------------------------------ postponed to 4.3.x since went out of time for 4.2.0.CR1 > OpenShift Server Adapter: Open launch configuration cause error > --------------------------------------------------------------- > > Key: JBIDE-16597 > URL: https://issues.jboss.org/browse/JBIDE-16597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: server_adapter_editor > Fix For: 4.3.x > > Attachments: open_launch_config1.png, open_launch_config2.png, open_launch_config3.png > > Original Estimate: 1 day > Remaining Estimate: 1 day > > In OpenShift server adapter settings is Open launch configuration link. Throws error after click on it. See attached images and error log: > {code:title=.log} > !ENTRY org.eclipse.ui 4 0 2014-02-17 13:45:08.437 > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.NullPointerException > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1401) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$3.widgetSelected(LaunchConfigurationTabGroupViewer.java:308) > 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:4423) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:213) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:661) > at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:638) > at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:594) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) > at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17998?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17998: --------------------------------------------- yeah its just the descriptive name I believe. does not change the GAV parts of the identification. It will change the output in the mvn builds so the names should still be unique. > Use better <name> in pom file > ----------------------------- > > Key: JBIDE-17998 > URL: https://issues.jboss.org/browse/JBIDE-17998 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > In order to improve identification of jbosstools related reports on SonarQube, the <name> in pom files should be: > * For the root pom, same name as the GitHub repo. Eg jbosstools-webservices, jbosstools-server... > * For the children, <name-of-repo>.<name-of-artifact>. Eg jbosstools-webservices.features, jbosstools-server.jmx.plugins... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17977) Server adapter: "configure markers" missing in server adapter context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17977?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17977: ------------------------------------------ merged and pushed to upstream/master > Server adapter: "configure markers" missing in server adapter context menu > -------------------------------------------------------------------------- > > Key: JBIDE-17977 > URL: https://issues.jboss.org/browse/JBIDE-17977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Labels: server_adapter > Fix For: 4.2.0.CR1 > > Attachments: server-adapter-configure-markers.png > > > configure markers available from the project context menu should also be accessible from server context menu. > seem to have been missed when we aligned the context markers. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3086: ------------------------------------------- I'm +1 on having one updatesite url for users. Mostly interested in reviewing how they are structured and how the result will look like for users. Can we make a test of this before making it live on the live system please ? > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17986: --------------------------------------------- [~nickboldt] yes i know we got the version that is broken from Luna. Thats why I wanted to clarify it is not jbosstools that bundles it (we mirror it yes, but it comes from eclipse luna) [~rcd] can you provide example project where you are seeing the failures ? > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18003) Forge quick access menu loses focus and closes when executed in the context of a cheatsheet command/action

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18003?page=com.atlassian.jira.plugi... ] Vineet Reynolds updated JBIDE-18003: ------------------------------------ Affects Version/s: 4.2.0.Beta3 > Forge quick access menu loses focus and closes when executed in the context of a cheatsheet command/action > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18003 > URL: https://issues.jboss.org/browse/JBIDE-18003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Vineet Reynolds > Priority: Minor > > When I add the org.jboss.tools.forge.ui.command.runForgeCommand command to an Eclipse cheatsheet and execute it, the quick access menu is launched, but immediately closes when the cheatsheet regain focus. We should find a way to retain focus in the quick access menu so that it wont be closed and will continue to receive user input. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17825) Cannot initialize JBoss DND

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17825?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17825: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Cannot initialize JBoss DND > --------------------------- > > Key: JBIDE-17825 > URL: https://issues.jboss.org/browse/JBIDE-17825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta3 > Environment: Fedora 20, > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > Almost allways (if not allways), when Central is started on fresh forkspace, "Cannot initialize JBoss DND" error appears in error log. > I don't know what's causing this message, but Drag'n'Drop installation from Central works. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18004) Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-18004: --------------------------------------- Summary: Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets Key: JBIDE-18004 URL: https://issues.jboss.org/browse/JBIDE-18004 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 4.2.0.Beta3 Reporter: Vineet Reynolds Priority: Minor The name of the command to be executed should be accepted as a parameter so that it can be directly launched from an Eclipse cheatsheet, instead of merely guiding the user to the quick access menu. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17956) Add progress bar to Add Arquillian profiles dialog

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17956?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17956: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Add progress bar to Add Arquillian profiles dialog > -------------------------------------------------- > > Key: JBIDE-17956 > URL: https://issues.jboss.org/browse/JBIDE-17956 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.2.0.Beta3 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.2.0.CR1 > > > In Add Arquillian profiles dialog, when I select all profiles and press OK, it takes quite a long time to finish the task. There should be a progress bar in this case. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014