Hi Phil, Phil Steitz wrote:
[snip] >> For the release you can now activate the appropriate JDK profile, provide >> the versions with the command line and possibly we can additionally add >> an enforcer rule to avoid errors. > > If maven can do the filtering to help create the source branches / > tags, that could eliminate the need to run Ant separately; but there > is also a nice feature of the Ant build that makes testing easier - > it can detect JDK levels and filter dynamically, so you can get all > of them working before you start splitting things out. Nobody stops you from activating the profiles automatically based on the JDK you let Maven run, but then it is not possible to run *Maven* with a different JDK than the one that is used to compile the (filtered) source and run the tests. It simply depends on what we want. The filtering itself is still Ant, but automatically invoked by Maven. > A key thing > we have to remember is that for each version, we need a tag that > corresponds exactly to what is released in that version and the > source in that tag has to build using the target JDK. That's exactly what happens with the profile solution. One release for each profile. > Are you guys OK with me plowing forward with the setup I described > yesterday - basically extending the Ant filtering - or should I hold > off creating the 1.5 branch and adding the filter tags? We have a do-ocraty ;-) Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
