[JBoss JIRA] (JBIDE-19567) Thym doesn't support JGit 4.0
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19567?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19567:
----------------------------------------
Newer Thym is mirrored at http://download.jboss.org/jbosstools/updates/requirements/thym/0.2.0-SNAP...
I'm not sure I fully understand how updating a Thym version should work now that it's moved out of .target file. Do you know what's to update?
> Thym doesn't support JGit 4.0
> -----------------------------
>
> Key: JBIDE-19567
> URL: https://issues.jboss.org/browse/JBIDE-19567
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, upstream
> Reporter: Mickael Istria
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet.
> {code}[INFO] [ERROR] Cannot resolve project dependencies:
> [INFO] [ERROR] Software being installed: org.jboss.tools.aerogear.thym 1.3.0.qualifier
> [INFO] [ERROR] Missing requirement: org.eclipse.thym.core 0.1.0.201503051642 requires 'bundle org.eclipse.jgit [3.0.0,4.0.0)' but it could not be found
> [INFO] [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.thym 1.3.0.qualifier depends on: bundle org.eclipse.thym.core 0.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-423:
------------------------------------
Description:
When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log
{code}
Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources:
com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar,
com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar
{code}
was:
When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log
{code}
Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources:
com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar,
com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar
{code}
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
> ---------------------------------------------------------------------------------
>
> Key: JBTIS-423
> URL: https://issues.jboss.org/browse/JBTIS-423
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.GA
> Environment: JBDS 8.1.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
>
> When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log
> {code}
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources:
> com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar,
> com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19410:
----------------------------------------
Since the use-case for it is only the dev-mode, I believe it's more efficient to show technical error messages at that time, so contributor writing code against JBT would more quickly understand what's missing. So I'm for keeping those messages as it.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19389) Cannot set timeout configuration to connect JDV server on Teiid designer
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19389?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19389:
-------------------------------------
[~blafond] Can you re-assign this issue unless ASTools is missing API or the current API is insufficient?
> Cannot set timeout configuration to connect JDV server on Teiid designer
> ------------------------------------------------------------------------
>
> Key: JBIDE-19389
> URL: https://issues.jboss.org/browse/JBIDE-19389
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Eiichi Nagai
> Assignee: Rob Stryker
>
> Describe the issue:
> The teiid-designer cannot connect to remote JDV server by timeout exceptions. However, the teiid-designer cannnot set timeout for it.
> {noformat}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72)
> at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> 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)
> ... 23 more
> Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144)
> 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)
> ... 25 more
> {noformat}
> Additional information:
> We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years