[JBoss JIRA] (JBIDE-18415) Forge New Project wizard - no Archetype catalogues listed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18415?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18415:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
> Forge New Project wizard - no Archetype catalogues listed
> ---------------------------------------------------------
>
> Key: JBIDE-18415
> URL: https://issues.jboss.org/browse/JBIDE-18415
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR1
> Reporter: Michelle Murray
> Assignee: George Gastaldi
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> Forge 2 New Project wizard lists no catalogs for 'From Archetype Catalog' project option.
> * Ctrl+4
> * New Project
> * Project name: blah
> * Project type: From Archetype Catalog >> no options for Catalog or Archetype
> Could this list be populated by Preferences > Maven > Archetypes > Archetype Catalog Table? And have a link in the wizard to this preference page for users to quickly add another catalog? (Like the OpenShift wizard has a link to SSH Preferences for adding private key to IDE in middle of wizard.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18456) Central connectors linked to earlyaccess URLs
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18456:
--------------------------------------
Summary: Central connectors linked to earlyaccess URLs
Key: JBIDE-18456
URL: https://issues.jboss.org/browse/JBIDE-18456
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: discovery
Affects Versions: 4.2.0.CR1
Reporter: Mickael Istria
Some connectors on Central are actually linking to Early Access URLs. They should point to the main URL (8.0-staging/).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18455) UI freeze when using server view on remote servers
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18455?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18455:
----------------------------------------
Fix Version/s: 4.2.0.CR2
> UI freeze when using server view on remote servers
> --------------------------------------------------
>
> Key: JBIDE-18455
> URL: https://issues.jboss.org/browse/JBIDE-18455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> create a remote server
> start it
> now when trying to use the server view with this server things freezes for several seconds.
> stacktrace shows it is blocking the main thread.
> full jstacktrace here: https://gist.github.com/maxandersen/51575583ba5877eb48ec
> important part here:
> {code}
> "main" prio=5 tid=0x0000000102870000 nid=0x513 in Object.wait() [0x00007fff5fbf9000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000007f492b908> (a java.lang.Object)
> at org.xnio.AbstractIoFuture.await(AbstractIoFuture.java:101)
> - locked <0x00000007f492b908> (a java.lang.Object)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:101)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> - locked <0x00000007f492a9a0> (a org.jboss.as.protocol.ProtocolConnectionManager)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144)
> - locked <0x00000007f491a368> (a org.jboss.as.controller.client.impl.RemotingModelControllerClient)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.getServerState(AS71Manager.java:266)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.getServerState(JBoss71ManagerService.java:142)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.isRunning(ManagementPublishController.java:112)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublish(ManagementPublishController.java:124)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:297)
> at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1215)
> at org.eclipse.wst.server.ui.internal.view.servers.PublishAction.accept(PublishAction.java:40)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18453) NPE while processing change in code
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18453?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18453:
----------------------------------
Fix Version/s: 4.2.0.CR2
> NPE while processing change in code
> -----------------------------------
>
> Key: JBIDE-18453
> URL: https://issues.jboss.org/browse/JBIDE-18453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> Following exception occurred while editing some code in a sample project:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:139)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:73)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:57)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months