[
https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin....
]
Kris Borchers commented on JBDS-2577:
-------------------------------------
Modernizr is not meant to be used to swap between min/non-min JS. It is used to load
completely different resources based on feature support detection in the browser.
Most JS devs I know use one of two methods to switch. The first, which is less popular
among serious devs, is to just switch manually when you deploy your changes into
production. I do not recommend this approach. The second is that devs use some sort of
build tool to concat/minify their JS into one or a couple of files at deployment. Tools
like Yeoman/Grunt do this for you. That way during dev, your files are all non-minified
and once you deploy your application, all files are combined and minified and the files
that reference them are automatically updated to point to the new minified versions.
The other option is to use a source map. I have been doing that occasionally lately as
well. That provides, in browsers that support them, a way to use your minified files
during dev, but there is a map that points to the non-minified version and can actually
take you to the appropriate sections of the non-minified code when an error or break-point
is reached in the minified version.
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
Fix For: 7.0.0.Beta2
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