oh, and... typically library developers would target for the lowest JDK version available/possible so that users can keep running things on older JDKs.
and of course as long as SUN keeps their JDKs backward compatible. Regards Mark Donszelmann -----Original Message----- From: Donszelmann, Mark [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 7:39 PM To: Maven Users List; Brett Porter; Shane Isbell Subject: RE: Problem of targetting two JDK versions Hi well, that answers my question, but developers using my library would have to say exactly which version (read target) they would need... I understand it is pretty late in the design phase, but would the following scenario not make sense: I have one library (for which I maintain 3 source codes, in three different maven projects): a. mylib-4.1-jdk-1.5.jar b. mylib-4.1-jdk-1.4.jar c. mylib-4.1-cdc-2.1.jar which are published on the remote repository. Anybody depending on this would just need to depend on: mylib-4.1 and when compiling for one or the other target it will pick up the correct jar file: - jdk-1.5 as target, will need a. and can use templates. - jdk-1.4 as target, will need b. and needs to deal with casting, etc... - cdc-2.1 (I have no knowlegde of cdc, so the version number is bogus) as target for CDC. It is here where I think jar files are ABI (Application Binary Interface) specific, and it would be a pity if Maven 2 would not automatically deal with it. Regards Mark Donszelmann -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 7:04 PM To: Maven Users List; Shane Isbell Subject: Re: Problem of targetting two JDK versions And my answer is the same as the one in Shane's thread :) On 6/17/05, Shane Isbell <[EMAIL PROTECTED]> wrote: > Yep, I need that option as well. > > Shane > > On 6/16/05, Donszelmann, Mark <[EMAIL PROTECTED]> wrote: > > Hi > > > > I was wondering if Maven 2 handles (or is going to) the situation > > where a library is written in both java 1.4 and java 1.5. > > > > I understand that the -source and -target options can be set on the > > compiler, thus delivering jar files for jdk 1.4 and jdk 1.5, so that is ok. > > > > However, if I depend on this library, then I would just want to > > depend on either, depending on the version I am targetting my application > > for. > > > > Thus the library would have a unique name, but the dependency on it > > would say if I need the jdk 1.4 or jdk 1.5 version. > > > > This may in fact be related to an earlier post by Shane Isbell > > [EMAIL PROTECTED] of totally different targets: > > Re: Problem targeting two platform builds with Maven 2.0 CDC and > > J2SE. > > > > Will Maven 2 handle this and if so, how? > > > > Regards > > Mark Donszelmann > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
