You're right that there's a less compelling argument for publishing
top-level artifacts like WARs to an Ivy repository. I'd be curious what
rationales others out there have found for publishing EARs or WARs to their
Ivy repository.
We publish .war files to our repository so they can be deployed to the web nodes as part of their update scripts by doing a simple svn export of the war file on those machines without needing to do a checkout and build of the entire project.

Reply via email to