[JBoss JIRA] (TOOLSDOC-393) Document bundled JBDS + EAP installer
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-393?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-393:
-------------------------------------
Sprint: Sprint 1
> Document bundled JBDS + EAP installer
> -------------------------------------
>
> Key: TOOLSDOC-393
> URL: https://issues.jboss.org/browse/TOOLSDOC-393
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: Installation Guide
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 1 hour, 15 minutes
> Remaining Estimate: 1 hour, 15 minutes
>
> Description: adding the latest version of EAP (6.1.1 unless something newer comes along) to the bundled JBDS + EAP universal installer
> Impact:
> * Add RN about update to EAP version in bundled JBDS + EAP installer
> * Installation Guide =
> ** 3.1 Install Options - add info about availability of bundled JBDS + EAP universal installer
> ** 3.2 Install JBoss Developer Studio - add info and note specifying what the bundled version provides, where to download and any additional step to get the bundles EAP installed
> * [Getting Started Guide = update TicketMonster assumptions, so don't have to have EAP already installed and work through bundled installer?]
> Estimate: write RN item + modify 2 sections = 1.25hr
--
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, 9 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Sande Gilda (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Sande Gilda commented on JBDS-2727:
-----------------------------------
Fred has made one simple change in this pull: https://github.com/jboss-jdf/jboss-as-archetype/pull/19
> 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
12 years, 9 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Rafael Benevides commented on JBDS-2727:
----------------------------------------
We can add any expression that we want to be replaced by {artifactId}. Look here: https://github.com/jboss-jdf/jboss-as-archetype/blob/master/jboss-javaee6...
> 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
12 years, 9 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
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...] and [there|https://github.com/jboss-developer/jboss-eap-quickstarts/blob/maste...]
[~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...] and [there|https://github.com/jboss-developer/jboss-eap-quickstarts/blob/maste...]
> 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
12 years, 9 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2727:
-----------------------------------
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...] and [there|https://github.com/jboss-developer/jboss-eap-quickstarts/blob/maste...]
> 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
12 years, 9 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2727:
-----------------------------------
Guys, in order for the cheatsheets to show up in JBDS, you need to fix 2 things :
- add the cheatsheets files to the archetype metadata descriptor : https://github.com/jboss-jdf/jboss-as-archetype/pull/19
- fix the cheatsheets so the <?xml ?> directive appears first. Currently the copyright header first prevents the cheatsheets from opening in JBDS (https://github.com/jboss-developer/jboss-eap-quickstarts/blob/master/kitc...)
> 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
12 years, 9 months
[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2767:
----------------------------------
[~maxandersen] If this is a +1 for JBDS 7.1.0, can you set all the correct CDW ACK crap in place so I can devel_ack it and make it happen?
[~rob.stryker] Does anything need to happen here except me adding the new tomcat.feature into the JBDS 7.1 update site and into the Core Features feature.xml so it's installed OOTB?
> Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
> ---------------------------------------------------------------------
>
> Key: JBDS-2767
> URL: https://issues.jboss.org/browse/JBDS-2767
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: servers, updatesite
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Attachments: 15498.png
>
>
> Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0.
> Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances.
> Original from Nick:
> Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7.
> Comparing the update sites for JBT 4.1.x and JBDS 7.1.x:
> !15498.png!
> Was it intentionally excluded from the update site, or forgotten?
--
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, 9 months