[JBoss JIRA] (JBIDE-12913) Startup/Shutdown Pollers fails with EAP511
by Jesper Skov (JIRA)
Jesper Skov created JBIDE-12913:
-----------------------------------
Summary: Startup/Shutdown Pollers fails with EAP511
Key: JBIDE-12913
URL: https://issues.jboss.org/browse/JBIDE-12913
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Alpha2
Environment: Windows XP
Reporter: Jesper Skov
Assignee: Rob Stryker
When we use Web Port Startup Poller with EAP511, the server is not started.
We get an error about the port (8080) already being in use. Which it is not (confirmed with netstat).
When changing Startup Poller to JMX, the server starts as expected.
When using the JMX Shutdown Poller, it also fails. This time with failed attempts to access the JMX server after the server has shut down:
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.jboss.Shutdown.main(Shutdown.java:219)
Caused by: javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
... 5 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
... 5 more
Using Process Terminated Poller works as expected though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12924) Seam 2.3 is no longer technical preview
by Martin Malina (JIRA)
Martin Malina created JBIDE-12924:
-------------------------------------
Summary: Seam 2.3 is no longer technical preview
Key: JBIDE-12924
URL: https://issues.jboss.org/browse/JBIDE-12924
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam 2
Affects Versions: 4.0.0.Beta1
Reporter: Martin Malina
Assignee: Alexey Kazakov
Fix For: 4.0.0.CR1
With Seam 2.3.0.Final having been out for a while, I think we can remove the (Technical preview) tag from Seam 2.3 in our tools, e.g. when you open the "Seam Web Project" dialog, you have the configuration "Dynamic web project with Seam 2.3 (Technical preview)"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12960) jboss.bind.address.management is set after unchecking Expose management port for remote server
by Martin Malina (JIRA)
Martin Malina created JBIDE-12960:
-------------------------------------
Summary: jboss.bind.address.management is set after unchecking Expose management port for remote server
Key: JBIDE-12960
URL: https://issues.jboss.org/browse/JBIDE-12960
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Beta1
Environment: JBDS 6.0.0.Beta1c B58
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
When you create a remote AS7 server and check Expose management port in the server editor, this is added to the start command:
-Djboss.bind.address.management=your.server.host.name
If you uncheck the option again, it should be removed from the command. But it's not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12965) Seam tests failures
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12965:
--------------------------------------
Summary: Seam tests failures
Key: JBIDE-12965
URL: https://issues.jboss.org/browse/JBIDE-12965
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.0.0.CR1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.0.0.CR1
{code}
testActionSourceFolderRename(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 2.074 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find source folder: /RefactoringTestProject-ejb/src
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.getSourceFolder(SeamPropertyRefactoringTest.java:297)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.renameSourceFolder(SeamPropertyRefactoringTest.java:284)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testActionSourceFolderRename(SeamPropertyRefactoringTest.java:175)
{code}
{code}
testModelSourceFolderRename(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find source folder: /RefactoringTestProject-war/src
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.getSourceFolder(SeamPropertyRefactoringTest.java:297)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.renameSourceFolder(SeamPropertyRefactoringTest.java:284)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testModelSourceFolderRename(SeamPropertyRefactoringTest.java:188)
{code}
{code}
testTestSourceFolderRename(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 0 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find source folder: /RefactoringTestProject-test/src
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.getSourceFolder(SeamPropertyRefactoringTest.java:297)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.renameSourceFolder(SeamPropertyRefactoringTest.java:284)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testTestSourceFolderRename(SeamPropertyRefactoringTest.java:201)
{code}
{code}
testViewFolderRename(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find folder: /RefactoringTestProject-war/webroot/WebContent
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.renameFolder(SeamPropertyRefactoringTest.java:318)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testViewFolderRename(SeamPropertyRefactoringTest.java:214)
{code}
{code}
testActionPackageRename(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find source folder: /RefactoringTestProject-ejb/src
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.renamePackage(SeamPropertyRefactoringTest.java:337)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testActionPackageRename(SeamPropertyRefactoringTest.java:228)
{code}
{code}
testModelPackageRename(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find source folder: /RefactoringTestProject-war/src
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.renamePackage(SeamPropertyRefactoringTest.java:337)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testModelPackageRename(SeamPropertyRefactoringTest.java:242)
{code}
{code}
testTestPackageRename(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 0 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find source folder: /RefactoringTestProject-test/src
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.renamePackage(SeamPropertyRefactoringTest.java:337)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testTestPackageRename(SeamPropertyRefactoringTest.java:256)
{code}
{code}
testViewFolderMove(org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest) Time elapsed: 0 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find folder: /RefactoringTestProject-war/webroot/WebContent
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.moveFolder(SeamPropertyRefactoringTest.java:403)
at org.jboss.tools.seam.core.test.refactoring.SeamPropertyRefactoringTest.testViewFolderMove(SeamPropertyRefactoringTest.java:269)
{code}
{code}
java.lang.NullPointerException
at org.jboss.tools.seam.core.test.SeamBigProjectGenerator.getFolderCount(SeamBigProjectGenerator.java:91)
at org.jboss.tools.seam.core.test.SeamBigProjectGenerator.generate(SeamBigProjectGenerator.java:35)
at org.jboss.tools.seam.core.test.SeamBigProjectTest.setUp(SeamBigProjectTest.java:68)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12899) Remote AS7 - an extra deployment scanner is added by default
by Martin Malina (JIRA)
Martin Malina created JBIDE-12899:
-------------------------------------
Summary: Remote AS7 - an extra deployment scanner is added by default
Key: JBIDE-12899
URL: https://issues.jboss.org/browse/JBIDE-12899
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.0.0.Beta1
When you set up a remote as7/eap6 and start the server, a second deployment scanner is added to standalone.xml on the remote server. It is set for the same dir as the default one. Thus you end up with two deployment scanners pointing to the same dir which results in weird behavior of deployments.
These are the two scanners that you can see in standalone.xml after the remote server is started:
{code}
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
<deployment-scanner name="jbosstoolsscanner1" path="/home/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/" scan-interval="5000"/>
{code}
You can see the additional scanner was added right after server start:
{code}
12:07:28,353 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 8013ms - Started 133 of 208 services (74 services are passive or on-demand)
12:07:57,071 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /home/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments
{code}
And this is what happens if you try to deploy a dynamic web project in this state:
{code}
12:09:32,999 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
12:09:37,316 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
12:09:37,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dynproj.war"
12:09:38,060 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /dynproj
12:09:38,222 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dynproj.war"
12:09:38,228 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"dynproj.war\")]"}}
12:09:48,308 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment dynproj.war in 70ms
12:09:48,461 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "dynproj.war"
12:09:53,464 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
As you can see you have two scanners noticing this war and both try to deploy it. The result is non-deterministic. Sometimes you end up with the module deployed, sometimes undeployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12798) Allow connections (users) to get labeled
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-12798:
----------------------------------------
Summary: Allow connections (users) to get labeled
Key: JBIDE-12798
URL: https://issues.jboss.org/browse/JBIDE-12798
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Affects Versions: 4.0.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.0.x
We're currently using username + password to connect to an OpenShift server. In JBIDE-12572 we now added a server-url to be able to connect to different user (without changing the express.conf files).
We should now add the ability to introduce labels for the connections. When you would look at / edit the connections you would now furthermore supply a lable. When launching the application wizard you would then choose the connection (by its name).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12901) Show in File Browser shows error for EAP 5.1.2
by Martin Malina (JIRA)
Martin Malina created JBIDE-12901:
-------------------------------------
Summary: Show in File Browser shows error for EAP 5.1.2
Key: JBIDE-12901
URL: https://issues.jboss.org/browse/JBIDE-12901
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Beta1
Environment: JBDS 6.0.0.Beta1 B45
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.Beta1
When you try to see what's in the deployment folder of a remote EAP 5.1.2 server, you will get an error (but the Remote System explorer will be opened correctly and will show the files).
{code}
Problems occurred when invoking code from plug-in: "org.eclipse.jface".
java.lang.ClassCastException: org.eclipse.core.internal.resources.Folder cannot be cast to org.eclipse.core.resources.IFile
at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getLocalResource(SystemViewRemoteFileAdapter.java:632)
at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getImageDescriptor(SystemViewRemoteFileAdapter.java:574)
at org.eclipse.rse.ui.view.SystemTableViewProvider.getImage(SystemTableViewProvider.java:236)
at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:85)
at org.eclipse.rse.internal.ui.view.SystemDecoratingLabelProvider.getColumnImage(SystemDecoratingLabelProvider.java:46)
at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:71)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:399)
at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:277)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:757)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636)
at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590)
at org.eclipse.rse.ui.view.SystemTableView.inputChanged(SystemTableView.java:479)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690)
at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1599)
at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1578)
at org.jboss.ide.eclipse.as.rse.ui.SystemShowInTableAction.run(SystemShowInTableAction.java:77)
at org.jboss.ide.eclipse.as.rse.ui.RSEDeploymentPreferenceUI$2.openExplorer(RSEDeploymentPreferenceUI.java:115)
at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:89)
at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:83)
at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.access$0(ExploreActionProvider.java:82)
at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider$1.run(ExploreActionProvider.java:74)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12800) Put org.jboss.tools.central.themes in category.
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-12800:
----------------------------------
Summary: Put org.jboss.tools.central.themes in category.
Key: JBIDE-12800
URL: https://issues.jboss.org/browse/JBIDE-12800
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: updatesite
Affects Versions: 4.0.0.Alpha2
Reporter: Radim Hopp
Assignee: Nick Boldt
Fix For: 4.0.0.Beta1
Plugin for theming was added in JBIDE-12552, but it isn't shown in any category.
Please, figure out some place (category) to put org.jboss.tools.central.themes.feature.
Now, only way to install org.jboss.tools.central.themes.feature is to install org.jboss.tools.central.themes.feature.source.feature.group and org.jboss.tools.central.themes.feature gets installed as dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months