>-----Original Message----- >From: Manos Batsis [mailto:manos_li...@geekologue.com] > >There is no standard convention yet AFAIK. Including the JS libs in the >war is one thing, making it accessible to the browser through a specific >URL is another.
Well that sucks. :( >Here (at Abiss.gr) we use the JStools plugin [1]; we include JS libs >using JARs as everything else and a filter [2] to serve scripts to the >client. I think the maven-javascript-plugin [3] has something else. > >Searching the archives should give more info, although both projects >have pretty good documentation. Overall however, JS libs in repos have >not cought on - you will have to include libs in your own repo for most >stuff. > >[1] http://dev.abiss.gr/mvn-jstools/ >[2] http://dev.abiss.gr/mvn-jstools/js-packaging.html >[3] http://mojo.codehaus.org/javascript-maven-tools/ Yeah, I started to take a look at the maven-javascript-plugin, but it looks very oriented towards *developing* js packages, and I just want to *use* an existing one. It also isn't clear how to tell it where to actually put the files. I didn't see anything like that in the mvn-jstools either, and using a filter isn't going to work very well for my project. (At the moment I just need to get an existing project converted to maven with NO changes to the code at all) I'll take a closer look tomorrow and see if there's something I can use. Thanks, eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
