[MECLIPSE-338] eclipse:eclipse behaves differently in multiproject setting vs. iterating single projects (when explicitly avoiding inter-project dependencies)

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.4
• Component/s: Core : Multi-projects
• Environment: Win XP Professional, Java 1.5_09, maven 2.0.6
• Assignee: Unassigned
• Reporter: Andreas Zielke
• Created: 30/Oct/07 07:54
• Updated: 15/Nov/07 18:02
• Resolved: 15/Nov/07 18:02

Description

I have a flat multiproject setting and would like to avoid project dependencies, to be closer to the production setting. (The motivation may be arguable, but anyway.) So I configured
{{
<eclipse.useProjectReferences>false</eclipse.useProjectReferences>
}}
in the master project pom.

When I call mvn eclipse:eclipse in the "child" projects, no inter-project dependencies are generated - this is behaviour I'd expected.
When I call mvn eclipse:eclipse in the "master" project, the eclipse files are generated, but interproject dependencies are inserted instead of jar dependencies.

I've created an minimal example to reproduce this behaviour. The archive contains three projects:
Master - the pom only project, driving the other two.
Base - the first child project with no project dependencies. (Could be common server/client-side code.)
Server_Base - the second child project with a dependency to Base.
After extracting the archive you can reproduce the error by doing the following:
1) Try running mvn eclipse:eclipse in Master,
2) backup the eclipse files in Server_Base
3) run mvn eclipse:clean eclipse:eclipse in Server_Base.
4) Compare the new eclipse project files with the previous ones.