[
http://jira.codehaus.org/browse/MNG-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128394#action_128394
]
Benjamin Bentmann commented on MNG-3481:
----------------------------------------
bq. Eclipse has its own compiler (JDT) that does things differently than Maven
Among others for this reason, I consider it a bad practice to have Maven and
Eclipse use the same output directory for class files as suggested by the
default configuration for the maven-eclipse-plugin and other IDE integrations
for M2.
> FAQ: My project compiles in Eclipse and not Maven. Why is Maven broken?
> -----------------------------------------------------------------------
>
> Key: MNG-3481
> URL: http://jira.codehaus.org/browse/MNG-3481
> Project: Maven 2
> Issue Type: Improvement
> Components: Documentation: Faqs
> Affects Versions: Documentation Deficit
> Reporter: Wayne Fay
>
> We see a fair number of emails on the Users list claiming "my project builds
> in Eclipse but not Maven". It would be nice to post something about this in
> the FAQ, perhaps along these lines:
> Q: My project compiles in Eclipse and not Maven. Why is Maven broken?
> A: Eclipse has its own compiler (JDT) that does things differently than Maven
> (which uses your JDK's javac). Try compiling your project with javac from the
> JDK and specifying your dependencies with -cp. If this works, then Maven
> should have no issues compiling it either.
> You can see more info in this (and other) threads:
> To: Maven Users List
> Subject: Re: package does not exit error with 3rd party jar dependency
> Date: Mon, 24 Mar 2008 16:13:08 +0100
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
