I really don't see the point in this. Whilst I can see your intention, I do not see the need, nor do I see realistically that it is feasable.
I do agree with the limitations that you state and I can think of more. To the point that I think it could only cover such a small subset of cases as to be questionable as to whether you'd bother. Perhaps you could better explain your thinking on the need? -Chris Sent from my iPhone On 24/04/2012, at 10:42 PM, Benson Margulies <bimargul...@gmail.com> wrote: > From time to time, there is an impedance mismatch between the desires > of an open source development community and the nature of Maven as a > *binary* dependency management system. While I wouldn't, for a moment, > suggest tampering with the existing binary system, I was wondering how > hard it would be to build a plugin, perhaps inspired by the scm > plugin, that could download and build source. > > One hopes to discover that the -sources artifact for a gav is, in > fact, comprehensive and buildable. Could the results of such a build > enter the reactor without core changes, or would there need to be a > two-phase approach? This, of course, assumes that the sources are (a) > buildable and (b) buildable with maven. (Give or take antrun or other > scripting.) A further interesting wrinkle would be to add patch > application to the mix -- possibly a problem bounded by the need for a > Java implementation of 'patch'. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
