I have been working on and off in my spare time on a better story for Maven and JavaScript development. You can see the results of my efforts at jszip.org
Personally speaking I think there are only a few issues left to resolve:
As part of the effort, I do repackage JavaScript libraries as simple .zip
files, you can see a complete list on central and you will note that jQuery is one of them, though I probably have to pick up the 1.9.x releases when I next get a window of opertunity
Because I am packaging these as plain simple .zip
files you don't have to use the rest of the jszip toolchain, though obviously I think it superior to just unpacking the .zip
as part of your build with, e.g. dependency:unpack-dependencies
Here is an example of how to add a jszip module using its tooling:
<project>
...
<dependencies>
...
<dependency>
<groupId>org.jszip.redist</groupId>
<artifactId>jquery</artifactId>
<version>1.8.3</version>
<type>jszip</type>
</dependency>
...
</dependencies>
<build>
...
<plugins>
...
<plugin>
<groupId>org.jszip.maven</groupId>
<artifactId>jszip-maven-plugin</artifactId>
<extensions>true</extensions>
<executions>
<execution>
<goals>
<goal>unpack</goal>
</goals>
</execution>
</executions>
</plugin>
...
</plugins>
...
</build>
<!-- this next part assumes you want to minify all javascript for releases
and that your release profile used by the maven release plugin is called
'release' (i.e. the default) -->
<profiles>
<profile>
<id>release</id>
<build>
<plugins>
<plugin>
<groupId>org.jszip.maven</groupId>
<artifactId>jszip-maven-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>optimize</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>