[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15897 at 5/9/14 5:56 AM:
------------------------------------------------------------------
1) we reordered the explorer context menu:
!explorer-application-context-menu.png!
!explorer-application-context-menu-showin.png!
* moved "Create Server Adapter" to the "New" submenu
* added connection, domain and application to the "New" submenu
* moved "Open in Web Browser" to "Show in" submenu
* reordered the remaining items to match the default structure for Eclipse context menus
2) and also did the following to the OpenShift server adapter context menu:
!serversview-openshift-contextmenu.png!
* added all missing items (as discussed above)
was (Author: adietish):
1) we reordered the explorer context menu:
!explorer-application-context-menu.png!
!explorer-application-context-menu-showin.png!
* moved "Create Server Adapter" to the "New" submenu
* added connection, domain and application to the "New" submenu
* moved "Open in Web Browser" to "Show in" submenu
* reordered the remaining items to match the default structure for Eclipse context menus
2) and also did the following to the OpenShift server adapter context menu:
!serversview-openshift-context-menu.png!
* added all missing items (as discussed above)
> Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-application-context-menu-showin.png, explorer-application-context-menu.png, explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png, serversview-openshift-contextmenu.png
>
> Original Estimate: 1 day
> Time Spent: 4 days, 4 hours
> Remaining Estimate: 0 minutes
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15897:
-------------------------------------
Attachment: explorer-application-context-menu.png
> Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-application-context-menu-showin.png, explorer-application-context-menu.png, explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png, serversview-openshift-contextmenu.png
>
> Original Estimate: 1 day
> Time Spent: 4 days, 4 hours
> Remaining Estimate: 0 minutes
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15897:
-------------------------------------
Attachment: serversview-openshift-contextmenu.png
> Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-application-context-menu-showin.png, explorer-application-context-menu.png, explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png, serversview-openshift-contextmenu.png
>
> Original Estimate: 1 day
> Time Spent: 4 days, 4 hours
> Remaining Estimate: 0 minutes
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15897:
-------------------------------------
Attachment: (was: explorer-application-context-menu.png)
> Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-application-context-menu-showin.png, explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png
>
> Original Estimate: 1 day
> Time Spent: 3 days
> Remaining Estimate: 0 minutes
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15897 at 5/9/14 5:50 AM:
------------------------------------------------------------------
1) we reordered the explorer context menu:
!explorer-application-context-menu.png!
!explorer-application-context-menu-showin.png!
* moved "Create Server Adapter" to the "New" submenu
* added connection, domain and application to the "New" submenu
* moved "Open in Web Browser" to "Show in" submenu
* reordered the remaining items to match the default structure for Eclipse context menus
2) and also did the following to the OpenShift server adapter context menu:
!serversview-openshift-context-menu.png!
* added all missing items (as discussed above)
was (Author: adietish):
we reordered the explorer context menu:
!explorer-application-context-menu.png!
!explorer-application-context-menu-showin.png!
* moved "Create Server Adapter" to the "New" submenu
* added connection, domain and application to the "New" submenu
* moved "Open in Web Browser" to "Show in" submenu
* reordered the remaining items to match the default structure for Eclipse context menus
> Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-application-context-menu-showin.png, explorer-application-context-menu.png, explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png
>
> Original Estimate: 1 day
> Time Spent: 3 days
> Remaining Estimate: 0 minutes
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17151) Improve the "New Restful Web Service" wizard
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17151?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-17151:
---------------------------------------
[~maxandersen],
not sure I grok what you mean: the Application class should be created only once per webapp, so basically, when creating the first JAX-RS resource. We could have a radio button to:
- create a subclass of JAX-RS Application
- configure a servler mapping in web.xml
- do not create an Application (and let the user manage herself that part if it is not a portable solution. Eg: deploying with RESTEasy on Tomcat)
[~ArunGupta],
Yes, I would only override the base URL in web.xml, something like:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
version="3.0">
<servlet-mapping>
<servlet-name>javax.ws.rs.core.Application</servlet-name>
<url-pattern>/rest/*</url-pattern>
</servlet-mapping>
</web-app>
{code}
(the servlet version should match the project settings)
I do not plan to provide implementation-specific servlet mappings in the wizard (yet). This could be a later improvement (if relevant)
> Improve the "New Restful Web Service" wizard
> --------------------------------------------
>
> Key: JBIDE-17151
> URL: https://issues.jboss.org/browse/JBIDE-17151
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.2.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta2
>
> Attachments: current wizard.png, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.bmml, Mockup for new JAX-RS Wizard.png
>
>
> The current wizard could be improved after feedback on JBIDE-13309, JBIDE-13310 and internal discussion:
> {quote}
> - Choosing the first wizard shows an option to edit "Web Service" and "Application Class Name" and have the same values. Why this value need to be entered twice and how is it used ?
> - web.xml is generated even though "Update web.xml" was not selected. Why can't ApplicationPath be used instead of web.xml anyway ?
> - Even in the generated web.xml, the mapped path is {{/*}}. This is not the recommended practice as none of the Servlets or other resources in the application would then be resolved correctly. The recommendation is to use something like {{/webresources}}, {{/resources}}, or {{/rest}} and have all the resources be accessed from there.
> - The generation of REST resource did not added JAX-RS facet to my project. Does it have to be manually added ? If yes, then why ?
> - Adding JAX-RS facet shows "Further configuration required" and require me to specify "JAX-RS Servlet class name". How is the user expected to know the class name ? This should not even be required for a Java EE 6 application.
> - In pure Java EE 6, there should be no need to ask that information anyway. Instead use {{@ApplicationPath}} to specify the base path of JAX-RS.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt commented on TOOLSDOC-492:
-------------------------------------
== Docbook to Asciidoc conversion script, docbookrx.rb
https://github.com/nickboldt/docbookrx/blob/tweaks-hacks-and-contribs/doc...
== Shell script wrapper, to run the ruby script on a whole directory so you can batch convert all 8 chapters
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC_492_3...
=== Resulting asciidoc files
https://github.com/nickboldt/jbosstools-documentation/tree/TOOLSDOC_492_3... *.adoc
== Maven script to generate HTML and Docbook from the Asciidoc
https://github.com/nickboldt/jbosstools-documentation/tree/TOOLSDOC_492_3...
{code}
mvn clean install
{code}
=== Resulting html + Docbook files
The folder `jbosstools-documentation/userguide/target/generated-docs/` contains both xml and html files, plus images.
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: asciidoc-to-html5-with-sidebar-toc.png, converted-adoc-asciidoc-css-not-github-css.png, converted-adoc-github-css-actual.png, converted-adoc-github-css.png, openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png, xref-do-not-render.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16511) OpenShift Explorer: non-contextual entries in the application context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16511?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16511:
-------------------------------------
Fix Version/s: 4.2.0.Beta2
(was: 4.2.x)
> OpenShift Explorer: non-contextual entries in the application context menu
> --------------------------------------------------------------------------
>
> Key: JBIDE-16511
> URL: https://issues.jboss.org/browse/JBIDE-16511
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.0.Beta2
>
> Attachments: app_context_menu.png
>
>
> Context menu of application contains menu item for new connection (New -> Connection). I think, that this should not be listed in menu items, bcs. I'm in context menu of application and new connection has nothing to do with it.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16511) OpenShift Explorer: non-contextual entries in the application context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16511?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16511:
------------------------------------------
In JBIDE-15897 we went for the full set of entries in "New" (as discussed with Max). You should be able to create any OpenShift resource (connection, domain, application) with whatever is selected in the Explorer. That's also how the package explorer context menu is done in Eclipse.
> OpenShift Explorer: non-contextual entries in the application context menu
> --------------------------------------------------------------------------
>
> Key: JBIDE-16511
> URL: https://issues.jboss.org/browse/JBIDE-16511
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: explorer
> Fix For: 4.2.0.Beta2
>
> Attachments: app_context_menu.png
>
>
> Context menu of application contains menu item for new connection (New -> Connection). I think, that this should not be listed in menu items, bcs. I'm in context menu of application and new connection has nothing to do with it.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months