Re: [mojo-user] [ANN] JSZip Maven Plugin 0.1-alpha-1 released

2012-06-02 Thread martin.eisengardt
Hi. I would like to help too. Especially with Extjs :) Greetings Martin

Re: [mojo-user] [ANN] JSZip Maven Plugin 0.1-alpha-1 released

2012-06-01 Thread Christopher Hunt
Hi Stephen, Not sure if you know, but the JS Import project (1) can already utilise zip files with a www classifier. The regular Assembly plugin can be used to make these packages. The following type of dependency declaration can then be made: dependency

Re: [mojo-user] [ANN] JSZip Maven Plugin 0.1-alpha-1 released

2012-06-01 Thread LeClaire Garvin
I think there is also some overlap with the web jar repository (https://github.com/webjars/webjars.github.com) project Regards, Garvin LeClaire garvin.lecla...@gmail.com On Jun 1, 2012, at 10:19 AM, Christopher Hunt wrote: Hi Stephen, Not sure if you know, but the JS Import project (1)

Re: [mojo-user] [ANN] JSZip Maven Plugin 0.1-alpha-1 released

2012-06-01 Thread Stephen Connolly
On 1 June 2012 15:19, Christopher Hunt hu...@internode.on.net wrote: Hi Stephen, Not sure if you know, but the JS Import project (1) can already utilise zip files with a www classifier. The regular Assembly plugin can be used to make these packages. The following type of dependency

Re: [jszip-dev] Re: [mojo-user] [ANN] JSZip Maven Plugin 0.1-alpha-1 released

2012-06-01 Thread Stephen Connolly
Yes, though jars don't work as well for packaging... let's drop the other mailing lists (left on BCC to let them know they are being dropped ;-) ) and move to just jszip-...@googlegroups.com On 1 June 2012 15:24, LeClaire Garvin garvin.lecla...@gmail.com wrote: I think there is also some overlap

Re: [mojo-user] [ANN] JSZip Maven Plugin 0.1-alpha-1 released

2012-06-01 Thread Christopher Hunt
On 02/06/2012, at 12:30 AM, Stephen Connolly wrote: Oh I know about that but it prevents the live editing that is possible by using the jszip packaging type. With the MJS setup, it is normal to edit the js files having previously invoked mvn jetty:run on the command line. In another terminal,