John Casey wrote:
Maven is a perfectly suited package management tool for its native language: Java. If you find some project which _happens_to_be_ built in a non-portable way, why not just throw up your own maven repository, and add a piece to the default build.properties, placing your repository first in the list to check for dependencies? You can then distribute this file with the distro in question, and everyone will be happy. I
That's a nice idea, thanks. Dion proposed something similar, and it seems that it could be a way to make Maven play along with native package management. Joerg has discussed that aproach with gentoo developers, afaik.
don't understand why it has to turn into such a ground-shifting change. While it's definitely not perfect, a very simple patch to maven (to remove the Base64 encoder dependency) will accommodate everything you've mentioned in your emails, Dalibor.
You must have joined us in the middle of the discussion. That was a different thread. Maven's small portability problems that prevent the CVS from working on kaffe are unrelated to this thread.
This thread is about a new idea of using maven for software management and distribution. There is nothing kaffe-specific in that idea, it's not even mine ;)
cheers, dalibor topic
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
