This is a bug/limitation of eclipse java tooling (aka JDT). Each workspace project has only one classpath and it is not possible to properly isolate main and test classes and dependencies.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=376616 and couple of jdt enhancement requests it depends on. -- Regards, Igor On 2013-03-26 6:50 AM, Tamas Janovics wrote:
Hello, I have a project with a a source folder (src/main/java) and a test source folder (src/test/java) as on maven's http://www.youtube.com/watch?feature=player_embedded&v=reIHx1ozxYk site is given. Now all classes from src/main/java have access to src/test/java (public) classes and all classes from src/test/java have access to src/main/java public classes. In progress of the implementation I can access to the main package from the src/test/java, but the maven ignore the test folder and it makes Errors in mvn package if anything is used from src/test/java folder in the src/main/java. How to configure the m2e or the src/main/java and src/test/java source folders to get the same configuration/isolation in eclipse as maven has? I think the following configuration in eclipse: - src/main/java has no access to src/test/java - src/test/java has access to src/main/java Thanks. Tamas _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
