[JBoss JIRA] (JBIDE-14856) OpenShift Explorer: should be able to remove several connections at once
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14856?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-14856.
--------------------------------------
Resolution: Done
> OpenShift Explorer: should be able to remove several connections at once
> ------------------------------------------------------------------------
>
> Key: JBIDE-14856
> URL: https://issues.jboss.org/browse/JBIDE-14856
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.Alpha1
>
>
> steps to reproduce:
> # ASSER: make sure you have several connections available in *OpenShift Explorer*
> # EXEC: select them all and open up the context menu
> Result:
> You cannot choose *Remove from view* for all the selected connections. You have select them one by one and remove them.
> Expected result:
> You can select all your connections and remove them all at once.
--
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, 5 months
[JBoss JIRA] (JBIDE-15161) warn users that phpmyadmin may not get embedded into a scalable application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15161?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15161:
-------------------------------------
Fix Version/s: 4.1.1.Beta1
> warn users that phpmyadmin may not get embedded into a scalable application
> ---------------------------------------------------------------------------
>
> Key: JBIDE-15161
> URL: https://issues.jboss.org/browse/JBIDE-15161
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: adding-phpmyadmin-to-scaling-2.png, adding-phpmyadmin-to-scaling-3.png, adding-phpmyadmin-to-scaling-4.png, adding-phpmyadmin-to-scaling.png, phpmyadmin-not-scalable.png
>
>
> phpmyadmin may not get embedded into a scalable application.
> # EXEC: create a scalable application on OpenShift
> # EXEC: try to embed phpmyadmin to it
> Result:
> !phpmyadmin-not-scalable.png!
> We should therefore warn the user when he tries to achieve this.
--
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, 5 months
[JBoss JIRA] (JBIDE-15319) Configure Markers: not present in Navigator context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15319?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15319:
-------------------------------------
Fix Version/s: 4.1.1.Beta1
> Configure Markers: not present in Navigator context menu
> --------------------------------------------------------
>
> Key: JBIDE-15319
> URL: https://issues.jboss.org/browse/JBIDE-15319
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: configure-markers.png
>
>
> We allow users to configure the markers for an OpenShift project via the package and project explorer context menu.
> !configure-markers.png!
> We're still missing this in the navigator. This is cumbersome since you by default only see the .openshift folder listed in the navigator. A user that wants to check for the marker-files thus has to inspect the folder in the navigator and then switch back to the package- or project-explorer.
--
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, 5 months
[JBoss JIRA] (JBIDE-15319) Configure Markers: not present in Navigator context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15319?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15319:
------------------------------------------
this was included in branch via JBIDE-15663
> Configure Markers: not present in Navigator context menu
> --------------------------------------------------------
>
> Key: JBIDE-15319
> URL: https://issues.jboss.org/browse/JBIDE-15319
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
> Attachments: configure-markers.png
>
>
> We allow users to configure the markers for an OpenShift project via the package and project explorer context menu.
> !configure-markers.png!
> We're still missing this in the navigator. This is cumbersome since you by default only see the .openshift folder listed in the navigator. A user that wants to check for the marker-files thus has to inspect the folder in the navigator and then switch back to the package- or project-explorer.
--
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, 5 months
[JBoss JIRA] (JBDS-2806) JBDS crashed after Help > Check for updates :: 7.0.0.GA (B364) -> 7.0.1.GA on OSX 10.8.5 (Mountain Lion)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2806?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2806:
----------------------------------
OK, next set of dumb questions. :D
Did the crash occur during the update? or on warm restart of JBDS?
If you do a COLD restart (shut down JBDS entirely, rather than letting it restart itself, then start it up yourself), does the crash happen again?
Can you reproduce the crash from a clean install using a clean workspace (new folder path, not an existing workspace), followed by running Help > Check for Updates ?
> JBDS crashed after Help > Check for updates :: 7.0.0.GA (B364) -> 7.0.1.GA on OSX 10.8.5 (Mountain Lion)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2806
> URL: https://issues.jboss.org/browse/JBDS-2806
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 7.0.0.GA, 7.0.1.GA
> Environment: Mac OS
> Reporter: Oleg Lovkis
> Assignee: Denis Golovin
> Priority: Critical
> Attachments: JBDS2806.crashdump.txt
>
>
> On OSX 10.8.5 (Mountain Lion) with Oracle JDK 1.7u25 x64, update from JBDS 7.0.0.GA (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) to 7.0.1.GA caused crash after performing Help -> Check For Updates
> See [^JBDS2806.crashdump.txt] for complete dump.
--
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, 5 months