[JBoss JIRA] (JBIDE-23649) [baseline compare check] plugins in jbosstools-webservices need to be upversioned so they're greater than versions in last stable jbosstools site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23649?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23649:
-------------------------------
Component/s: webservices
(was: server)
> [baseline compare check] plugins in jbosstools-webservices need to be upversioned so they're greater than versions in last stable jbosstools site
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23649
> URL: https://issues.jboss.org/browse/JBIDE-23649
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
>
> Building jbosstools-server from master branch, after releasing JBoss Tools 4.4.2.Final to the stable site [1] on Dec 8 last week:
> {code}
> mvn clean install -DskipTests -DskipBaselineComparison=false{code}
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.archives.ui: Duplicate version but different content found for (org.jboss.ide.eclipse.archives.ui/3.6.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.archives.scanner.feature: Duplicate version but different content found for (org.jboss.tools.archives.scanner.feature.feature.jar/3.6.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.classpath.core: Duplicate version but different content found for (org.jboss.ide.eclipse.as.classpath.core/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.doc.user: Duplicate version but different content found for (org.jboss.ide.eclipse.as.doc.user/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.ui.mbeans: Duplicate version but different content found for (org.jboss.ide.eclipse.as.ui.mbeans/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.rse.core: Duplicate version but different content found for (org.jboss.ide.eclipse.as.rse.core/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.management.as7: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.as7/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.management.eap61plus: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.eap61plus/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.management.wildfly9: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.wildfly9/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.as.catalog: Duplicate version but different content found for (org.jboss.tools.as.catalog/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.jmx.local: Duplicate version but different content found for (org.jboss.tools.jmx.local/1.8.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.wtp.runtimes.tomcat: Duplicate version but different content found for (org.jboss.tools.wtp.runtimes.tomcat/1.3.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.wtp.server.launchbar.feature: Duplicate version but different content found for (org.jboss.tools.wtp.server.launchbar.feature.source.feature.jar/1.3.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> {code}
> [1] <lastStableRepository>http://download.jboss.org/jbosstools/neon/stable/updates/</lastStableRepository> - https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23648) integration tests: ImageTagTest tries to assert that uppercase tags cannot be added to docker images, but it fails to
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23648?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23648:
-------------------------------------
Fix Version/s: 4.4.3.AM1
> integration tests: ImageTagTest tries to assert that uppercase tags cannot be added to docker images, but it fails to
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23648
> URL: https://issues.jboss.org/browse/JBIDE-23648
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, integration-tests
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.3.AM1
>
>
> ImageTagTest tries to assert that uppercase tags cannot be added to docker images. But it has 2 flaws:
> * it tries to assert the existence of an error dialog (when providing an uppercase tag) via
> {code}new ShellWithTextIsAvailable("Error tagging image to <" + imageTagUppercase + ">"){code}
> but ShellWithTextIsAvailable is an AbstractWaitCondition. So it has no effect at all
> * the docker tooling wont prevent you from providing an uppercase tag. It will actually accept it, send it to the daemon and then display it. No error occurrs. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=509223
> The assertion itself is absolutely correct. The cmd line wont accept uppercase letters in a tag.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23648) integration tests: ImageTagTest tries to assert that uppercase tags cannot be added to docker images, but it fails to
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23648:
----------------------------------------
Summary: integration tests: ImageTagTest tries to assert that uppercase tags cannot be added to docker images, but it fails to
Key: JBIDE-23648
URL: https://issues.jboss.org/browse/JBIDE-23648
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: docker, integration-tests
Affects Versions: 4.4.2.Final
Reporter: Andre Dietisheim
ImageTagTest tries to assert that uppercase tags cannot be added to docker images. But it has 2 flaws:
* it tries to assert the existence of an error dialog (when providing an uppercase tag) via
{code}new ShellWithTextIsAvailable("Error tagging image to <" + imageTagUppercase + ">"){code}
but ShellWithTextIsAvailable is an AbstractWaitCondition. So it has no effect at all
* the docker tooling wont prevent you from providing an uppercase tag. It will actually accept it, send it to the daemon and then display it. No error occurrs. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=509223
The assertion itself is absolutely correct. The cmd line wont accept uppercase letters in a tag.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23647?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-23647:
-----------------------------------------
That makes sense. It definitely looks like a bug.
> UI freeze while trying to starting the forge runtime
> ----------------------------------------------------
>
> Key: JBIDE-23647
> URL: https://issues.jboss.org/browse/JBIDE-23647
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Attachments: image-2016-12-14-18-17-34-950.png
>
>
> maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
> I hit Ctrl+4 and then the UI is blocked:
> !image-2016-12-14-18-17-34-950.png|thumbnail!
> I have this stack in logs
> {noformat}
> Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
> SEVERE: Error occurred.
> java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
> at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23647?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23647:
-----------------------------------------
I'm not sure that we should write in the jar even if it is exploded on a JBDS installation. We should better use a workspace settings, what do you think?
> UI freeze while trying to starting the forge runtime
> ----------------------------------------------------
>
> Key: JBIDE-23647
> URL: https://issues.jboss.org/browse/JBIDE-23647
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Attachments: image-2016-12-14-18-17-34-950.png
>
>
> maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
> I hit Ctrl+4 and then the UI is blocked:
> !image-2016-12-14-18-17-34-950.png|thumbnail!
> I have this stack in logs
> {noformat}
> Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
> SEVERE: Error occurred.
> java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
> at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23647?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-23647 at 12/14/16 12:59 PM:
--------------------------------------------------------------------
I would say that it is because it is in a jar which is not exploded in the target platform
was (Author: aurelien.pupier):
I would say that it is because it is in a jar
> UI freeze while trying to starting the forge runtime
> ----------------------------------------------------
>
> Key: JBIDE-23647
> URL: https://issues.jboss.org/browse/JBIDE-23647
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Attachments: image-2016-12-14-18-17-34-950.png
>
>
> maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
> I hit Ctrl+4 and then the UI is blocked:
> !image-2016-12-14-18-17-34-950.png|thumbnail!
> I have this stack in logs
> {noformat}
> Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
> SEVERE: Error occurred.
> java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
> at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23647?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23647:
-----------------------------------------
I would say that it is because it is in a jar
> UI freeze while trying to starting the forge runtime
> ----------------------------------------------------
>
> Key: JBIDE-23647
> URL: https://issues.jboss.org/browse/JBIDE-23647
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Attachments: image-2016-12-14-18-17-34-950.png
>
>
> maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
> I hit Ctrl+4 and then the UI is blocked:
> !image-2016-12-14-18-17-34-950.png|thumbnail!
> I have this stack in logs
> {noformat}
> Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
> SEVERE: Error occurred.
> java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
> at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23647?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-23647:
-----------------------------------------
That error seems to be the reason why it doesn't start. Can you investigate why that directory cannot be created?
> UI freeze while trying to starting the forge runtime
> ----------------------------------------------------
>
> Key: JBIDE-23647
> URL: https://issues.jboss.org/browse/JBIDE-23647
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Attachments: image-2016-12-14-18-17-34-950.png
>
>
> maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
> I hit Ctrl+4 and then the UI is blocked:
> !image-2016-12-14-18-17-34-950.png|thumbnail!
> I have this stack in logs
> {noformat}
> Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
> SEVERE: Error occurred.
> java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
> at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-3595) dark theme not nice
by Todd Mancini (JIRA)
[ https://issues.jboss.org/browse/JBDS-3595?page=com.atlassian.jira.plugin.... ]
Todd Mancini commented on JBDS-3595:
------------------------------------
I'm willing to consider as part of the January PDD planning process. Let's defer until that discussion.
> dark theme not nice
> -------------------
>
> Key: JBDS-3595
> URL: https://issues.jboss.org/browse/JBDS-3595
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 9.1.0.Beta2
> Reporter: Aleksandar Kostadinov
> Priority: Minor
> Fix For: 10.x
>
> Attachments: jbds_dark.png
>
>
> Selecting "Dark" them in appearance yields somehow ugly result. Would be nice to be fixed.
> !jbds_dark.png|thumbnail!
> btw have installed GoClipse, not sure if that matters. Have not checked dark theme before install.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months