Re: Deploying to a Maven Repo with Ivy

On Oct 15, 2008, at 9:50 AM, Gilles Scokart wrote: Concerning the mapping, did you have thought to map one ivy module to multiple maven poms. I think that if you want to keep the same richness, when you have an ivy file with multiple functional configurations, you should generate multiple

Re: Next step in Ivy 2.0 release process

2008/10/15 Maarten Coene [EMAIL PROTECTED]: Hi, Ivy-2.0.0-RC1 is out for some time now. What will be the next step? - create a new RC2 release containing some (or all) of the bugfixes which have been committed into SVN trunk and maybe some open issues which aren't fixed yet - create a

Re: Next step in Ivy 2.0 release process

Le jeudi 16 octobre 2008, Gilles Scokart a écrit : 2008/10/15 Maarten Coene [EMAIL PROTECTED]: Hi, Ivy-2.0.0-RC1 is out for some time now. What will be the next step? - create a new RC2 release containing some (or all) of the bugfixes which have been committed into SVN trunk and maybe

Re: Deploying to a Maven Repo with Ivy

On Oct 16, 2008, at 10:14 AM, Hans Dockter wrote: On Oct 15, 2008, at 9:50 AM, Gilles Scokart wrote: Concerning the mapping, did you have thought to map one ivy module to multiple maven poms. I think that if you want to keep the same richness, when you have an ivy file with multiple

Re: Deploying to a Maven Repo with Ivy

2008/10/16 Hans Dockter [EMAIL PROTECTED]: On Oct 16, 2008, at 12:39 PM, Gilles Scokart wrote: Even if you have a single jar, that can work. To continue with you example of hibernate.jar with a withEHCache and withDistributedTransactions configuration, you could have 3 modules generated.

Re: Deploying to a Maven Repo with Ivy

On Oct 16, 2008, at 12:39 PM, Gilles Scokart wrote: Even if you have a single jar, that can work. To continue with you example of hibernate.jar with a withEHCache and withDistributedTransactions configuration, you could have 3 modules generated. One will be the hibernate-core which will be a

Re: Next step in Ivy 2.0 release process

On Thu, Oct 16, 2008 at 10:39 AM, Gilles Scokart [EMAIL PROTECTED] wrote: 2008/10/15 Maarten Coene [EMAIL PROTECTED]: Hi, Ivy-2.0.0-RC1 is out for some time now. What will be the next step? - create a new RC2 release containing some (or all) of the bugfixes which have been committed

Re: Deploying to a Maven Repo with Ivy

Even if you have a single jar, that can work. To continue with you example of hibernate.jar with a withEHCache and withDistributedTransactions configuration, you could have 3 modules generated. One will be the hibernate-core which will be a classical pom with an artefact (and probably the common

Re: Compiling fails on JDK 1.3

Stefan Bodewig wrote: On Fri, 10 Oct 2008, Jan Materne [EMAIL PROTECTED] wrote: I tried a build on JDK 1.3/WinXP-SP2, but that failed. The constructor FileOutputStream(File, boolean) was added in JDK 1.4. Should be easy to fix, I'm just not sure whether it needs to be.

ivy settings classpath always creates new classloader when used with subant

Hi, I have a custom Ivy resolver that keeps a static cache because it is time-consuming to initialise. However, this cache doesn't work in a multi-project build, because the ivysettings/classpath command is creating a new URLClassLoader for each subant iteration, so all static class fields

CVS tests

Hi all, I've committed a test CVS repository to Ant's svn repo under src/tests/antunit/taskdefs/cvs together with an AntUnit test file that doesn't get executed as part of the top level build file (because we'd need to check for a working cvs setup otherwise). It seems to work for me.