January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16395) Generate new content in New Header wizard for JQM 1.4

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16395?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16395: ----------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Generate new content in New Header wizard for JQM 1.4 > ----------------------------------------------------- > > Key: JBIDE-16395 > URL: https://issues.jboss.org/browse/JBIDE-16395 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: scr.png > > > The automatical enhancement of links in toolbars as buttons with inline and mini style, as well as positioning the first two buttons in a header left and right, is deprecated in JQM 1.4 and will be removed in JQM 1.5. > In JQM 1.4, buttons should be set with classes, i.e. positioning is set by 'ui-btn-left' and 'ui-btn-right'. > For JQM 1.4 wizard should generate code > {code} > <div data-role="header"> > <a href="#" class="ui-btn-left ui-btn ui-btn-inline ui-mini ui-corner-all ui-btn-icon-left ui-icon-delete">Cancel</a> > <h1>My App</h1> > <a href="#" class="ui-btn-right ui-btn ui-btn-inline ui-mini ui-corner-all ui-icon-check">Save</a> > </div>{code} > Input controls of wizards in both versions can be the same -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16395) Generate new content in New Header wizard for JQM 1.4

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16395?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16395: ----------------------------------- Attachment: scr.png !scr.png! > Generate new content in New Header wizard for JQM 1.4 > ----------------------------------------------------- > > Key: JBIDE-16395 > URL: https://issues.jboss.org/browse/JBIDE-16395 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: scr.png > > > The automatical enhancement of links in toolbars as buttons with inline and mini style, as well as positioning the first two buttons in a header left and right, is deprecated in JQM 1.4 and will be removed in JQM 1.5. > In JQM 1.4, buttons should be set with classes, i.e. positioning is set by 'ui-btn-left' and 'ui-btn-right'. > For JQM 1.4 wizard should generate code > {code} > <div data-role="header"> > <a href="#" class="ui-btn-left ui-btn ui-btn-inline ui-mini ui-corner-all ui-btn-icon-left ui-icon-delete">Cancel</a> > <h1>My App</h1> > <a href="#" class="ui-btn-right ui-btn ui-btn-inline ui-mini ui-corner-all ui-icon-check">Save</a> > </div>{code} > Input controls of wizards in both versions can be the same -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16330) Deployment to Android emulator ignores saved run configuration

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16330?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16330: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Priority: Minor (was: Major) > Deployment to Android emulator ignores saved run configuration > -------------------------------------------------------------- > > Key: JBIDE-16330 > URL: https://issues.jboss.org/browse/JBIDE-16330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Priority: Minor > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The deployment to an emulator is always performed on a currently running AVD even if the runtime config for the project specifies a different AVD. > Ignore/reject if this is by design. But from the point of view of the user, it would be better to ensure consistency - when a user wants to run his project on a specific AVD, he needs to create a runtime config, but the moment a different AVD is running, this config is ignored. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16330) Deployment to Android emulator ignores saved run configuration

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16330?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16330: -------------------------------------- It does try to minimize the number of emulator instances to save on resources. I guess we can ask to restart the instance in case of an edit to selected AVD on launch configuration or just give a warning > Deployment to Android emulator ignores saved run configuration > -------------------------------------------------------------- > > Key: JBIDE-16330 > URL: https://issues.jboss.org/browse/JBIDE-16330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Priority: Minor > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The deployment to an emulator is always performed on a currently running AVD even if the runtime config for the project specifies a different AVD. > Ignore/reject if this is by design. But from the point of view of the user, it would be better to ensure consistency - when a user wants to run his project on a specific AVD, he needs to create a runtime config, but the moment a different AVD is running, this config is ignored. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16400) Timeout shutdown poller does not wait for timeout

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16400?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-16400: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 Description: When you select "Timeout" as the Shutdown poller in server editor, one would expect the server to show stopped only after the timeout has elapsed (like it happens with the Timeout startup poller). Instead, the server is shown instantly once you stop the server. Steps to Reproduce: 1. Add EAP 6.2 as a server 2. Open the server editor by double-clicking the server in the server view 3. Select both startup and shutdown pollers to "timeout" and save the editor 4. Start the server (by clicking the start button in the server view) Server will be in the "Starting" state until the timeout is reached - good 5. Stop the server (by clicking the stop button in the server view) Server will switch to "Stopped" immediately - FAIL - it should wait for the timeout Affects Version/s: 4.1.1.Final Environment: JBDS 7.1.0.GA EAP 6.2.0 Component/s: server > Timeout shutdown poller does not wait for timeout > ------------------------------------------------- > > Key: JBIDE-16400 > URL: https://issues.jboss.org/browse/JBIDE-16400 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Final > Environment: JBDS 7.1.0.GA > EAP 6.2.0 > Reporter: Martin Malina > Fix For: 4.2.0.Alpha2 > > > When you select "Timeout" as the Shutdown poller in server editor, one would expect the server to show stopped only after the timeout has elapsed (like it happens with the Timeout startup poller). Instead, the server is shown instantly once you stop the server. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16400) Timeout shutdown poller does not wait for timeout

by Martin Malina (JIRA)

Martin Malina created JBIDE-16400: ------------------------------------- Summary: Timeout shutdown poller does not wait for timeout Key: JBIDE-16400 URL: https://issues.jboss.org/browse/JBIDE-16400 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Martin Malina -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16392) Application wizard: application type is not stored/restored from preferences

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16392?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-16392: ---------------------------------------- Assignee: Andre Dietisheim > Application wizard: application type is not stored/restored from preferences > ---------------------------------------------------------------------------- > > Key: JBIDE-16392 > URL: https://issues.jboss.org/browse/JBIDE-16392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: application-type-empty.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2849) Document Offline Usage

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-2849: ------------------------------------ Don't forget the maven repo. I'm glad that Jim mentioned this. > Document Offline Usage > ---------------------- > > Key: JBDS-2849 > URL: https://issues.jboss.org/browse/JBDS-2849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > Assignee: Michelle Murray > > Working with the Training team, document how JBDS is to be used in an offline state. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16399) Forge start failure is not reported

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-16399: ------------------------------------- Summary: Forge start failure is not reported Key: JBIDE-16399 URL: https://issues.jboss.org/browse/JBIDE-16399 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.0.Alpha2 Reporter: Denis Golovin Priority: Critical If there is an error in Forge startup VM parameters forge console is not starting with zero error messages. Eclipse Error Log View and system output are empty. Forge console says "Forge is not running ........." forever. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2851) Team Usability

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-2851: ------------------------------------ Are we talking about a pure-documentation solution to this? Or - are we going to build some new wizards? > Team Usability > -------------- > > Key: JBDS-2851 > URL: https://issues.jboss.org/browse/JBDS-2851 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > > It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as > - how to integrate with CVS, SVN, Git > - how to "import" a Maven-based project from SCM > "Check out Maven Projects from SCM" has misfired for some users > - how to "checkin" changes back to the SCM > To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things. > For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically. -- 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, 5 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 January 2014