[JBoss JIRA] (JBIDE-15382) Create target platform from Kepler SR1 (RC) dependencies
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15382?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15382:
------------------------------------
Final Kepler SR1 bits will be available as of 2013/09/19 or 2013/09/20, so next week, please pull the updated bits into a 4.31.0.Alpha2 target platform for release by Wed 2013/09/25. That way it's reviewed, released, and finalized (?) before Alpha2 code freeze on Thu 2013/09/26.
Unless of course [~fbricon] has new m2e-wtp bits released AFTER that date. :D
> Create target platform from Kepler SR1 (RC) dependencies
> --------------------------------------------------------
>
> Key: JBIDE-15382
> URL: https://issues.jboss.org/browse/JBIDE-15382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0.
> [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1
> There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items.
> For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS.
> === FORMAL REQUEST ===
> Reason: Leverage bugfixs of Kepler SR1 RC1 (or RC2 for components which already submitted RC2)
> License and owner: EPL, Eclispe community
> Original repository: download.eclipse.org webtools,kepler,mylyn,tm,m2e,orbit
> JBoss Mirrored repository:
> Source: git.eclipse.org
> Affected projects: All
> Required in devstudio: Yes
> Type of dependency: distributions
> List of bundles: only some version changed + new dependency for EGit (org.tukaani.xy)
--
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-2727) Cheatsheets for JBoss Central archetypes
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Snjezana Peco reassigned JBDS-2727:
-----------------------------------
Assignee: Fred Bricon (was: Snjezana Peco)
> 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: Fred Bricon
> 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-2727) Cheatsheets for JBoss Central archetypes
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Snjezana Peco commented on JBDS-2727:
-------------------------------------
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