I'm considering moving my solution to using the concept of WAR overlays;
a WAR project that requires certain javascripts specifies those as project
dependencies, which themselves are simple WAR projects with only js files in
their correct paths
they get slapped onto the using WARs, and presto, no
From: Manos Batsis [mailto:manos_li...@geekologue.com]
On 06/15/2010 01:55 AM, Haszlakiewicz, Eric wrote:
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
-Original Message-
From: Shan Syed [mailto:shan...@gmail.com]
I've worked on projects that share common javascript files, so I used a
simple assembly descriptor to zip each set of files and install them as
maven artifacts
WAR projects then just specified them as dependencies in their POMs
I've got a webapp that uses javascript files from third party projects.
For instance, one of the files we use is prototype.js. It seems like
this must be something that many people have done in the past, but I
can't seem to find much information about it.
The first issue I have is that I can't
I don't know the state of the plugin, but have a look at the Maven
Javascript Plugin.
http://mojo.codehaus.org/javascript-maven-tools/javascript-maven-plugin/index.html
Hth,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Tue, Jun 15,
On 06/15/2010 01:23 AM, Haszlakiewicz, Eric wrote:
I've got a webapp that uses javascript files from third party projects.
For instance, one of the files we use is prototype.js. It seems like
this must be something that many people have done in the past, but I
can't seem to find much
-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
I've worked on projects that share common javascript files, so I used a
simple assembly descriptor to zip each set of files and install them as
maven artifacts
WAR projects then just specified them as dependencies in their POMs
it's nice then to be able to treat these artifacts like any other
On 06/15/2010 01:55 AM, Haszlakiewicz, Eric wrote:
-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.
