It is possible to emerge dev-java/maven-bin without having dev-java/forehead installed; however, I was unable to run maven without installing forehead manually because of some ClassNotFound exception pointing to forehead. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I second this; dev-java/forehead is required for dev-java/maven-bin to work. But dev-java/forehead is ~x86 (dev-java/maven-bin is x86).
Hi, dev-java/Maven-bin already come with forehead (1.0-beta-5) in /usr/share/maven/lib without actually installing forehead. neurogeek
Could you post more information? In particular, which version of maven-bin this was with, and a log of the messages you get when you attempt to run it.
dev-java/maven-bin-1.0 % maven Exception in thread "main" java.lang.NoClassDefFoundError: com/werken/forehead/Forehead Emerging forehead [dev-java/forehead-1.0_beta5] and running env-update makes maven run on ~amd64 [after keywording forehead appropriately].
I've installed forehead but maven still doesn't run (did env-update) i've installed (on x86): dev-java/maven-bin-1.0_rc3 dev-java/forehead-1.0_beta5 The error I get: Exception in thread "main" java.lang.NoClassDefFoundError: com/werken/forehead/Forehead
It looks like MAVEN_HOME isn't set correctly. Online 154 in /usr/bin/maven it tries to search forehead in the maven directory (so yes a forehead dependancy isn't neccesary): -classpath "${MAVEN_HOME}/lib/forehead-${FOREHEAD_VERSION}.jar" \ but MAVEN_HOME is set to /usr for some reason after doing an: export MAVEN_HOME=/usr/share/maven everything worked fine
I've added a patch for /usr/bin/maven to properly detect MAVEN_HOME to CVS. Thanks for reporting.
