Rafal Krzewski wrote:
> [EMAIL PROTECTED] wrote:
>
>>I don't know what to do here. Tell me your platform, jdk and vendor? Maybe
>>it's the unix script, as I don't run it often, but those classes are in
>>the endorsed dir jars. And if the JDK can't see them, then there's either
>>something wrong with the JDK or the launcher script.
OK I tracked this one down. The problem was that I was running different
bin/maven script than the one in $MAVEN_HOME. I don't know what was the
nature of mismatch but I'm not sure if I really care.
For now I've replaced the symlink /usr/local/bin/maven ->
/usr/local/maven/bin/maven with a simple wrapper that you can find
attached to the message.
It checks that MAVEN_HOME is set and valid and then launches the real
bin/maven script contained in that directory.
Next week I'll try to come up with a patch for the maven script itself
that will prevent such things from happening.
Thanks for assistance anyways!
Rafal
#!/bin/sh
if [ -z "$MAVEN_HOME" ]; then
echo MAVEN_HOME is not defined
else
if [ -d $MAVEN_HOME ]; then
if [ -x $MAVEN_HOME ]; then
$MAVEN_HOME/bin/maven $*
else
echo $MAVEN_HOME/bin/maven does not exist or is not executable
fi
else
echo $MAVEN_HOME does not exist or is not a direcotry
fi
fi
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
