[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-386:
-------------------------------------
Assignee: Fred Bricon (was: Michelle Murray)
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
> Key: TOOLSDOC-386
> URL: https://issues.jboss.org/browse/TOOLSDOC-386
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.0
>
> Attachments: MavenTools_contentspec.pdf
>
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224
--
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
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-386:
------------------------------------------
[~maxandersen], [~fbricon]: please bring this JIRA to the attention of anyone else who is familiar with all of the technical aspects of Maven Tools and could review the content spec.
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
> Key: TOOLSDOC-386
> URL: https://issues.jboss.org/browse/TOOLSDOC-386
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.0
>
> Attachments: MavenTools_contentspec.pdf
>
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224
--
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
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-386:
-------------------------------------
Description:
Please review the content spec of the Maven Tools chapter from a technical viewpoint:
1) Is the info about features correct?
2) Are any features missing?
The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
The content spec is available here as a pdf. Alternatively, the content spec is also available at:
https://mojo.redhat.com/docs/DOC-19224
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
> Key: TOOLSDOC-386
> URL: https://issues.jboss.org/browse/TOOLSDOC-386
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
> Attachments: MavenTools_contentspec.pdf
>
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224
--
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
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-386:
-------------------------------------
Attachment: MavenTools_contentspec.pdf
> Review: Devs to review Maven Tools content spec
> -----------------------------------------------
>
> Key: TOOLSDOC-386
> URL: https://issues.jboss.org/browse/TOOLSDOC-386
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - Maven Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
> Attachments: MavenTools_contentspec.pdf
>
>
> Please review the content spec of the Maven Tools chapter from a technical viewpoint:
> 1) Is the info about features correct?
> 2) Are any features missing?
> The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts.
> For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later.
> The content spec is available here as a pdf. Alternatively, the content spec is also available at:
> https://mojo.redhat.com/docs/DOC-19224
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15361) CLONE - Create Datasource Dialog/Wizard usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15361?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15361:
----------------------------------------
Fix Version/s: 4.1.1.Alpha1
(was: 4.1.1.Final)
> CLONE - Create Datasource Dialog/Wizard usability
> -------------------------------------------------
>
> Key: JBIDE-15361
> URL: https://issues.jboss.org/browse/JBIDE-15361
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.1.0.Beta2
> Reporter: Burr Sutter
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.1.Alpha1
>
>
> The current Create Datasource dialog has a few usability "gotchas":
> 1) It is located under the "JBoss Tools Web" category - when it is more appropriate to be under the "JBoss Tools" category, closer to the Forge wizards - where you need it.
> 2) It defaults to AS5, not AS7 - it should default to EAP6/AS7
> 3) It defaults to register in persistence.xml - it is unclear to me how cleanly this injects into the current persistence.xml provided by the Forge wizards, I tend to uncheck it to be safe - then manually tweak up the persistence.xml to reference the same resource.
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-14591) Properties Tab for html elements
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14591?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14591:
----------------------------------------
Fix Version/s: 4.1.1.Alpha1
(was: 4.1.1.Final)
> Properties Tab for html elements
> --------------------------------
>
> Key: JBIDE-14591
> URL: https://issues.jboss.org/browse/JBIDE-14591
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta1
> Reporter: Burr Sutter
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1
>
> Attachments: 2013-05-22_1333.png, button.png, collapsible.png, image.png, listview.png, page.png, slider.png, video.png
>
>
> The Properties Tab currently only has a General category. I would like to see us have another category where we have identified the most used jQuery/jQuery mobile widget properties such as:
> id (always at the top)
> data-role
> data-icon
> data-iconpos
> other data-* set of properties
> value (for input fields, value is pretty important)
> type (for input fields, critical)
> placeholder
> The available properties can be more extensive than what was originally shown in the wizard/dialog when the widget was dragged from the palette. Any property deemed important enough to show in the wizard/dialog should also be promoted into this new category.
> My proposal for the category name: jQuery
--
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
10 years, 10 months