December 2013 - jbosstools-issues

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Assignee: (was: Rob Stryker) > 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 > > 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, 3 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Estimated Difficulty: Medium > 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 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-15185 at 12/20/13 9:20 AM: --------------------------------------------------------------- > if I could enter a relative path or a path containing a variable in the "Jboss Runtime" dialog would help us. We want to save this configuration in subversion and distribute it to developers. This is 100% impossible. I will explain why. Only servers can be stored and shared. Runtimes cannot. Servers are initially stored in one file named servers.xml at the following path: ./workspace/.metadata/.plugins/org.eclipse.wst.server.core/servers.xml Servers, however, can be right-clicked and in the properties page can have the option to be stored as separate files. They would then be stored in workspace/servers/YourServername.xml. Runtimes, however, are not stored in any accessible place at all. Runtimes are stored as one property key inside the file .metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.wst.server.core.prefs There are many other unrelated keys in that file, most of which have nothing to do with a runtime definition. Runtimes cannot be right-clicked and exported or stored separately. It is 100% impossible in current UI and indeed in current API. There is no option to change where runtimes are stored at all. was (Author: rob.stryker): > if I could enter a relative path or a path containing a variable in the "Jboss Runtime" dialog would help us. We want to save this configuration in subversion and distribute it to developers. This is 100% impossible. I will explain why. Only servers can be stored and shared. Runtimes cannot. Servers are initially stored in one file named servers.xml at the following path: ./workspace/.metadata/.plugins/org.eclipse.wst.server.core/servers.xml Servers, however, can be right-clicked and in the properties page can have the option to be stored as separate files. They would then be stored in {workspace}/servers/YourServername.xml. Runtimes, however, are not stored in any accessible place at all. Runtimes are stored as one property key inside the file .metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.wst.server.core.prefs There are many other unrelated keys in that file, most of which have nothing to do with a runtime definition. Runtimes cannot be right-clicked and exported or stored separately. It is 100% impossible in current UI and indeed in current API. There is no option to change where runtimes are stored at all. > add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15185 > URL: https://issues.jboss.org/browse/JBIDE-15185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Gary Hu > Fix For: 4.2.x > > > The current jbds version only allow users to specify an absolute path for "Home Directory" when creating JBoss Runtime Server. Is it possible to use a user defined variable here? -- 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, 3 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Summary: Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module (was: there's no "deployments" page for OpenShift that would allow me to rename a module) > 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 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10988) Let the user delete apps from within the application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10988?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10988: ------------------------------------- Assignee: (was: Xavier Coulon) > Let the user delete apps from within the application wizard > ----------------------------------------------------------- > > Key: JBIDE-10988 > URL: https://issues.jboss.org/browse/JBIDE-10988 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Priority: Minor > Labels: new_and_noteworthy > Fix For: LATER > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10988) Let the user delete apps from within the application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10988?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10988: ------------------------------------- Estimated Difficulty: Low > Let the user delete apps from within the application wizard > ----------------------------------------------------------- > > Key: JBIDE-10988 > URL: https://issues.jboss.org/browse/JBIDE-10988 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Priority: Minor > Labels: new_and_noteworthy > Fix For: LATER > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10853) Application wizard: Embed wizard: jenkins cartridge asks for name - why not use default "jenkins" if available (and jenkins-2 if not...?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10853?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10853: ------------------------------------- Assignee: (was: Andre Dietisheim) > Application wizard: Embed wizard: jenkins cartridge asks for name - why not use default "jenkins" if available (and jenkins-2 if not...?) > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10853 > URL: https://issues.jboss.org/browse/JBIDE-10853 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: application_wizard, embed_wizard, new_and_noteworthy > Fix For: LATER > > > If you embed the jenkins client you're prompted to create a jenkins appliaction (if there's none yet) and asked to provide some name for this new application. We should - instead of prompting - use a fixed name: jenkins, jenkins-2, jenkins-3 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10853) Application wizard: Embed wizard: jenkins cartridge asks for name - why not use default "jenkins" if available (and jenkins-2 if not...?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10853?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10853: ------------------------------------- Estimated Difficulty: Low > Application wizard: Embed wizard: jenkins cartridge asks for name - why not use default "jenkins" if available (and jenkins-2 if not...?) > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10853 > URL: https://issues.jboss.org/browse/JBIDE-10853 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: application_wizard, embed_wizard, new_and_noteworthy > Fix For: LATER > > > If you embed the jenkins client you're prompted to create a jenkins appliaction (if there's none yet) and asked to provide some name for this new application. We should - instead of prompting - use a fixed name: jenkins, jenkins-2, jenkins-3 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10788) Server Adapter: Add setting ui for openshift source servers to use wtp context root if required

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10788?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10788: ------------------------------------- Estimated Difficulty: Medium > Server Adapter: Add setting ui for openshift source servers to use wtp context root if required > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-10788 > URL: https://issues.jboss.org/browse/JBIDE-10788 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 3.3.0.M5 > Reporter: Rob Stryker > Priority: Minor > Labels: server_adapter > Fix For: LATER > > > link to JBIDE-10514 , a UI is required for this setting. > 1. Create a new application in wizard and allow to create a new project in the workspace > 2. Fix all the bugs so that it compiles (delete modules.jsp, add java version 1.6 to pom.xml, reload project configuration) > 3. Modify all your build stuff so the project does NOT deploy to root > 4. Change your context root to match what your setting is in the build > 5. Right click the project and select Run as... + Run on server > 6. Choose associated openshift server > 7. Result - No page found due to the incorrect URL. It's still using root instead of your new custom context root > A UI is required for this setting -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10747) ApplicationDetailsDialog: link background is not using the selection background color, it stays white

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10747?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10747: ------------------------------------- Estimated Difficulty: Medium > ApplicationDetailsDialog: link background is not using the selection background color, it stays white > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-10747 > URL: https://issues.jboss.org/browse/JBIDE-10747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: wrong-background-color.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, 3 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 December 2013