[jbosstools-issues] [JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

Sande Gilda (JIRA) jira-events at lists.jboss.org
Wed Sep 18 15:35:03 EDT 2013


    [ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805601#comment-12805601 ] 

Sande Gilda commented on JBDS-2727:
-----------------------------------

[~rafabene] has an automated process that updates the archetype any time you change the quickstart that was based on it. When [~snjeza]'s cheat sheet for the kitchensink quickstart was merged, his process created the cheat sheet for the jboss-javaee6-webapp-archetype and modified it to use the ${package} variable rather than the hardcode paths.

I think this means we just need to create the cheat sheets for the related quickstarts, and the related archetype get the .cheatsheet.xml file for free.

If this is true, then item 1 on the list, the Java EE Web cheat sheet is complete. I believe [~fbricon] is testing it: 
https://github.com/jboss-jdf/jboss-as-archetype/blob/master/jboss-javaee6-webapp-archetype/src/main/resources/archetype-resources/.cheatsheet.xml

[~burrsutter] or [~bleathem]: The 3rd item on the list is a cheat sheet for RichFaces. Which quickstart is the one based on an archetype. I assume it's the kitchensink-rf?
                
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
>                 Key: JBDS-2727
>                 URL: https://issues.jboss.org/browse/JBDS-2727
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: central, requirements
>            Reporter: Burr Sutter
>         Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette.  It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application 
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations

--
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


More information about the jbosstools-issues mailing list