Greetings, On Thu, Aug 26, 2010 at 12:53 PM, Manos Batsis <[email protected]> wrote: > > The only reason to package those javascript files in JARs and upload them to > the maven central repo is for other projects to reuse them as dependencies. > I don't think this is your case.
This definitely wasn't what he asked to do, and you were right to answer him directly. I answered the question that I think he *should* have asked.. ;-) Perhaps complicating things far too much.. > On the other hand and since most javascript projects do not produce maven > dependencies for the maven users out there, it might make sense to establish > a community in this list to maintain popular JS lib dependencies. > > Some questions to list members: > > - Does it sound like a good idea and why? > - How should we go for it in organizing a team of maintainers? > - How should those JS libs packaged? There's already a javascript project on codehaus[1], I am surprised that they do not already publish Maven artifacts for popular frameworks. I'd recommend publish them in a variety of formats: * maven-remote-resource-bundle * jar * war The first could be used to seed the second and third. Let the users choose for themselves which works best for them.. -Jesse [1] http://mojo.codehaus.org/javascript-maven-tools/ -- There are 10 types of people in this world, those that can read binary and those that can not. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
