[JBoss JIRA] (JBIDE-12080) Explorer: provide initial instruction when there are no connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12080?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12080:
-------------------------------------
Labels: explorer (was: )
> Explorer: provide initial instruction when there are no connections
> -------------------------------------------------------------------
>
> Key: JBIDE-12080
> URL: https://issues.jboss.org/browse/JBIDE-12080
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.x
>
> Attachments: openshift.png, servers.png
>
>
> OpenShift Explorer could provide basic instruction about how to create a new connection (where to click) like in Servers view:
> !servers.png|thumbnail!
> copied from duplicate JBIDE-14587:
> {quote}
> My 1st reflex is, when the view is empty, is to right-click to bring up the OpenShift Management UI. But nothing happens. I need to remember I need to click on the top right button to log-in (which doesn't stand out much on the window background).
> So. I'd welcome a "Connect to OpenShift" menu showing up on right-click, when OpenShift Explorer is empty. That menu doesn't need to appear if already connected.
> {quote}
--
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, 4 months
[JBoss JIRA] (JBIDE-11411) Server Adapter: Warn user when the deployments folder is changed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11411?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11411:
-------------------------------------
Summary: Server Adapter: Warn user when the deployments folder is changed (was: OpenShift server adapter: Warn user when the deployments folder is changed)
> Server Adapter: Warn user when the deployments folder is changed
> ----------------------------------------------------------------
>
> Key: JBIDE-11411
> URL: https://issues.jboss.org/browse/JBIDE-11411
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
>
> As Max comment:
> We could warn the user if the deployments folder is not deployments (or even better look for .openshift/config/standalone.xml setting if the apptype is JBoss and only validate then)
--
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, 4 months
[JBoss JIRA] (JBIDE-12080) Explorer: provide initial instruction when there are no connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12080?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12080:
-------------------------------------
Summary: Explorer: provide initial instruction when there are no connections (was: Provide initial instruction in OpenShift Explorer)
> Explorer: provide initial instruction when there are no connections
> -------------------------------------------------------------------
>
> Key: JBIDE-12080
> URL: https://issues.jboss.org/browse/JBIDE-12080
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: openshift.png, servers.png
>
>
> OpenShift Explorer could provide basic instruction about how to create a new connection (where to click) like in Servers view:
> !servers.png|thumbnail!
> copied from duplicate JBIDE-14587:
> {quote}
> My 1st reflex is, when the view is empty, is to right-click to bring up the OpenShift Management UI. But nothing happens. I need to remember I need to click on the top right button to log-in (which doesn't stand out much on the window background).
> So. I'd welcome a "Connect to OpenShift" menu showing up on right-click, when OpenShift Explorer is empty. That menu doesn't need to appear if already connected.
> {quote}
--
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, 4 months
[JBoss JIRA] (JBDS-2857) Add OS X Mavericks to the support matrix
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-2857:
--------------------------------------
Need QE confirmation. I'm pretty sure the list of OS/JDK's did not change for this release so we can't include it unless QE sign off and say they tested with this.
> Add OS X Mavericks to the support matrix
> ----------------------------------------
>
> Key: JBDS-2857
> URL: https://issues.jboss.org/browse/JBDS-2857
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Max Rydahl Andersen
>
> I know this comes very late, so you may want to just push this to 8.0.0 immediately.
> However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it.
> I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document.
--
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, 4 months
[JBoss JIRA] (JBIDE-12803) Server Adapter: Cannot publish after I renamed the maven artifact
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12803?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12803:
-------------------------------------
Summary: Server Adapter: Cannot publish after I renamed the maven artifact (was: Server Adapter: Publishing to ... OpenShift Server - after project rename)
> Server Adapter: Cannot publish after I renamed the maven artifact
> -----------------------------------------------------------------
>
> 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
> Labels: server_adapter
> Fix For: 4.2.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
12 years, 4 months
[JBoss JIRA] (JBIDE-13922) OpenShift "Secure Storage" dialog in infinite loop of prompting
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13922?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13922:
-------------------------------------
Priority: Minor (was: Major)
> OpenShift "Secure Storage" dialog in infinite loop of prompting
> ---------------------------------------------------------------
>
> Key: JBIDE-13922
> URL: https://issues.jboss.org/browse/JBIDE-13922
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Environment: Fedora 18
> Reporter: R Searls
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
>
> Running : JBoss Developer Studio
> version:6.0.1.GA
> Build id:GA-v20130327-2052-B361
> OS: Fedora 18
> When creating a new OpenShift App in the "New OpenShift Application" dialog
> I type in my password, (I have an existing account.) and select the checkbox,
> "Save password (could trigger storage login)" and click next. The " Secure
> Storage" dialog displays. I click the cancel button. Each time I click cancel
> in this dialog, the dialog closes and pops back open. It's in an infinit loop.
> I must kill the app to get out of this cycle.
--
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, 4 months
[JBoss JIRA] (JBIDE-12803) Server Adapter: 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:
-------------------------------------
Summary: Server Adapter: Publishing to ... OpenShift Server - after project rename (was: Publishing to ... OpenShift Server - after project rename)
> Server Adapter: 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.2.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
12 years, 4 months
[JBoss JIRA] (JBIDE-12803) Server Adapter: 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:
-------------------------------------
Labels: server_adapter (was: )
> Server Adapter: 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
> Labels: server_adapter
> Fix For: 4.2.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
12 years, 4 months
[JBoss JIRA] (JBIDE-13936) Support deployment on multiple applications (eg: test vs prod)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13936?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13936:
-------------------------------------
Labels: server_adapter (was: )
> Support deployment on multiple applications (eg: test vs prod)
> ---------------------------------------------------------------
>
> Key: JBIDE-13936
> URL: https://issues.jboss.org/browse/JBIDE-13936
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: LATER
>
>
> could we support multiple platforms and have a workflow of the following kind:
> 1 - user deploys to a 'test' platform/application
> 2 - user tests/check it's all good
> 3 - if so, he can deploy on the 'production' platform/application
> This would mean, for example, having 2 server adapters and being able to support 2 'git remotes'
--
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, 4 months