The ebuild needs to be updated to build the packages from source
Created attachment 43360 [details] New ebuild for maven-bin
I have created a new ebuild to build some pacakges from source. Some of the problems encountered are 1. SOme pacakges like commons-jelly do not exist in portage 2. Maven (actually Forehead) seems to want to load ant-optional-1.5.3-1.jar directly. THis jar contains all the optional tasks for ant. Gentoo installs ant-tasks where each task has a seperate jar. How do we work around this? 3. Some of the packages are older than the ones is portage.
1) Then we need to add it. Make out a new bug that we need it, and make this bug depend on it. 2) Download ant-optional-1.5.3-1.jar from the maven repo, unpack it and see what's inside. I have a hunch the stuff in ant-tasks covers it, so you have to rewrite the build script for Forehead to use the jar files from ant-tasks instead this one monolithic jar file. 3) Try with the newer ones and see if it works. If it doesnt' open a new bug for each package we need to create an older ebuild for, and make this bug depend on them. Typically, DEPEND/RDEPEND should be on the form =dev-java/<lib>-<major>.<minor>*, as <major>.<minor> typically has the same SLOT (but this is not strictly guaranteed).
Im not sure if I am misunderstanding the ebuild. But I believe you are just using the binaries and then replacing a few of the dependent library.
Created attachment 43538 [details] Ebuild for maven-1.0 from source The sources are required (also attached).
Created attachment 43539 [details] maven-20041106.tar.bz2
Created attachment 43540 [details] maven-plugins-20041106.tbz2
The build suffers from a sandbox access violation. The problem is with the second build (building maven using maven). The build is still successful. It is the test that is failing. Hopefully someone can figure this out, or help to figure it out.
Created attachment 43586 [details] 25maven place this file in the files directory
Created attachment 43593 [details] maven-1.0.ebuild
Sandbox violation fixed, additional architectures added (Only tested on x86).
Maybe the first release of this ebuild would change to maven 1.0.1? This version was released just a week ago.
*** Bug 72711 has been marked as a duplicate of this bug. ***
Created attachment 46446 [details] maven-1.0.2.ebuild
Created attachment 46447 [details] maven-20041219.tbz2
Updated to maven-1.0.2 as people are really asking for this. The issue of the jars being pulled from the web still exist. However, this is still being worked on. There was renaming of the cvs pulls and major clean up of the ebuild. All testing is welcome, and please post any errors or suggestions. Saleem
Created attachment 46457 [details] maven-1.0.2.ebuild Fixes jikes support
Created attachment 46886 [details] maven-1.0.2.ebuild Adds the RDEPENDs. Please DO NOT use this ebuild as it will most likely not work. The ebuild here is more for documentation purposes. It lists the needed dependencies (most of which dont exist in portage with the name in the ebuild). Saleem
just a small one, but I suspect you want maven.home.local in that ebuild, not naven.home.local.
*** Bug 88912 has been marked as a duplicate of this bug. ***
I've used the most recent ebuild, and added it to experimental. It turns out that there ar e number more dependencies than initially thought... the ones already listed were just for bootstrapping maven. The big thing I did is to attempt to recreate a maven repository at ${WORKDIR}/.maven/repository, and populate it with symlinks a la java-pkg_jar-from . Once maven is bootstrapped, I patched it to be in offline mode, so now its a matter of attempting to 'ebuild compile', let it fail, then see what jars it once.
*** Bug 117200 has been marked as a duplicate of this bug. ***
*** Bug 127952 has been marked as a duplicate of this bug. ***
*** Bug 175034 has been marked as a duplicate of this bug. ***
