maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: Namespace issues in Maven projects between Mac and Windows
Date Wed, 06 Nov 2013 15:09:19 GMT
Unless you have configured the maven-compiler-plugin to use a compiler
other than the default, the JDK's javac is used. So I would assume it's due
to Apple's JDK accepting this mismatch while Oracle's JDK doesn't.

/Anders


On Wed, Nov 6, 2013 at 3:47 PM, Andrew Pennebaker <apennebaker@42six.com>wrote:

> On my machine, I have a Java file with a different stated package name (
> my.namespace.test) than the file's directory structure would indicate (
> src/test/java/org/namespace/test/). On my machine, "mvn compile" and "mvn
> test" still work without issue or warning.
>
> But on my friend's machine, Maven complained during compilation that it
> could not find the Java file. By moving the file into a directory structure
> matching its stated package, we got "mvn compile" and "mvn test" to work on
> his machine as well. I'm curious why our "mvn compile"s are behaving
> differently.
>
> Our specs:
>
> * My Maven 3.1.1, from Homebrew, with Apple JavaSE JDK 6, on Mac OS X 10.9
> Mavericks x64
> * Friend's Maven 3.0.5, from Chocolatey, with Oracle JavaSE JDK6, on
> Windows 7 x64
>
> --
> Cheers,
>
> Andrew Pennebaker
> apennebaker@42six.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message