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 deploy
buzzterrier wrote:
I publish milestone and release status artifacts to the same Ivysvn
repository using the ivy buildnumber feature. Below is the milestone ant
task I use (note that the release task is identical, but has a "release"
status):
Using "latest.integration" will retrieve whatever Ivy decides is the
latest version of an artifact. You can set this to be any specific
version you have published if you so desire. For example, if you
published version 1.1 of module "x" and then later published version
1.2, using "latest.integr
Garry Smith wrote:
That is good to hear. We currently have jars in our SVN that are
organised in the same way you mention (by
organisation/module/version). To move to the Ivy way of resolving
dependencies it sounds like we just have to include the appropriate
ivy metatdata for each existing
Like Maarten said, this looks like it was fixed in Ivy 2.0.0-RC1 so if
you upgrade to that version and try again it should work.
Burkhardt Stefan (CI/TMP) wrote:
Hi Maartin,
I am currently using apache-ivy-2.0.0-beta2.
Stefan
-Ursprüngliche Nachricht-
Von: Maarten Coene [mailto:[EM
It would be helpful if you could provide the relevant fragments of your
ivy files so we can see how you have set things up.
Guilherme Namen Pimenta wrote:
When i configure ivy to retrive postgresql 8.3-603.jdbc3 from maven
repo, ivy download and put the jar source not the jar with class files.
