Actually, the problem has more to do with a mixed up environment. I'm not sure I would call it a bug, but it was a bit confusing:
charm% env | grep JAVA JAVA_HOME=/openpkg/libexec/java-jdk15 JAVA_PLATFORM=sun-jdk-1.5.0 charm% unset JAVA_PLATFORM charm% mvn.orig /openpkg/bin/java:ERROR: invalid JAVA_PLATFORM: "sun-jdk" charm% Now that I have openpkg fully merged into my environment, this doesn't happen. But before, when I was using /openpkg/bin/mvn with my normal environment, which just had JAVA_HOME set, I would get this error. It's a little strange because this would only happen within maven. If you run java directly (no args) it doesn't complain. I'll try to take a closer look when I get a chance. -Dave On Thu, Nov 13, 2008 at 1:57 PM, Ralf S. Engelschall <[EMAIL PROTECTED]>wrote: > On Thu, Nov 13, 2008, David Stenglein wrote: > > > The mvn/maven.sh seems to be based on the new java infrastructure, but it > seems > > to have a problem. > > > > The line at the beginning: > > export JAVA_PLATFORM="sun-jdk" > > > > seems to throw things off. Should this just be removed? > > Sorry, can you be more specific: what do you mean by "throw things off"? > The JAVA_PLATFORM variable just says that the Java has to be a JDK (and > not GCJ, etc) because (as I can remember) that Maven didn't work with > GCJ. What does break for you? > > Ralf S. Engelschall > [EMAIL PROTECTED] > www.engelschall.com > > ______________________________________________________________________ > OpenPKG http://openpkg.org > User Communication List openpkg-users@openpkg.org >
