[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Snjezana Peco edited comment on JBDS-2727 at 9/16/13 11:21 AM:
---------------------------------------------------------------
The guide seems to look good.
Maybe, you would need to add more info about the $\{currentProject\} property.
{quote}
Use the replaceable value $\{currentProject\} to avoid hard-coding the project path. This ensures that if the quickstart folder is moved, the cheat sheet will work as expected.
{quote}
To use the $\{currentProject\} property, you have to add the getProjectForCheatsheet command as described at https://issues.jboss.org/browse/JBIDE-12915?focusedCommentId=12794158&pag...
was (Author: snjeza):
The guide seems to look good.
Maybe, you would need to add more info about the ${\currentProject\} property.
{quote}
Use the replaceable value $\{currentProject\} to avoid hard-coding the project path. This ensures that if the quickstart folder is moved, the cheat sheet will work as expected.
{quote}
To use the $\{currentProject\} property, you have to add the getProjectForCheatsheet command as described at https://issues.jboss.org/browse/JBIDE-12915?focusedCommentId=12794158&pag...
> 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
> Assignee: Snjezana Peco
> 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
12 years, 7 months
[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2763:
-------------------------------------
If we change the installer window title to Red Hat JBoss Developer Studio, shouldn't we then also change the JBDS window title, too? Not that I'm a fan, just saying... ;)
> REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2763
> URL: https://issues.jboss.org/browse/JBDS-2763
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
>
> Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
> !https://issues.jboss.org/secure/attachment/12364502/12364502_ins-step-5.png!
> Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar?
> What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
--
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, 7 months
[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2763:
-----------------------------
Description:
Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
!https://issues.jboss.org/secure/attachment/12364502/12364502_ins-step-5.png!
Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar?
What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
was:
Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar?
What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
> REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2763
> URL: https://issues.jboss.org/browse/JBDS-2763
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
>
> Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
> !https://issues.jboss.org/secure/attachment/12364502/12364502_ins-step-5.png!
> Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar?
> What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
--
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, 7 months
[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2763:
-----------------------------
Description:
Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
Should we also rename the jbdevstudio-***.jar files to rhjbdevstudio-***.jar?
What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
was:
Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
Should we also rename the jbdevstudio-*.jar files to rhjbdevstudio-*.jar?
What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
> REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2763
> URL: https://issues.jboss.org/browse/JBDS-2763
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
>
> Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
> Should we also rename the jbdevstudio-***.jar files to rhjbdevstudio-***.jar?
> What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
--
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, 7 months
[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2763:
-----------------------------
Description:
Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar?
What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
was:
Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
Should we also rename the jbdevstudio-***.jar files to rhjbdevstudio-***.jar?
What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
> REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2763
> URL: https://issues.jboss.org/browse/JBDS-2763
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
>
> Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
> Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar?
> What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
--
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, 7 months
[JBoss JIRA] (JBDS-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2763:
--------------------------------
Summary: REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?
Key: JBDS-2763
URL: https://issues.jboss.org/browse/JBDS-2763
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: build, installer
Affects Versions: 7.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ?
Should we also rename the jbdevstudio-*.jar files to rhjbdevstudio-*.jar?
What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ?
--
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, 7 months