Arnaud Vandyck wrote:
On 5/26/07, Trygve Laugstøl <trygvis@apache.org> wrote:Arnaud Vandyck wrote: > If we wanna use maven to build, we need maven in main. If we want to > extract metadata, we just need an xslt or some > perl/python/java/whatever xml parser. No you don't. I meant that you can use Maven to generate the files and include in debian/. That way you can leverage the project's meta-data and start working on integration Maven into the build process until it is properly into main and those files can be generated build-time.I don't like the idea of generating those files at build time. But maybe I don't understand what you mean.
I think you understood me correctly. There is nothing wrong with generated files, there are already lots of them begin built on every .deb build. I know it's not ideal to check in generated files, but given the benefit it shouldn't be a big problem.
I made a Maven 2 plugin for this over *3* years ago [1], but still no-one has been able to leverage any of the metadata in Maven.
Anyway, tools used to generate and build debian package are in main so if we want to include maven calls in those scripts, we need maven to be in main.
Yes, do be a integral part of the build cycle it has to be. But it does not have to be there to be able to leverage a lot of the information that is inside every Maven-based project.
[1]: Probably even earlier than that, but that was when the repository was initialized: http://fisheye.codehaus.org/changelog/mojo?cs=5
-- Trygve