Maven
  1. Maven
  2. MNG-5343

Allow the use of JSR330 annotation in Maven extensions and plugins

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.0-alpha-1
    • Component/s: None
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.

      This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.

      [1]: http://sonatype.github.com/sisu-maven-plugin/

        Issue Links

          Activity

          Hide
          Herve Boutemy added a comment - - edited

          done in r1380105

          JSR-330 is available in core since 3.0-beta-3 (see MNG-4749), but since it wasn't exported to plugins or extensions, it couldn't be used outside core.

          Notice that Guice API isn't exposed, even in Maven 3.1, so it's still available only inside Maven core, but not in plugins or extensions

          Show
          Herve Boutemy added a comment - - edited done in r1380105 JSR-330 is available in core since 3.0-beta-3 (see MNG-4749 ), but since it wasn't exported to plugins or extensions, it couldn't be used outside core. Notice that Guice API isn't exposed, even in Maven 3.1, so it's still available only inside Maven core, but not in plugins or extensions

            People

            • Assignee:
              Jason van Zyl
              Reporter:
              Jason van Zyl
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: