[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2727:
-----------------------------
CDW pm_ack: ? (was: +)
> 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
>
> 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-2577) JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2577:
-----------------------------------
So, if we add m2e-wro4j to the list of connectors in JBoss Central, we just need to document how to switch between minified/raw js files using the Maven Profile manager.
This is by far the easiest solution to introduce minification support to JBDS, But it would be restricted to external js and css (i.e. js and css code inside html/jsp/whatever pages wouldn't be optimized). I don't know if yeoman/grunt/bower have the same limitation.
One downside is this would be restricted to mavenized projects.
Adding support for yeoman/grunt/bower will require much more work for sure.
> JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
> -----------------------------------------------------------------------
>
> Key: JBDS-2577
> URL: https://issues.jboss.org/browse/JBDS-2577
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Jiri Pallich
> Assignee: Max Rydahl Andersen
> Priority: Blocker
>
> Support non-minified JS libs for Dev, swap in minified JS libs for production (wro4j - maven integration?).
> Examples of JS libs: jQuery, jQuery Mobile
--
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-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2741:
-----------------------------
CDW devel_ack: ? (was: +)
CDW pm_ack: + (was: ?)
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2741
> URL: https://issues.jboss.org/browse/JBDS-2741
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, requirements, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Alpha2
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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