Uploaded image for project: 'Maven Compiler Plugin'
  1. Maven Compiler Plugin
  2. MCOMPILER-203

Allow compiler-plugin to specify annotation processor dependencies

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.3.2, 3.1
    • 3.5
    • None
    • Java 6+

    Description

      Right now the status quo for annotation processor artifacts requires one of two actions:

      1. Use an external plugin for annotation processing
      2. Put the annotation processor in as a dependency with provided scope

      The former is suboptimal because the external plugins are clunky and ill-supported, and inflexible/hard to use. The latter is suboptimal because it is often the case that you do not want to leak annotation processor classes on to the application class path.

      It should be possible to add annotation processor dependency artifacts to the compiler plugin configuration such that they are recognized by the annotation processing search algorithm of the compiler, but they do not actually appear on the compilation class path. Ideally they would also be isolated from one another (dependency graphs and all), but that's more of a "nice to have".

      Attachments

        Issue Links

        Activity

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

          People

            agudian Andreas Gudian
            dmlloyd David M. Lloyd
            Votes:
            2 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment