[
https://issues.apache.org/jira/browse/SHINDIG-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569512#action_12569512
]
Kevin Brown commented on SHINDIG-52:
------------------------------------
Has anyone looked into this recently? We're considering using some internal
tools for this task when rolling up our builds at Google, but we do have a
certain preference for keeping our code as close to "stock" Shindig as makes
sense for us. If not, I'll play with it and see if we can get the desired
results.
In a nutshell, what I'd like to see happen is this:
Input file: trunk/features/core/prefs.js (includes all comments and such)
Output file: war/features/core/prefs.js (minified as much as possible)
Nice to have bonus:
Additional output file: war/features/core/prefs.debug.js (same as original
source file; we can add special logic for allowing a "debug" retrieval as well
as a normal one.
> Use Maven Javascript Plugin to enable better builds
> ---------------------------------------------------
>
> Key: SHINDIG-52
> URL: https://issues.apache.org/jira/browse/SHINDIG-52
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java
> Reporter: Paul Lindner
> Assignee: Kevin Brown
>
> It would be great if the maven build process could incorporate the Javascript
> plugin mentioned here:
> http://hammerfest.sourceforge.net/maven-javascript-plugin/
> I'll have a look at how difficult it is to enable this. It would be nice to
> have minified javascript and multiple files combined into a single
> compilation unit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
