within an IDE plugin, like IvyDE for instance.
Maarten
- Original Message
From: Arcozen
To: ivy-user@ant.apache.org
Sent: Tue, February 23, 2010 5:50:32 PM
Subject: Re: Ivy repository strategies for Javascript artifact
Thanks a lot Mitch! :)
I agree about your considerations
On Tue 2010-02-23 at 08:31h, Mitch Gitman wrote on ivy-user:
> Marco:
:
> Just this sort of paradigm is already automatically supported with .war
> files and web containers. The WAR is the artifact, not its individual
> contents.
On the other hand Marco wrote:
> > 2) extract from zip archive ever
It's also possible you could deploy your zip directly and use e.g.
org.springframework.js.resource.ResourceServlet to serve up the
individual files. -Matt
On Feb 23, 2010, at 10:31 AM, Mitch Gitman wrote:
Marco:
If it's a versioned artifact that needs to be shared, then it's a
good fit
f
Thanks a lot Mitch! :)
I agree about your considerations.
Additional steps with Ant could help us during the build process, leaving
zip files in the repository.
2010/2/23 Mitch Gitman
> Marco:
> If it's a versioned artifact that needs to be shared, then it's a good fit
> for Ivy. As to the quest
Marco:
If it's a versioned artifact that needs to be shared, then it's a good fit
for Ivy. As to the question of whether to publish each individual file or
the entire archive, once you get into supporting a directory layout where
this file goes here and that file goes there and some files go in a c
