This one time, at band camp, [EMAIL PROTECTED] said:
>And that you have a writable $MAVEN_HOME/plugins directory?
Thanks, Dion, that was it. Now I feel like a bone head ;-). It seems
to me that if Maven performed a quick permissions check of the
directories that the error reporting could be improved to help the
user identify this problem.
After I got Maven to work, however, I received the following segfault:
/opt/maven/bin/maven: line 114: 18613 Segmentation fault $JAVACMD $MAVEN_OPTS
-classpath ${MAVEN_HOME}/lib/forehead-${FOREHEAD_VERSION}.jar
-Dforehead.conf.file=${MAVEN_HOME}/bin/forehead.conf -Dtools.jar=$TOOLS_JAR
-Dmaven.home=${MAVEN_HOME} $MAIN_CLASS $@
This occurred while using J2SE 1.4.1_01-b01. Only because I experienced
the same problem recently with Scarab did I know how to rememdy
this. By switching back to Java 1.2x, the segfault disappeared.
Thanks again, Dion.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
