On Fri, 2013-07-26 at 15:30 +0100, sebb wrote: > On 26 July 2013 15:18, Oleg Kalnichevski <[email protected]> wrote: > > Folks > > > > Both HttpCore and HttpClient trunks (especially the latter) have a > > significant number of deprecated classes that accumulated in the course > > of 3 feature releases. I would rather see them removed but we have to > > practical about it. As an alternative, I would like to move deprecated > > classes to a separate src folder ./src/deprecated/java > > or ./src/main/java-deprecated. This would enable us to apply different > > policies to those classes, exclude them from the test coverage reports, > > and simply not to have them in the way. This change will not affect > > binary compatibility, just packaging. > > > > I hope there will be no objections but if I am mistaken please make them > > known now before I start moving classes around. > > No objection, but this will require quite a few changes to poms, as > one can no longer rely on the default Maven configuration. > > There are only about 5 deprecation warnings in httpcore, so I suggest > leaving that. >
Supposedly this thing can be used to inject additional sources to the Maven's generate-sources phase, which should cause only minimal changes to the pom metdata. Remains to be seen if that is indeed the case. http://mojo.codehaus.org/build-helper-maven-plugin/add-source-mojo.html Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
