<p>I like the mapping idea, perhaps with a hook for your minification tool of choice? One of the ideas I've been rollicking around is: minifaces </p>
<p>:)</p>
<p>Lincoln Baxter III<br>
<a href="http://ocpsoft.com">http://ocpsoft.com</a><br>
<a href="http://scrumshark.com">http://scrumshark.com</a><br>
Keep it simple.</p>
<p><blockquote type="cite">On Dec 23, 2009 4:01 PM, "Imre Osswald" <<a href="mailto:ioss@mx.jevelopers.com">ioss@mx.jevelopers.com</a>> wrote:<br><br><div style="word-wrap:break-word"><div> </div><div><br>
<div><div><div><p><font color="#500050">On 23.12.2009, at 21:22, Dan Allen wrote:
> On Wed, Dec 23, 2009 at 3:17 PM, Lincoln Baxter, III <l...</font></p>While it would be great to have jsf automatically resolve duplicates/versions, I think sometimes the developers has to get involved, so first of all it should be possible to map resource-requests to other resources, so that a user (=developer) could say (.*)jquery(.*).js maps to lets say a jquery-min-1.2.13.js resource in some other jar or war.<div>
(This could even be used to replace images of components with one line, if you allow for references from the matches on the source-regexp in the target-exp)</div><div>While it is possible to do that on your own, I think that could be a valuable addition to the specs.</div>
<div><br></div><div>Concerning version issues, I don't think we should come up with a solution (which would probably involve versionnamespacing the included scripts and the calls to it... ugly!) but as suggested just say "you're on your own".</div>
<div><br></div><font color="#888888"><div>Imre</div></font></div></div></div></div></div></blockquote></p>