Following the new java policy, packages shouldn't rely on packed jars, dependencies need to be added on our own packages and used.
Created attachment 43613 [details] New ebuild to build velocity from source jars New ebuild that builds velocity from source jars. The following packages have been fixed >=dev-java/avalon-logkit-bin-1.2 >=dev-java/oro-2.0.6 dev-java/commons-collections dev-java/fop =dev-java/jdom-1.0_beta9 dev-java/antlr >=dev-java/bcel-5.1 >=dev-java/junit-3.8 >=dev-java/log4j-1.2.8 =dev-java/servletapi-2.3-r1 There are no builds available for w3c.jar werken.xpath.jar
werken.xpath.jar - that is the main problem of this bug. it seems to be a lot of work to build it from source. it is available but werken-xpath uses very old versions of libraries which are needed to compile the project. it asked the developers to update their project to make sure one can compile it with todays libraries, but they said that they wont do it. they said to me i should ask the velocity team to remove the deprecated library, i did that but there is no response email since yet. we could provide a binary ebuild for werken-xpath, but if you use the version which is available on sf.net you're not able to compile velocity.
I just added werken-0.9.4-beta to portage. This was based on the work done by jpackage. I should be able to commit a new revision that no longer uses bundled jars in the next day or two.
Fixed in CVS.
