June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12025) org.jboss.tools.forge.runtime plugin is missing Provider and Plug-in name.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12025?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-12025. ------------------------------- Resolution: Done > org.jboss.tools.forge.runtime plugin is missing Provider and Plug-in name. > -------------------------------------------------------------------------- > > Key: JBIDE-12025 > URL: https://issues.jboss.org/browse/JBIDE-12025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 3.3.0.CR1 > Reporter: Jaroslav Jankovič > Assignee: Koen Aers > Fix For: 4.1.0.Beta2 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14123) Java file should be selected in Project Explorer tab after Forge command 'entity' or 'field'

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14123?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-14123. ------------------------------- Resolution: Done > Java file should be selected in Project Explorer tab after Forge command 'entity' or 'field' > -------------------------------------------------------------------------------------------- > > Key: JBIDE-14123 > URL: https://issues.jboss.org/browse/JBIDE-14123 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Koen Aers > Fix For: 4.1.0.Beta2 > > > Not sure if this is a bug or just something that hasn't been implemented. > When you issue the command 'persistence setup' on the forge command line, the persistence.xml file is created, opened in an editor and the file is selected in the Project Explorer tab. All good. > When you issue the command 'entity', a new Java file is created and opened in an editor. It would be great if the Java file was selected in the Project Explorer tab. > Similarly, when you issue the command 'field', the appropriate Java file is opened in an editor and the field highlighted. The field is selected in the Outline tab. It would be great if the Java file was selected in the Project Explorer tab. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14441) Forge: Remove Runtime button is always disabled in Installed Forge Runtimes Preference Page

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14441?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-14441. ------------------------------- Resolution: Cannot Reproduce Bug Denis, the behaviour is indeed as Michelle indicates. I couldn't reproduce the stack trace that you pasted. Feel free to reopen if you can reproduce it. > Forge: Remove Runtime button is always disabled in Installed Forge Runtimes Preference Page > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14441 > URL: https://issues.jboss.org/browse/JBIDE-14441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Denis Golovin > Assignee: Koen Aers > Fix For: 4.1.0.Beta2 > > Attachments: Forge_enabledRemovebutton.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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14694) Cheatsheet is not opened when importing project as existing one

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14694: --------------------------------------------- [~snjeza] i still don't understand what you want to remove - can you be more specific ? got pullrequest or is it aleady fixed or ? > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14694) Cheatsheet is not opened when importing project as existing one

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14694: ---------------------------------------- Priority: Blocker (was: Major) > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14080) Browsersim > ScreenShot > Save is not clear where it saves images

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14080?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14080: --------------------------------------------- Looks much better - a few quirks: On Save (with empty save location specified) I get a file dialog that says "Save &As..." (notice the extra &). saved file is not using 24hr clock, so I got browsersim_2013-06-11-012039.png instead of browsersim_2013-06-11-132039.png Good for Beta2 :) > Browsersim > ScreenShot > Save is not clear where it saves images > ----------------------------------------------------------------- > > Key: JBIDE-14080 > URL: https://issues.jboss.org/browse/JBIDE-14080 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Beta2 > > > As a first time user of browserim clicking Screenshot > Save looks like it does nothing. > As it turns out it is actually saving funky timestamped .png's into my home folder. > I think that is a bad default behavior. > Here is my suggestion: > A) prefix the file with browsersim- (making it easier to find) > B) use a ISO date format instead of the current mix of _'s and -'s. i.e. 2013-04-17-103221.png or just 20130417103221.png > C) if user have not set preferences (i.e. blank field) ask the user on his first Save > to specify which folder to save to. > D) on Screenshot > Save show dialog stating the full path of the save file in a way that makes it possible to copy/paste the path (maybe even copy/paste it to the clipboard). > Option D could be made more smooth/better by having something like: > Title: Screenshot saved > Text: Screenshot saved to [filename]. > [ ] Copy path to clipboard > [ ] Do this always and do not show this again > [Ok] [Cancel] > And as usual have a "reset dialog settings" in preferences to reset this. > Then on first users they are informed about where the file is saved and can get to it instantly - and experienced users can just dismiss this dialog and have the action they want every time. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14074) Duplicated toolbar in Forge Console tab

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14074?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-14074. ------------------------------- Resolution: Cannot Reproduce Bug Since it cannot be reproduced anymore. > Duplicated toolbar in Forge Console tab > --------------------------------------- > > Key: JBIDE-14074 > URL: https://issues.jboss.org/browse/JBIDE-14074 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Koen Aers > Priority: Minor > Fix For: 4.1.0.Beta2 > > Attachments: data source explorer.png, Forge_twomenubars.png, Forge_twomenubars2.png > > > The toolbar in the Forge Console tab is duplicated - there are two of each button. See attached screen capture. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14834) bump parent pom version used in root pom to Beta2

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-14834: ---------------------------------- Summary: bump parent pom version used in root pom to Beta2 Key: JBIDE-14834 URL: https://issues.jboss.org/browse/JBIDE-14834 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid Affects Versions: 4.1.0.Beta2 Reporter: Nick Boldt please apply this: https://github.com/jbosstools/jbosstools-aerogear/pull/4 -- 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, 10 months

1
0
0 / 0

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-2720: --------------------------------------- Best workflow for adopters would be to include it directly in JBT and JBDS. Will the plugin require fixes, or can we think it as "done"? If changes can happen, it's better to include it in JBT site (as an uncategorized dependency) so it has the same development process as our code. If it's done and if we're not about to change it soon, it would make sense to make it a requirement part of the target-platform. > 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.1.0.Beta2 > > 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, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14760) Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14760?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-14760: ------------------------------------------------- Jason DeTiberus <jdetiber(a)redhat.com> changed the Status of [bug 970805|https://bugzilla.redhat.com/show_bug.cgi?id=970805] from ASSIGNED to MODIFIED > Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-14760 > URL: https://issues.jboss.org/browse/JBIDE-14760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Environment: jdk7 > Reporter: jing zh > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > Attachments: JBT_test.png > > > If trying to connect openshift server ,it would be failed with following error shown. > Could not verify credentials for jinzhang1: Could not request https://broker.osetestv2.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name -- 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, 10 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 June 2013