[JBoss JIRA] (JBIDE-13106) Tail files: Change icon and tooltip for "close console" to better show difference to closing view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13106?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13106:
-------------------------------------
Assignee: (was: Xavier Coulon)
Estimated Difficulty: Low
> Tail files: Change icon and tooltip for "close console" to better show difference to closing view
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13106
> URL: https://issues.jboss.org/browse/JBIDE-13106
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta1
> Reporter: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: different-close-actions.png
>
>
> The Server Log console has 2 distinct actions that are labeled "close console".
> !different-close-actions.png!
> 1) the close button to the console view, that closes the view. The view would get hidden and would reappear if you choose "tail files..." on the very same OpenShift applcation
> 2) the close button in the view toolbar which actually kills the logging process. If you then pick "tail files.." on the application again, the view would show up again and ask you for the pattern.
> We should choose a different icon and tooltip for 2) so that it gets more obvious to users that the 2 are about two different things.
--
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-2844) Management API Server Adapter
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
Burr Sutter updated JBDS-2844:
------------------------------
Target Release: 8.0.0.GA
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
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-2844) Management API Server Adapter
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2844:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
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-2851) Team Usability
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Burr Sutter updated JBDS-2851:
------------------------------
Target Release: 8.0.0.GA
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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-2851) Team Usability
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2851:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
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-10650) EGitUtils is too large, needs to be split into smaller parts
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10650?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10650:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> EGitUtils is too large, needs to be split into smaller parts
> ------------------------------------------------------------
>
> Key: JBIDE-10650
> URL: https://issues.jboss.org/browse/JBIDE-10650
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: LATER
>
>
> EGitUtils is a collection of handy utilities to simplify tasks when dealing with EGit/JGit in OpenShift. It holds all its functionality in static methods. The class grew up to > 800 lines in its current incarnation. This is by far too large to be maintained effectively. We need to split it up into smaller parts (into commands? into several util classes?)
--
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