[
https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2577:
-------------------------------------------
I've added those I know that this issue affects or have an opinion to the list of
watchers.
The requirement comes from [~burrsutter] but I'm not sure if we can do anything about
this issue beyond what we got already.
Note: making minified javascript validate properly is a *separate* concern to this. This
one is just about how to handle "swapping" between minified vs nonminified
libraries.
My wager is that this is not something the tools will "care" about - it is
handled by using tricks like
modernizer(http://modernizr.com/docs/#load) and/or
wro4j(https://code.google.com/p/wro4j/ /
https://code.google.com/p/wro4j/wiki/MavenPlugin).
Thus it becomes a 100% runtime or in case of wro4j, a maven build issue.
What we just need it is to know which conventions to suggest/document for those using
modernizer and wro4j.
How do you guys handle it for local development ?
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