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

Fred Bricon (JIRA) jira-events at lists.jboss.org
Thu Sep 19 16:39:03 EDT 2013


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

Fred Bricon edited comment on JBDS-2727 at 9/19/13 4:38 PM:
------------------------------------------------------------

Another thing worth fixing in the cheatsheet is the project name (kitchensink), hardcoded at the end [here|https://github.com/jboss-developer/jboss-eap-quickstarts/blob/master/kitchensink/.cheatsheet.xml#L692] and [there|https://github.com/jboss-developer/jboss-eap-quickstarts/blob/master/kitchensink/.cheatsheet.xml#L697]

[~rafabene] : I suspect the project name is not replaced by ${artifactId} in the archetype because qs-tools is case sensitive and/or requires to be surrounded by whitespaces. 
                
      was (Author: fbricon):
    Another thing worth fixing in the cheatsheet is the project name (kitchensink), hardcoded at the end [here|https://github.com/jboss-developer/jboss-eap-quickstarts/blob/master/kitchensink/.cheatsheet.xml#L692] and [there|https://github.com/jboss-developer/jboss-eap-quickstarts/blob/master/kitchensink/.cheatsheet.xml#L697]
                  
> 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