April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16976) OpenShift import: Error dialog after importing application without SSH key on PaaS is not enough descriptive

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16976?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-16976: ---------------------------------- Attachment: error_dialog.png > OpenShift import: Error dialog after importing application without SSH key on PaaS is not enough descriptive > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16976 > URL: https://issues.jboss.org/browse/JBIDE-16976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Attachments: error_dialog.png > > > When creating application and following import (git clone after creation process is completed) in case of no SSH key/not added into preferences shell there is a error dialog with description, that something went wrong during git clone (respectively creating local git repo) and exception thrown. > !error_dialog.png! > It would be nice to have in the dialog, that problem is caused by missing SSH key or at least remove InvocationTargetException from error message - it is useless for user. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16822) Dark text on dark background in Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16822?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-16822. ------------------------------ Resolution: Done Indeed. The reason I was able to replicate this issue was that the Beta1a build we got was actually Beta1 (without respin-a). I've tried it on "new" Beta1a' build and it's ok now. > Dark text on dark background in Central > --------------------------------------- > > Key: JBIDE-16822 > URL: https://issues.jboss.org/browse/JBIDE-16822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.2.CR1, 4.2.0.Alpha2 > Environment: Fedora 20, KDE 4.12.3, Oxygen color theme > Reporter: Radim Hopp > Assignee: Snjezana Peco > Labels: respin-a > Fix For: 4.2.0.Beta1 > > Attachments: central-popup.png, centralHoverColors.png > > > There is dark text on dark background in hover popup of project examples. > See screenshot: > !central-popup.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16975) jQuery Mobile palette: add drop-down list identifier to version

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16975?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16975: ------------------------------------ Fix Version/s: (was: 4.2.0.Beta1) > jQuery Mobile palette: add drop-down list identifier to version > --------------------------------------------------------------- > > Key: JBIDE-16975 > URL: https://issues.jboss.org/browse/JBIDE-16975 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > > The implementation for multiple jQuery Mobile palette versions is very clean. But I'm not sure users will intuitively know that they can click on the version number to see a list of available versions and change the version. > Can a downwards arrowhead be added next to the version number to clarify this? Like in the OpenShift Application connection wizard where the connection field has a downwards arrowhead at the end of the value, or the new server wizard where the profile field has a downwards arrowhead at the end of the value. In both of these the downwards arrowhead immediately signifies to user to click here to see more options. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16975) jQuery Mobile palette: add drop-down list identifier to version

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-16975: --------------------------------------- Summary: jQuery Mobile palette: add drop-down list identifier to version Key: JBIDE-16975 URL: https://issues.jboss.org/browse/JBIDE-16975 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.Beta1 Reporter: Michelle Murray Fix For: 4.2.0.Beta1 The implementation for multiple jQuery Mobile palette versions is very clean. But I'm not sure users will intuitively know that they can click on the version number to see a list of available versions and change the version. Can a downwards arrowhead be added next to the version number to clarify this? Like in the OpenShift Application connection wizard where the connection field has a downwards arrowhead at the end of the value, or the new server wizard where the profile field has a downwards arrowhead at the end of the value. In both of these the downwards arrowhead immediately signifies to user to click here to see more options. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-485) Add info on multiple jQuery Mobile versions in Palette view

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-485: ---------------------------------------- Summary: Add info on multiple jQuery Mobile versions in Palette view Key: TOOLSDOC-485 URL: https://issues.jboss.org/browse/TOOLSDOC-485 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Enhancement Security Level: Public (Everyone can see) Components: User Guide - Mobile Web Tools Affects Versions: 4.2.0.Beta1 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.2.0.Beta1 Use Case: New version of jQuery Mobile is available and Mobile Web Tools has been extended to accommodate it. Feature: The palette view now supports jQuery Mobile 1.4. The palette detects the jQuery Mobile JS file version used in the HTML file and switches to the corresponding version: 1.3 or 14. It also can be switched manually. jQuery Mobile Palette v1.4 has its own set of wizards. Writer Task: Edit topic 22847. Include info on how to switch between jQuery Mobile versions in palette and that appropriate one is selected by default based on file in editor. Create a new screen cap for figure 'jQuery Mobile Palette in the Palette View' showing 1.4 version. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-485) Add info on multiple jQuery Mobile versions in Palette view

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-485?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-485: ------------------------------------- Sprint: 2014/S5 (31-Mar > 13-Apr) > Add info on multiple jQuery Mobile versions in Palette view > ----------------------------------------------------------- > > Key: TOOLSDOC-485 > URL: https://issues.jboss.org/browse/TOOLSDOC-485 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: User Guide - Mobile Web Tools > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Beta1 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > Use Case: New version of jQuery Mobile is available and Mobile Web Tools has been extended to accommodate it. > Feature: The palette view now supports jQuery Mobile 1.4. The palette detects the jQuery Mobile JS file version used in the HTML file and switches to the corresponding version: 1.3 or 14. It also can be switched manually. jQuery Mobile Palette v1.4 has its own set of wizards. > Writer Task: Edit topic 22847. Include info on how to switch between jQuery Mobile versions in palette and that appropriate one is selected by default based on file in editor. Create a new screen cap for figure 'jQuery Mobile Palette in the Palette View' showing 1.4 version. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2971) Verify VJET/0.10.0.201402070708 with JBDS 8.0

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2971?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-2971: ------------------------------------- We would want newer version if they were some bug fixes - unfortunately, I didn't find fixed anything worth (patch fixing JBIDE-16164 still not applied. Documentation of VJET is horrible - can't find changelog, bugs on eclipse vjet wiki is not up-to-date). I think we can still use 0.10.0.201309201624. Applying newer version (0.10.0.201402070708) is not necessary, but if we want to provide newer version for user, you can push it to the Central (I do not see any profit ATM). > Verify VJET/0.10.0.201402070708 with JBDS 8.0 > --------------------------------------------- > > Key: JBDS-2971 > URL: https://issues.jboss.org/browse/JBDS-2971 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Marián Labuda > Fix For: 8.0.0.Beta1 > > > See: https://issues.jboss.org/browse/JBIDE-15677 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2971) Verify VJET/0.10.0.201402070708 with JBDS 8.0

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2971?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-2971: -------------------------------- Assignee: Nick Boldt (was: Marián Labuda) > Verify VJET/0.10.0.201402070708 with JBDS 8.0 > --------------------------------------------- > > Key: JBDS-2971 > URL: https://issues.jboss.org/browse/JBDS-2971 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 8.0.0.Beta1 > > > See: https://issues.jboss.org/browse/JBIDE-15677 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2971) Verify VJET/0.10.0.201402070708 with JBDS 8.0

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2971?page=com.atlassian.jira.plugin.... ] Marián Labuda resolved JBDS-2971. --------------------------------- Resolution: Done > Verify VJET/0.10.0.201402070708 with JBDS 8.0 > --------------------------------------------- > > Key: JBDS-2971 > URL: https://issues.jboss.org/browse/JBDS-2971 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 8.0.0.Beta1 > > > See: https://issues.jboss.org/browse/JBIDE-15677 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16950?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16950: --------------------------------------------- Rob - we know all this. Go verify if code changed between the refactoring. Or point to the places in code this is happening and we can go take a look. > Very frequently, webapps are being undeployed right after being deployed > ------------------------------------------------------------------------ > > Key: JBIDE-16950 > URL: https://issues.jboss.org/browse/JBIDE-16950 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta1 > > > I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed. > See http://screencast.com/t/JmwA0TlBrDWX > The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs : > {noformat} > 14:13:45,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war") > 14:13:45,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme > 14:13:45,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war") > 14:13:50,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme > 14:13:50,730 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms > 14:13:50,999 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war") > 14:13:56,004 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy > {noformat} > Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast) -- 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, 2 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 April 2014