Le 09/03/2012 03:03, sebb a écrit : > Some while back, we discussed including binary (and source) jars for > the test code in releases. > [The test source code is already included in the source archive]. > > The intention was to make it easier to run binary compatibility tests > against new releases.
Yes, I remember you raised important compatibility issues when we tried to release 2.1, so it saved us from doing big mistakes. > > I think it would be worth adding this to the release profile. > The effect will be to create 2 more jars. +1 > > Ideally the test.jar should be included in the binary zip/tar files. -1. I think it should be separated. As our components are picked up as dependencies to higher level projects, they don't always know precisely how they are managed. So the jar may end up in there top level application just because they throw everything they find the binary distribution in. > That will have to be done by each component as it will usually require > an edit to the assembly descriptor. > But in any case the jars would be available from the Maven repo if required. +1 Luc > > OK? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
