September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12655) OpenShift Wizard should warn if there are no ssh public keys in the OpenShift account

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12655: ---------------------------------------- Summary: OpenShift Wizard should warn if there are no ssh public keys in the OpenShift account Key: JBIDE-12655 URL: https://issues.jboss.org/browse/JBIDE-12655 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.0.0.Alpha2 Attachments: cloning-settings.png, Screen Shot 2012-05-25 at 10.57.18 AM.png If the end-user's .ssh directory is empty - we should provide a stronger warning for them - ideally provide a URL to some documentation/video explaining how the user can use Eclipse/JBoss Tools to create their private/public keys - so they can then upload the .pub to OpenShift. At least 10 users failed this test today and had to be "handheld" through the process. What is worse, if the end-user uploads a slightly butchered pub key - the create application phase still works but the git clone fails - with a relatively poor error message - recovery normally means having to go up to the OpenShift console, deleting the poorly created apps - getting the pub key uploaded correctly (deleting the previous one) and starting again. The fact that Eclipse could create the keys was actually unknown by the instructor's of today's class. SSH is still a nightmare for the newbie trying to use OpenShift + JBDS. How to reproduce: 1. ASSERT: make sure you have an OpenShift user without a domain (create a new user or kill your users domain) 2. EXEC: launch *OpenShift Application* wizard and create a new application Result: Cloning fails, since there are no ssh-keys on the local machine and no keys were added to OpenShift. The wizard did not tell the user since the domain already existed. The domain creation dialog is currently the only place that would allow a user to create a new ssh-key. If you already have a domain, you'll never get asked to create your keys. -- 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

13 years, 6 months

3
11
0 / 0

[JBoss JIRA] (JBIDE-12731) OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12731: ---------------------------------------- Summary: OpenShift Explorer: user used in application wizard launched from central should make it to the users in the explorer Key: JBIDE-12731 URL: https://issues.jboss.org/browse/JBIDE-12731 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.0.0.Alpha2 Reporter: Andre Dietisheim Assignee: Xavier Coulon Fix For: 4.0.x How to reproduce: # ASSERT: make sure you have an openshift user account that is not listed in the OpenShift Explorer # EXEC: open up the OpenShift Explorer # EXEC: in central, hit *OpenShift Application* # EXEC: in the upcoming authentication dialog, provide your user (that is not listed in the explorer) and hit *Next* Result: # ASSERT: the user is not listed in the OpenShift explorer even though it was used and valid. I think we should add this new user to the OpenShift explorer since it was used and proven to be valid. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12298) Missing Requirement installing JBoss Extension

by Pete Miller (JIRA)

Pete Miller created JBIDE-12298: ----------------------------------- Summary: Missing Requirement installing JBoss Extension Key: JBIDE-12298 URL: https://issues.jboss.org/browse/JBIDE-12298 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.2.0.Final Environment: Juno Java with J2EE added, under 64-bit JDK 1.7.0 Reporter: Pete Miller Assignee: Rob Stryker Get the following after trying to install new JBossAS Tools Extenion under Servers: http://download.eclipse.org/webtools/downloads/drops/R3.4.0/I-3.4.0-20120... Cannot complete the install because one or more required items could not be found. Software being installed: JBossAS Tools 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.feature.feature.group 2.3.0.v20120504-0300-H103-Beta3) Missing requirement: JBoss AS Core Plug-in 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.core 2.3.0.v20120504-0300-H103-Beta3) requires 'bundle org.eclipse.pde.core 3.7.0' but it could not be found Cannot satisfy dependency: From: JBossAS Tools Server / Compression Integration 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.archives.integration.feature.feature.group 2.3.0.v20120504-0300-H103-Beta3) To: org.jboss.ide.eclipse.as.core 0.0.0 Cannot satisfy dependency: From: JBossAS Tools 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.feature.feature.group 2.3.0.v20120504-0300-H103-Beta3) To: org.jboss.ide.eclipse.as.archives.integration.feature.feature.group [2.3.0.v20120504-0300-H103-Beta3] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-12049) Disable program arguments change in launch config unless you uncheck Always update arguments

by Martin Malina (JIRA)

Martin Malina created JBIDE-12049: ------------------------------------- Summary: Disable program arguments change in launch config unless you uncheck Always update arguments Key: JBIDE-12049 URL: https://issues.jboss.org/browse/JBIDE-12049 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.1 Similarly to how the launch configuration works for remote servers, the Program arguments for a local server should be greyed and disabled unless you uncheck "Always update arguments...". Currently, if the checkbox is checked, the changes you make in the text field are not reflected anyway - the arguments are calculated at each launch of the server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
10
0 / 0

[JBoss JIRA] (JBIDE-12583) Unify two download-runtime models in o.j.t.runtime.as.handler plugin

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12583: ----------------------------------- Summary: Unify two download-runtime models in o.j.t.runtime.as.handler plugin Key: JBIDE-12583 URL: https://issues.jboss.org/browse/JBIDE-12583 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers, runtime detection Affects Versions: 4.0.0.Alpha2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.0.x ASTools has an integration plugin for astools vs runtime. With runtime now living at the bottom of the stack, this plugin may no longer be useful. The runtime wizard dialog cannot load any runtime.ui dialogs because there is no dependency between as.ui and runtime.ui. To add a dependency here would basically make o.j.t.runtime.as.handler to be useless. All the code there could easily be pushed into astools' other plugins. This isn't a huge priority, but it is a little silly to have two models doing exactly the same thing. -- 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

13 years, 6 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6116) Would be very nice if JBoss Tools would download and install JBoss AS into a local directory so that manual configuration can be avoided.

by Lincoln Baxter III (JIRA)

Would be very nice if JBoss Tools would download and install JBoss AS into a local directory so that manual configuration can be avoided. ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6116 URL: https://jira.jboss.org/jira/browse/JBIDE-6116 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.0.GA Reporter: Lincoln Baxter III When using the GlassFish eclipse plug-in, if the Server Runtime is not currently installed or configured, the plug-in will give you a chance to configure the Runtime, or click a button/link to have the plugin go out to the internet, download, and configure the application server for you. I think it would be great for new users/usability if JBoss Tools could provide a similar convenience. The latest plugin-compatible version of the AS should probably be the target of the download. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

6
19
0 / 0

[JBoss JIRA] (JBIDE-12101) per-module temp deploy folder is not respected

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12101: ----------------------------------- Summary: per-module temp deploy folder is not respected Key: JBIDE-12101 URL: https://issues.jboss.org/browse/JBIDE-12101 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.CR1 Step 1) Create a jboss server step 2) create a dynamic web project step 3) open server editor for server from 1) step 4) set server to view all modules step 5) modify the deploy and the temp deploy folders step 6) save editor step 7) add web project to server, initiate full publish step 8) verify whether or not the file copy went to the right temp folder (FAIL) Details that will be helpful to actually catching the bug are: 1) you will want your server to use server based deployment (middle radio) 2) You will want to customize the per-module deploy folder to be on a different file system 3) You will want the per-module temp folder to be on the same fs as the per-module deploy folder The file-copy mechanism initially copies to the tempDeployFolder, then does a renameTo the final destination. The renameTo fails if the source and destination are on different Filesystems. To force the bug, you will want to ensure the default deploy / temp deploy (in the disabled text boxes) is different from the ones you type in the server editor / column viewer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
8
0 / 0

[JBoss JIRA] (JBDS-2265) Theming error messages in Error log after JBDS startup

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBDS-2265: ------------------------------------ Summary: Theming error messages in Error log after JBDS startup Key: JBDS-2265 URL: https://issues.jboss.org/browse/JBDS-2265 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: ui/branding Affects Versions: 6.0.0.Alpha1 Reporter: Stefan Bunciak Fix For: 6.0.0.Alpha2 {code} Failed to get bundle for: bundleclass://net.jeeeyul.eclipse.themes/net.jeeeyul.eclipse.themes.rendering.ChromeTabRendering {code} -- 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

13 years, 6 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12279) Test fails because of timeout

by Mickael Istria (JIRA)

13 years, 6 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-11139) No problem popup appears when an error occurs while editing domain name

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-11139: ------------------------------------- Summary: No problem popup appears when an error occurs while editing domain name Key: JBIDE-11139 URL: https://issues.jboss.org/browse/JBIDE-11139 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Xavier Coulon Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 If an error occurs (ie, new domain name already exists), then the wizard closes, and an error popup appears but immediatly disappear.. The message is displayed in the error log, though.. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
7
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 September 2012