Be able to exclude specific projects from having Eclipse .project/.classpath generated for them

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

We have a large tree of projects in Maven, and one or two leaf projects that just can NOT be built in Eclipse.
We do prefer to have the direct project dependencies, but we can't have them for these few "bad" leaf projects (that almost everybody depends on).
We'd prefer to be able to specify these projects to just NOT be handled by the Eclipse plugin, and all dependencies on them should refer to the repository .jar files.

Issue Links

is duplicated by

New Feature - A new feature of the product, which has yet to be developed. MECLIPSE-158 Add the ability to selectively treat a referenced project as a local repository file

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Kenney Westerhof added a comment -

You can run mvn -r -Dmaven.reactor.excludes=path/to/leaf1/pom.xml,path/to/leaf2/pom.xml

Show
Kenney Westerhof added a comment - You can run mvn -r -Dmaven.reactor.excludes=path/to/leaf1/pom.xml,path/to/leaf2/pom.xml
Hide
Permalink
Kenney Westerhof added a comment -

the reactor excludes is the proper solution as it only affects imports in eclipse. I'd hate to see custom
'skip this' configurations in POM files for all IDE's and their specific bugs.

Show
Kenney Westerhof added a comment - the reactor excludes is the proper solution as it only affects imports in eclipse. I'd hate to see custom 'skip this' configurations in POM files for all IDE's and their specific bugs.

People

  • Assignee:
    Unassigned
    Reporter:
    John Lussmyer
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: