It is not exactly what you want, but you can use a conf. The only thing is that your build script will have to manage that. Ivy will not analyse for you the jdk/jre that you are using.
Note that I'm not sure it is feasible without input from the build script. Indeed, even if your script is running in a jdk 1.5, you might only want the dependency on 1.4. I don't have the link, but I remind me some weeks (maybe months) ago a related discussions concerning the possibility to declare the java version on which your module depends. I don't know if there is already a jira issue for that. Gilles > -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Sent: jeudi 8 février 2007 11:41 > To: [email protected] > Subject: Re: What is the default jdk version for Ivy? > > Kevin Jackson wrote: > > Hi, > > > > Just (finally) got time to check out the ivy codebase and start poking > > around. > > > > What version of Java is it supposed to be compatible with? I'm making > > an assumption that it should really be as compatible as Ant is > > (jdk1.2+), but I'd like confirmation. > > Actually, this reminds me of a related problem. > > is there any way to make a module/dependency conditional on, say, a JDK > version. > > At work the core app and most of the libraries build on java1.4, but I > have some extras that need java 5, and am debating a java6 library to > get the extra features there (file system permissions, built in http > server) > > I can't include these dependencies in our release module because they > are only buildable on java1.5 and 1.6; it screws up people building on > java1.4. > > is there anything like > > <depends module="sf-java6-stuff" if="jdk1.6+" />
