May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14368) forge view is stuck (no input accepted, stop is not responding) if I edit the runtime

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14368?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14368: ------------------------------------- Steps to Reproduce: 1) ASSERT: make sure you have a local forge runtime installed on your harddrive and added in the forge preferences 2) ASSERT: make sure forge tooling is running on local runtime !local-runtime.png! 3) ASSERT: make sure you have the Forge view opened and forge running !forge-is-running.png! 4) EXEC: in the forge preferences hit *Edit* but dont change anything. Simply hit "OK" and close your preferences Result: Once you get back from preferences the forge view is not responding. You cannot enter any input and the *Stop* button is not responding either. 5) EXEC: close the forge view and reopen it: Result: The forge view is telling you that the forge runtime is not running: !forge-is-not-running.png! It pretty much looks like as if editing the runtime kills the runtime without the view noticing it. was: 1) ASSERT: make sure you have a local forge runtime installed on your harddrive and added in the forge preferences 2) ASSERT: make sure forge tooling is running on local runtime !local-runtime.png! 3) ASSERT: make sure you have the Forge view opened and forge running !forge-is-running.png! 4) EXEC: in the forge preferences hit *Edit* but dont change anything. Simply hit "OK" and close your preferences Result: Once you get back from preferences the forge view is not responding. You cannot enter any input and the *Stop* button is not responding either. 5) EXEC: close the forge view and reopen it: Result: The forge view is telling you that the forge runtime is not running: !forge-is-not-running.png! It pretty much looks like as if editing the runtime kills the runtime without the view noticing it. > forge view is stuck (no input accepted, stop is not responding) if I edit the runtime > ------------------------------------------------------------------------------------- > > Key: JBIDE-14368 > URL: https://issues.jboss.org/browse/JBIDE-14368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Koen Aers > Attachments: forge-is-not-running.png, forge-is-running.png, local-runtime.png > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14368) forge view is stuck (no input accepted, stop is not responding) if I edit the runtime

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-14368: ---------------------------------------- Summary: forge view is stuck (no input accepted, stop is not responding) if I edit the runtime Key: JBIDE-14368 URL: https://issues.jboss.org/browse/JBIDE-14368 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Koen Aers Attachments: forge-is-not-running.png, forge-is-running.png, local-runtime.png -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14368) forge view is stuck (no input accepted, stop is not responding) if I edit the runtime

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14368?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14368: ------------------------------------- Attachment: local-runtime.png forge-is-running.png forge-is-not-running.png > forge view is stuck (no input accepted, stop is not responding) if I edit the runtime > ------------------------------------------------------------------------------------- > > Key: JBIDE-14368 > URL: https://issues.jboss.org/browse/JBIDE-14368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Koen Aers > Attachments: forge-is-not-running.png, forge-is-running.png, local-runtime.png > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-310) redirect /latest to /reference where the latest released docs can be found

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-310?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TOOLSDOC-310: ---------------------------------------------- that is for another jira - but in general download.jboss.org is backed up so we can recover from that (should get that tested). And finally - I don't think we should actually have any html on this site that is not part of the generated and uploaded content. i.e. other projects just let apache generate the index for the download. > redirect /latest to /reference where the latest released docs can be found > -------------------------------------------------------------------------- > > Key: TOOLSDOC-310 > URL: https://issues.jboss.org/browse/TOOLSDOC-310 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > for some reason https://github.com/jbosstools/jbosstools-documentation/pull/48 removed the latest link assuming latest is used to point to the nightly build. > That is not what it is for. > It is to point to the latest docs made available. > This link (before: http://docs.jboss.org/tools/latest/) was used to point to the last latest documentation. > I believe this should be put back since this is how other docs refer to the latest version. > We could even go so ar to create a docs.jboss.org/tools/4.0, docs.jboss.org/tools/3.3 etc. folder each with their /latest link in them. > Latest links are trivial to make with sftp as part of the release upload anyway thus should be all possible to script if it is too cumbersome to remember. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13850) Filtering libraries in Source Lookup plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13850?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13850: --------------------------------------------- where is that preference for a filter ? I couldn't spot it ? debugging is not for advanced users IMO; its for normal users. But even advanced nor normal users should have to specify regular expressions for something as comon as having old libraries duplicated. Can't we make it more intelligent and choose the newest out of possibly many matches ? > Filtering libraries in Source Lookup plugin > ------------------------------------------- > > Key: JBIDE-13850 > URL: https://issues.jboss.org/browse/JBIDE-13850 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > jsf 1.2 and hibernate 3 will be excluded by default for the JBoss AS Container -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13283 at 5/2/13 5:16 AM: ---------------------------------------------------------------- Some metrics before we can try Akamai: with TP from commit [773a5a40012f06c057a44309235843b6cc670aff|https://github.com/jbosstools/jb...] (no pack.gz, no Akamai), resolved from my office in Grenoble on a Kepler 20130320-2352, clicking "Set As Target Platform" on jbosstools-multiple.target took me *13m37s* was (Author: mickael_istria): Some metrics: with TP from commit 773a5a40012f06c057a44309235843b6cc670aff (no pack.gz, no Akamai), resolved from my office in Grenoble on a Kepler 20130320-2352, clicking "Set As Target Platform" took me *13m37s* > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, target-platform, updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14367) Add helloworls-rs quickstart to central

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-14367: ---------------------------------- Summary: Add helloworls-rs quickstart to central Key: JBIDE-14367 URL: https://issues.jboss.org/browse/JBIDE-14367 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central, project-examples Reporter: Radim Hopp jax-rs-client quickstart has helloworld-rs as prerequisite, but helloworld-rs is not present in project examples in JBT. I think it would make sense to add this quickstart to central, OR at least mention in jax-rs-client readme where could be helloworld-rs obtained from. WDYT? -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-2720: -------------------------------------------- well, bitbucket.org can be used for mercurial if github is not possible ;) > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Yahor Radtsevich > Fix For: 4.0.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, mozconfig1, mozconfig2 > > > If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for windows 64 bit. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13283: --------------------------------------------- [~mickael_istria] which repo/which commit ? and 13m37s compared to what ? > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, target-platform, updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14340) "Searching for runtimes" dialog is opened whenever starting JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14340?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14340: --------------------------------------------- i looked at the patch - was this just completely broken since it is just a negation of an if statement. and where are the tests for runtimExists ? this code looks like it is doing much more than just check the runtimes exists. > "Searching for runtimes" dialog is opened whenever starting JBDS > ---------------------------------------------------------------- > > Key: JBIDE-14340 > URL: https://issues.jboss.org/browse/JBIDE-14340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.0.Beta1 > > > The dialog shouldn't be opened if the corresponding server is created. -- 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

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2013