June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16371) Application wizard: provide checkboxes for (per application-type) applicable markers

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16371?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16371. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Application wizard: provide checkboxes for (per application-type) applicable markers > ------------------------------------------------------------------------------------ > > Key: JBIDE-16371 > URL: https://issues.jboss.org/browse/JBIDE-16371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: LATER > > Attachments: project-page.png > > > Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845 > We should offer these markers as toggles in the Application wizard on the project configuration page: > !project-page.png! > In a mail with Max and Burr: > {quote} > for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense? > {quote} > When implementing this we should consider that most markers, which are not sourcecode related, are by now considered as deprected in OpenShift. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16720. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Server Adapter: 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 > Assignee: Andre Dietisheim > Labels: server_adapter > Fix For: LATER > > > 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 was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17191) Server adapter: allow users to "Debug" OpenShift applications

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17191?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17191. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Server adapter: allow users to "Debug" OpenShift applications > ------------------------------------------------------------- > > Key: JBIDE-17191 > URL: https://issues.jboss.org/browse/JBIDE-17191 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Andre Dietisheim > Labels: server_adapter > Fix For: LATER > > Attachments: cf_eclipse_application_details_debug_start1.png, cf_eclipse_editor_connect_to_debugger.png, debug-server-adapter.png > > Original Estimate: 3 days > Remaining Estimate: 3 days > > traditional server adapters have "Debug", > !debug-server-adapter.png! > We should have this for OpenShift server adapters, too. We also need some launch config for these. > We need to be able to only port forward single ports (not just all like now) in the openshift-java-client. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14825) Application wizard: have to manually create git folder if I dont want to use the default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14825?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-14825. --------------------------------- Resolution: Done This has been done in some previous commit. > Application wizard: have to manually create git folder if I dont want to use the default > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14825 > URL: https://issues.jboss.org/browse/JBIDE-14825 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: LATER > > Attachments: non-std-git-clone-location.png > > > steps to reproduce: > # ASSERT: make sure you have an account on OpenShift > # EXEC: launch app creation wizard > # EXEC: in 3nd page uncheck *use default clone destination* and type in some folder that does not exist yet > Result: > You have to create your folder on your own, the wizard wont help you, it'll just error > !non-std-git-clone-location.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17672) Contribute changes to EGit commit/push operation so that we can nicely fit in our custom behaviour

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17672?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17672. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Contribute changes to EGit commit/push operation so that we can nicely fit in our custom behaviour > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-17672 > URL: https://issues.jboss.org/browse/JBIDE-17672 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Fix For: LATER > > > In JBIDE-10541 we made the EGit commit dialog come up before we publish the project to OpenShift. We did that by providing a modified copy of the EGit CommitUI class. We should contribute the changes that we did to CommitUI so that we can get rid of our copy. > When doing this we should also include streaming git responses to the Eclipse console as in Eclipse bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=418653 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

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 Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-14818. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > 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 > Assignee: Rob Stryker > Priority: Critical > Labels: server_adapter_editor > Fix For: LATER > > > 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 was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11268) Explorer: context menu for cartridges should have "web browser" option if URL is available for cartridge

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11268?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-11268. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Explorer: context menu for cartridges should have "web browser" option if URL is available for cartridge > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-11268 > URL: https://issues.jboss.org/browse/JBIDE-11268 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta2 > Reporter: Max Rydahl Andersen > Labels: explorer > Fix For: LATER > > Attachments: cron.png, JBIDE-11268.patch, jenkins.png, metrics.png > > > i.e. jenkins and mysql have an URL property we could show. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10757) Application wizard: Provide a "Review Changes" dialog window when importing an application into an existing project

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10757?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-10757. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Application wizard: Provide a "Review Changes" dialog window when importing an application into an existing project > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10757 > URL: https://issues.jboss.org/browse/JBIDE-10757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Xavier Coulon > Labels: application_wizard > Fix For: LATER > > Attachments: Screen Shot 2012-01-31 at 11.34.47 AM.png > > > When the user wants to import an OpenShift application into an existing project, a set of changes will have to be performed. > We could provide the user with a "Review changes" dialog so that he can assert that the changes that will be performed are correct and won't erase/break his previous files (or configuration). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-11408. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Upstream: 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: LATER > > > 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 was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17973) Application wizard, embed wizard: Obscure database password

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17973. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Application wizard, embed wizard: Obscure database password > ----------------------------------------------------------- > > Key: JBIDE-17973 > URL: https://issues.jboss.org/browse/JBIDE-17973 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Priority: Minor > Labels: application_wizard, embed_wizard, uxtest > Fix For: LATER > > > When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured. > It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment. > Reproduce steps: > 1. Open new OpenShift Application wizard > 2. Sign in & proceed to next screen > 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen > 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen > 5. Click next on set up project screen > 6. Click finish on next screen > 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5... > Expected: Password on this pop-up should be obscured. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 2015