Uploaded image for project: 'Maven Eclipse Plugin (RETIRED)'
  1. Maven Eclipse Plugin (RETIRED)
  2. MECLIPSE-147

Dependencies that are inherited from subprojects that are specified in Require-Bundle or Import-Package should be excluded

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • PDE support
    • None

    Description

      Project A depends on Project B

      Project A adds Project B in as a "Require-Bundle".

      Project B exports its dependencies.

      Project A therefore does not want to link resources in .project and .classpath. It already inherits them by depending on Project B.

      I've attached a patch which is, apologies, completely specific to my project. What I'm trying to do in the patch is to not just exclude any reactor projects but also exclude any dependencies that originate from reactor dependencies. I wanted to take the "node" variable and ask whether its parent was a reactor project. However, I don't think the ResolutionNode API allows me to traverse up the hierarchy towards the parent.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            daveboden David Boden
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment