Apache Ivy: resolving dependencies embedded in an installer?

The problem with a call to "ivy:retrieve" is that you need to also add an "artifact" tag in your ivy. Xml (complete with URL) in order to retrieve a dependency not found in a Maven respository I don't like this for two reasons The ivy. Xml should just declare your dependencies, not their locations Need additonal custom logic in the build.

Xml to handle the 3rd party package Ideally it should be your repository settings that decide how to download the various jars, that is why I like the packager resolver. Even if the library I want is not in Maven, I can configure ivy to handle it The following is an example of turning the jreleaseinfo project into an ivy dependency (hosted in sourceforge, I couldn't find it in Maven) ivy. Xml :?

Xml version="1.0" encoding="ISO-8859-1"?

The problem with a call to "ivy:retrieve" is that you need to also add an "artifact" tag in your ivy. Xml (complete with URL) in order to retrieve a dependency not found in a Maven respository... I don't like this for two reasons The ivy. Xml should just declare your dependencies, not their locations.

Need additonal custom logic in the build. Xml to handle the 3rd party package Ideally it should be your repository settings that decide how to download the various jars, that is why I like the packager resolver. Even if the library I want is not in Maven, I can configure ivy to handle it.

The following is an example of turning the jreleaseinfo project into an ivy dependency (hosted in sourceforge, I couldn't find it in Maven) ivy. Xml: Declare two resolvers. Default is Maven2, the other is a packager configured to look locally for instructions.(See also the Ivy Roundup project) ivysettings.

Xml The magic is containing in the "packager" file. At resolve time this will be used to generate an ANT script that both downloads and extracts the required jars.(No need to put this logic into your build. Xml) repository/ch.

Oscg/jreleaseinfo/1.3.0/packager. Xml To reduce the number of files I omitted the module's ivy.xml. This appears to be optional unless you want to declare it's licence and other attributes that should be present in a public repository.

IvyRoundup is a public packager repo. But packager is exactly the way to go. – SEK Feb 15 at 11:14.

I think this is very straightforward: 'ivy:retrieve' a_installer and then unzip a. J and a-lib into your lib directory (or wherever you want it). This should be easily to do with ant?

I have to wonder if there is some complication you haven't mentioned that prevents you from doing this.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.