[JBoss JIRA] (JBIDE-12803) Publishing to ... OpenShift Server - after project rename
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12803?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12803:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.0.x)
> Publishing to ... OpenShift Server - after project rename
> ---------------------------------------------------------
>
> Key: JBIDE-12803
> URL: https://issues.jboss.org/browse/JBIDE-12803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: 2012-10-04_1859.png
>
>
> Using JBDS, I used
> Refactor - Rename Maven Artifact
> and
> Refactor - Rename
> to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
> The workaround is to double-click on the Openshift server adapter (Servers Tab) and reset which project it is tied to.
--
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-12803) Publishing to ... OpenShift Server - after project rename
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12803?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-12803 at 1/10/13 8:34 AM:
-------------------------------------------------------------------
setting to Minor and 4.1.x since this is an edge case (happens when you rename a project) which an easy workaround (open server editor and set the project again) exists.
was (Author: adietish):
setting to Minor and 4.1.x since this is an edge case (happens when you rename a project)
> Publishing to ... OpenShift Server - after project rename
> ---------------------------------------------------------
>
> Key: JBIDE-12803
> URL: https://issues.jboss.org/browse/JBIDE-12803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: 2012-10-04_1859.png
>
>
> Using JBDS, I used
> Refactor - Rename Maven Artifact
> and
> Refactor - Rename
> to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
> The workaround is to double-click on the Openshift server adapter (Servers Tab) and reset which project it is tied to.
--
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-12803) Publishing to ... OpenShift Server - after project rename
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12803?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-12803:
------------------------------------------
setting to Minor and 4.1.x since this is an edge case (happens when you rename a project)
> Publishing to ... OpenShift Server - after project rename
> ---------------------------------------------------------
>
> Key: JBIDE-12803
> URL: https://issues.jboss.org/browse/JBIDE-12803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: 2012-10-04_1859.png
>
>
> Using JBDS, I used
> Refactor - Rename Maven Artifact
> and
> Refactor - Rename
> to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
> The workaround is to double-click on the Openshift server adapter (Servers Tab) and reset which project it is tied to.
--
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-12803) Publishing to ... OpenShift Server - after project rename
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12803?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12803:
-------------------------------------
Priority: Minor (was: Major)
> Publishing to ... OpenShift Server - after project rename
> ---------------------------------------------------------
>
> Key: JBIDE-12803
> URL: https://issues.jboss.org/browse/JBIDE-12803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.0.x
>
> Attachments: 2012-10-04_1859.png
>
>
> Using JBDS, I used
> Refactor - Rename Maven Artifact
> and
> Refactor - Rename
> to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
> The workaround is to double-click on the Openshift server adapter (Servers Tab) and reset which project it is tied to.
--
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-12802) The are no local changes in
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12802?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-12802.
--------------------------------------
Resolution: Duplicate Issue
> The are no local changes in
> ---------------------------
>
> Key: JBIDE-12802
> URL: https://issues.jboss.org/browse/JBIDE-12802
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Alpha2
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha1
>
> Attachments: 2012-10-04_1808.png
>
>
> First, this message is poorly written with "the are no changes".
> Second, it is inaccurate, I have added a file to my project and I have used Team -> Commit on it so it no longer has a question mark on the file. In other words, I have changed something but this message almost always says "hey nothing has changed".
> How to reproduce:
> # ASSERT: make sure you have a project in your workspace, that you imported from OpenShift. You should have a server adapter for your project
> # EXEC: create a new file in it and add it Team->Commit->Check your file
> # EXEC: Go to your server adapter and publish
> Result:
> The adapter warns you that there are no changes and asks you if you still want to publish your project
> Expected result:
> The adapter states that there's 1 change.
--
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