[JBoss JIRA] (JBIDE-10633) No changed items were selected. Do you wish to amend the last commit?
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10633?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-10633.
--------------------------------------
Resolution: Out of Date
We don't offer the "Commit and Push" action any more.
> No changed items were selected. Do you wish to amend the last commit?
> ---------------------------------------------------------------------
>
> Key: JBIDE-10633
> URL: https://issues.jboss.org/browse/JBIDE-10633
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.M5
> Environment: Mac OS X Lion
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Fix For: 4.0.x
>
> Attachments: Screen Shot 2012-01-13 at 1.37.47 PM.png
>
>
> This message is problematic. It says that nothing changed, when in fact, everything changed - the project's contents are 100% different from what they were.
> See video for complete workflow -
> http://vimeo.com/35023638
> 1) New HTML5 Project called "test40"
> 2) New OpenShift Express project called "test40"
> 3) Copy existing project
> 4) Team-Commit and Push
--
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
[JBoss JIRA] (JBIDE-10612) OpenShift Server adapter: is not updated when application info is renamed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10612?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10612:
-------------------------------------
Steps to Reproduce:
# ASSERT: You have imported/created an OpenShift application to your workspace
# EXEC: Open the OpenShift wizard, log in, and rename your domain
Result:
1. Run As - Run on Server doesn't work (trying to reach url with the old domain)
!runas.png|thumbnail!
2. OpenShift server adapter has the old domain associated, so even publish doesn't work
!runtime.png|thumbnail!
3. OpenShift functions like tailing files doesn't work.
{code}
Failed to tail files for application 'scaledjboss'
0e4bb0996744463d98dee75df05bdac1(a)scaledjboss-rhdomain.rhcloud.com: unknown host
{code}
But the domain was renamed correctly:
!running.png|thumbnail!
was:
#ASSERT: You have imported/created an OpenShift application to your workspace
#EXEC: Open the OpenShift wizard, log in, and rename your domain
Result:
1. Run As - Run on Server doesn't work (trying to reach url with the old domain)
!runas.png|thumbnail!
2. OpenShift server adapter has the old domain associated, so even publish doesn't work
!runtime.png|thumbnail!
3. OpenShift functions like tailing files doesn't work.
{code}
Failed to tail files for application 'scaledjboss'
0e4bb0996744463d98dee75df05bdac1(a)scaledjboss-rhdomain.rhcloud.com: unknown host
{code}
But the domain was renamed correctly:
!running.png|thumbnail!
> OpenShift Server adapter: is not updated when application info is renamed
> -------------------------------------------------------------------------
>
> Key: JBIDE-10612
> URL: https://issues.jboss.org/browse/JBIDE-10612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Stefan Bunciak
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.0.x
>
> Attachments: runas.png, running.png, runtime.png
>
>
> OpenShift wizard will rename domain on the server and in OpenShift Explorer but not in the server adapter.
--
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
[JBoss JIRA] (JBIDE-10717) Retrieve/display the information about the embeddable cartridges
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10717?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10717:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.0.x)
> Retrieve/display the information about the embeddable cartridges
> ----------------------------------------------------------------
>
> Key: JBIDE-10717
> URL: https://issues.jboss.org/browse/JBIDE-10717
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
>
> See how we can retrieve the information about the embeddable cartridges that were associated with a created application.
> For example, we should provide the user with the URL and credentials of the MySQL cartridge.
> The question is:
> - can we provide this information at the end of the creation process,
> - or should we give access to this information after, from the 'Express Console' view ? (this would be handful, but probably require work at the java client level, too)
--
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
[JBoss JIRA] (JBIDE-10818) OpenShift Express Console: different jobs have to block each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10818:
-------------------------------------
Priority: Minor (was: Major)
> OpenShift Express Console: different jobs have to block each other
> -------------------------------------------------------------------
>
> Key: JBIDE-10818
> URL: https://issues.jboss.org/browse/JBIDE-10818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.1.x
>
>
> The *OpenShift Express Console* allows you to delete applications, create new applications and will allow you to refresh the view. Those operations are executed in background jobs so that the Eclipse UI is not blocked in the meantime. We therefore have to setup scheduling rules on those jobs so that a refresh will wait until the delete is finished. To me the best way to achieve this is to create cathegories of jobs (ex. ApplicationJob, UserJob, etc.) that have the appropriate scheduling rules initialized (ex. ApplicationJobs operate on applications and therefore have to block UserJob that possibly operate on all applications.)
--
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