On Sat, Jan 10, 2004 at 04:29:04PM -0800, jkw wrote: > > for a maven-using project the project.xml is the only logical place > for dependency info, which means the portage info would have to > extracted from that. that could be done as part of the process of > making the ebuild. it's possible the whole ebuild could be > automatically generated based on a template and a transform on the > project.xml; after all the maven project and the gentoo ebuild are > functionally similar. > > > to support maven as a build tool, after download the dependent jars > could be symlinked into a temporary maven-style repository, which > maven would be instructed to use during build.
I was hoping for something like this. It appears that the repository on ibiblio that maven uses does not provide source code for the various 'modules', so we'll still have to package the various dependencies in the old-fashioned way. Without having looked at Maven, I also suspect we could patch it to have a 'Gentoo-mode' where it just stopped with an error whenever it ended up actually doing any downloading while being used inside Portage as a build tool, but this must of course never interfere with regular end-user usage of Maven. Kind regards, Karl T -- [EMAIL PROTECTED] mailing list
