[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 updated JBIDE-23647:
------------------------------------
Fix Version/s: 4.4.x
> 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
> Fix For: 4.4.x
>
> 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)
7 years, 5 months
[JBoss JIRA] (JBIDE-23645) Remove org.jboss.tools.ui.bot.ext from integration tests
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23645?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23645:
----------------------------------
Fix Version/s: 4.4.3.AM2
> Remove org.jboss.tools.ui.bot.ext from integration tests
> --------------------------------------------------------
>
> Key: JBIDE-23645
> URL: https://issues.jboss.org/browse/JBIDE-23645
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.4.3.AM2
>
>
> org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext.
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
> This was previously discussed in JBIDE-23593 where I found the following tests that still use bot.ext.
> I found out that some tests still use bot.ext:
> {code}
> $ find . -iname 'manifest.mf' -path '*/META-INF/*'|xargs grep 'ui\.bot\.ext'|sed 's/:.*//'|uniq
> ./plugins/org.jboss.tools.jst.ui.bot/META-INF/MANIFEST.MF
> ./plugins/org.jboss.tools.ui.bot.ext/META-INF/MANIFEST.MF
> ./tests/org.jboss.tools.portlet.ui.bot.test/META-INF/MANIFEST.MF
> ./tests/org.jboss.tools.seam.ui.bot.test/META-INF/MANIFEST.MF
> ./tests/org.jboss.tools.ws.ui.bot.test/META-INF/MANIFEST.MF
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23302:
------------------------------------
>From Ryszard:
> Here is the commit I’ve done for bootstrap-community https://github.com/jbossorg/bootstrap-community/commit/e2dc8a990b3641e995... So you can either try merging it to your repo or just repeat the same what I did which is find in all files “http://static.jboss.org/“ and replace it with “//static.jboss.org/“.
> Actually I realised that on your staging and prod sites you’ll probably use the minimalised CSS/JS versions and I need to push them to static.jboss.org. I’ll do that now.
> Ok pushed the new versions, I hope they will work. You’ll need to update your _config/site.yml https://static.jboss.org/theme/css/bootstrap-community/2.3.1.6/ and https://static.jboss.org/theme/js/libs/bootstrap-community/2.3.1.6/
Xavier's changes to move up to the new bootstrap [1] are live in https://tools.stage.jboss.org/ and fonts are now appearing as expected when compared to http://tools.stage.jboss.org/
Xavier has pushed the change to our production branch too, so changes should appear shortly on https://tools.jboss.org/
We're ready to enable https (instead of the redirect) on tools.jboss.org, whenever you guys are ready to flip the switch.
[1] https://github.com/jbosstools/jbosstools-website/commits/production
> https no longer working on tools.jboss.org
> ------------------------------------------
>
> Key: JBIDE-23302
> URL: https://issues.jboss.org/browse/JBIDE-23302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, website
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Fix For: 4.4.3.AM1
>
> Attachments: image.png, stage-http.png, stage.png
>
>
> Is it expected that tools.jboss.org no longer provides https?
> https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg:
> {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901
> {code}
> To see this in action, go here:
> https://tools.jboss.org --> redirects to http://tools.jboss.org
> or, go here:
> https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org
> I bet this is a problem for eng-ops@ or the new PnT portal.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ]
Aurélien Pupier commented on JBTIS-1008:
----------------------------------------
I was wrong, it doesn't work neither with "installation" mode, I think that I had a CDK already running when i tried using it.
so need to deal with the issue that I see when using the zip as local "software site"
> Provide OpenShift 3 support feature in Integration Stack Target Platform
> ------------------------------------------------------------------------
>
> Key: JBTIS-1008
> URL: https://issues.jboss.org/browse/JBTIS-1008
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: screenshot-1.png
>
>
> My goal is to be able to leverage OpenShift 3 and CDK integration.
> I think that the required feature is org.jboss.tools.openshift.feature
> [~adietish]Can you confirm that it is the right feature?
> *Reason:* Leverage OpenShift 3 and CDK integration.
> *Project page/sources:*
> *Version:* 3.3.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* .devstudiois
> *Include in JBDS:* Yes (DevtsudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months