April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16139) Server Adapter: state after import is wrong if I dont publish

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16139?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16139: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Server Adapter: state after import is wrong if I dont publish > ------------------------------------------------------------- > > Key: JBIDE-16139 > URL: https://issues.jboss.org/browse/JBIDE-16139 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: server_adapter > Fix For: 4.2.x > > Attachments: erroneously-synchronized-adapter.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14818: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Priority: Critical > Labels: server_adapter_editor > Fix For: 4.2.x > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15978) Properties view: URL for embedded cartridges is empty

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15978?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15978: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Properties view: URL for embedded cartridges is empty > ----------------------------------------------------- > > Key: JBIDE-15978 > URL: https://issues.jboss.org/browse/JBIDE-15978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: empty-url-property.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13730) Server Adapter: state [Republish] although Repository is uptodate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13730?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13730: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Server Adapter: state [Republish] although Repository is uptodate > ----------------------------------------------------------------- > > Key: JBIDE-13730 > URL: https://issues.jboss.org/browse/JBIDE-13730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Labels: server_adapter > Fix For: 4.2.x > > Attachments: republishsync.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16720) Allow easier access to openshift operations from jboss servers

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16720: ---------------------------------------- Sprint: Sprint Beta2 CF > Allow easier access to openshift operations from jboss servers > -------------------------------------------------------------- > > Key: JBIDE-16720 > URL: https://issues.jboss.org/browse/JBIDE-16720 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.1.1.Final > Reporter: Mark Drilling > Fix For: 4.2.x > > > We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case. > Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push. > Currently, we connect to an OpenShift DV instance like this: > 1) Deploy DV cartridge via OpenShift web console. > 2) Port forward from command line using rhc port-forward > 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective > The issues we observed: > 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo. > 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list. > Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.) -- 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

1
0
0 / 0

[JBoss JIRA] (JBDS-2838) OpenShift Usability

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2838?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2838: -------------------------------------- Sprint: (was: Sprint Beta2 CF) > OpenShift Usability > ------------------- > > Key: JBDS-2838 > URL: https://issues.jboss.org/browse/JBDS-2838 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Andre Dietisheim > Priority: Blocker > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.GA > > > This task is to explore the overall usability of the OpenShift Wizard, OpenShift Explorer, the adapter in the Servers Tab and review things like Run As on OpenShift (JBIDE-16069) -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11408: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER) > ----------------------------------------------------------------------- > > Key: JBIDE-11408 > URL: https://issues.jboss.org/browse/JBIDE-11408 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, upstream > Environment: windows 7 > Reporter: Nam Duong > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.x > > > similar to https://issues.jboss.org/browse/JBIDE-10061 > When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error: > git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/ > Cloning into 'kitchensink'... > The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established. > RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open. > It is required that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: /home/spousty/.ssh/id_rsa > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > fatal: The remote end hung up unexpectedly -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-11427) Application wizard: Importing maven application requires user to update project configuration (WATCHER)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11427?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11427: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Application wizard: Importing maven application requires user to update project configuration (WATCHER) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-11427 > URL: https://issues.jboss.org/browse/JBIDE-11427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, openshift > Affects Versions: 3.3.0.Beta2 > Environment: Mac OSX Lion - 32bit Eclipse with Tools 3.3.0.Beta2b > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Critical > Labels: application_wizard > Fix For: 4.1.x, 4.2.x > > > When selecting "Import Application" on a openshift deployed application (not in the current workspace) requires the end-user to update his project configuration (Maven->Update Project Configuration) -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13096) SSH key wizard: Add Existing SSH key: automatically provide sensible default-name

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13096?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13096: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > SSH key wizard: Add Existing SSH key: automatically provide sensible default-name > --------------------------------------------------------------------------------- > > Key: JBIDE-13096 > URL: https://issues.jboss.org/browse/JBIDE-13096 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: sshkeys_wizard > Fix For: 4.2.x > > > When adding an existing ssh key the user is required to provide a name for the key he's adding (uploading). To the newbie user it is not obvious what he shall provide as name. We should help here a provide some sensible default name. > How to reproduce: > # ASSERT: make sure you have an account on OpenShift and in the OpenShift Explorer > # EXEC: in the OpenShift Explorer: pick "Manage SSH Keys..." from the context-menu of your user > # EXEC: in the upcoming dialog: hit "Add" > Result: > You get a dialog that asks you to browse and select your key and provide a name for it. > Expected: > Automatically provide some meaningful default name so that the newbie user may just pick his key and upload. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13106) Tail files: Change icon and tooltip for "close console" to better show difference to closing view

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13106?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13106: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Tail files: Change icon and tooltip for "close console" to better show difference to closing view > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-13106 > URL: https://issues.jboss.org/browse/JBIDE-13106 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: different-close-actions.png > > > The Server Log console has 2 distinct actions that are labeled "close console". > !different-close-actions.png! > 1) the close button to the console view, that closes the view. The view would get hidden and would reappear if you choose "tail files..." on the very same OpenShift applcation > 2) the close button in the view toolbar which actually kills the logging process. If you then pick "tail files.." on the application again, the view would show up again and ask you for the pattern. > We should choose a different icon and tooltip for 2) so that it gets more obvious to users that the 2 are about two different things. -- 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

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