I think you have some typos in your e-mail
my.namesapce.test should be org.mynamespace.test to match
src/test/java/org/namespace/test/
Give the commands that you used to compile on each machine and the
output log
You might check in your settings.xml files on each machine to make sure
that they match.
Ron
On 06/11/2013 9:47 AM, Andrew Pennebaker 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
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
