[JBoss JIRA] (JBIDE-11419) Openshift event model
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11419?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11419:
-------------------------------------
Assignee: (was: Xavier Coulon)
> Openshift event model
> ---------------------
>
> Key: JBIDE-11419
> URL: https://issues.jboss.org/browse/JBIDE-11419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Rob Stryker
> Priority: Minor
> Fix For: LATER
>
>
> An event model is needed so that interested listeners can know when applications are created / deleted, domains are changed, etc. This event model must be robust enough to survive workspace restarts in some fashion (not necessarily persissted...) It must provide listeners an opportunity to subscribe in some fashion without forcing a long-running remote load of the model.
--
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
[JBoss JIRA] (JBIDE-11419) Openshift event model
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11419?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11419:
-------------------------------------
Estimated Difficulty: High
> Openshift event model
> ---------------------
>
> Key: JBIDE-11419
> URL: https://issues.jboss.org/browse/JBIDE-11419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Rob Stryker
> Priority: Minor
> Fix For: LATER
>
>
> An event model is needed so that interested listeners can know when applications are created / deleted, domains are changed, etc. This event model must be robust enough to survive workspace restarts in some fashion (not necessarily persissted...) It must provide listeners an opportunity to subscribe in some fashion without forcing a long-running remote load of the model.
--
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
[JBoss JIRA] (JBIDE-11367) Application wizard: run jobs outside of Wizards instead of within container
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11367:
-------------------------------------
Assignee: (was: Andre Dietisheim)
> Application wizard: run jobs outside of Wizards instead of within container
> ---------------------------------------------------------------------------
>
> Key: JBIDE-11367
> URL: https://issues.jboss.org/browse/JBIDE-11367
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Xavier Coulon
> Labels: application_wizard
> Fix For: LATER
>
>
> After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen.
> We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished.
--
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
[JBoss JIRA] (JBIDE-11367) Application wizard: run jobs outside of Wizards instead of within container
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11367:
-------------------------------------
Estimated Difficulty: High
> Application wizard: run jobs outside of Wizards instead of within container
> ---------------------------------------------------------------------------
>
> Key: JBIDE-11367
> URL: https://issues.jboss.org/browse/JBIDE-11367
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Xavier Coulon
> Labels: application_wizard
> Fix For: LATER
>
>
> After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen.
> We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished.
--
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
[JBoss JIRA] (JBIDE-11367) Application wizard: run jobs outside of Wizards instead of within container
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11367:
-------------------------------------
Summary: Application wizard: run jobs outside of Wizards instead of within container (was: Run jobs outside of Wizards instead of within container (wizard lApplication wizard: aunches background jobs and closes))
> Application wizard: run jobs outside of Wizards instead of within container
> ---------------------------------------------------------------------------
>
> Key: JBIDE-11367
> URL: https://issues.jboss.org/browse/JBIDE-11367
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: LATER
>
>
> After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen.
> We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished.
--
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
[JBoss JIRA] (JBIDE-11367) Application wizard: run jobs outside of Wizards instead of within container
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11367:
-------------------------------------
Labels: application_wizard (was: )
> Application wizard: run jobs outside of Wizards instead of within container
> ---------------------------------------------------------------------------
>
> Key: JBIDE-11367
> URL: https://issues.jboss.org/browse/JBIDE-11367
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: LATER
>
>
> After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen.
> We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished.
--
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
[JBoss JIRA] (JBIDE-11367) Run jobs outside of Wizards instead of within container (wizard lApplication wizard: aunches background jobs and closes)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11367:
-------------------------------------
Summary: Run jobs outside of Wizards instead of within container (wizard lApplication wizard: aunches background jobs and closes) (was: Run jobs outside of Wizards instead of within container (wizard launches background jobs and closes))
> Run jobs outside of Wizards instead of within container (wizard lApplication wizard: aunches background jobs and closes)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11367
> URL: https://issues.jboss.org/browse/JBIDE-11367
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: LATER
>
>
> After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen.
> We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished.
--
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
[JBoss JIRA] (JBIDE-10757) Application wizard: Provide a "Review Changes" dialog window when importing an application into an existing project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10757?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10757:
-------------------------------------
Summary: Application wizard: Provide a "Review Changes" dialog window when importing an application into an existing project (was: Provide a "Review Changes" dialog window when importing an Application wizard: OpenShift application into an existing project)
> 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 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
[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:
-------------------------------------
Labels: server_adapter_editor (was: )
> 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
>
> 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
[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 commented on JBIDE-15185:
-------------------------------------
> 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