ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Gill" <>
Subject Re: Spring 2.0.7 Packaging Problem
Date Thu, 06 Dec 2007 01:04:04 GMT
Download all your artifacts (spring and otherwise) and build your own
repository. It takes a little longer to setup, but in the end you have total
control. Relying on external repositories is a really bad idea IMO.

On Dec 6, 2007 7:49 AM, Edward Sumerfield <> wrote:

> Ivy downloads the spring-core.jar version 2.0.7 which does not contain
>    org.springframework.scripting.config.LangNamespaceHandler
> When I download from the spring site I get the scripting package in the
> single spring.jar.
> What is the best approach to dealing with these kinds of inconsistencies?
> Start with public repositories first and then bring them into the shared
> or
> build the shared repository as you go to ensure that you have what you
> want?
> If I am having to rely on building my dependency xml files myself I wonder
> how much I am saving using Ivy. I like the idea of being specific but the
> brute force method of including **/* is enticingly simple.
> --
> Ed

John Gill

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message