Uploaded image for project: 'Maven Plugin Tools'
  1. Maven Plugin Tools
  2. MPLUGIN-257

deprecate classical Maven objects as components

    XMLWordPrintableJSON

Details

    • Wish
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.2
    • 3.3
    • None
    • None

    Description

      such component annotations added in MPLUGIN-204 were a bad idea, because they cause confusion with Plexus components

      it's better to remove the feature and add examples in documentation:

      @Parameter( defaultValue="${session}", readonly=true )
private MavenSession session;

@Parameter( defaultValue="${project}", readonly=true )
private MavenProject project;

@Parameter( defaultValue="${mojo}", readonly=true )
private MojoExecution mojo;

@Parameter( defaultValue="${plugin}", readonly=true )
private PluginDescriptor plugin;

@Parameter( defaultValue="${settings}", readonly=true )
private Settings settings;

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MPLUGIN-266 Incorrect warning comment about deprecated @component usage for maven objects

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MPLUGIN-270 Deprecation of classical Maven objects as components is broken when using Javadoc tags

          • Major - Major loss of function.
          • Closed
          supercedes

          New Feature - A new feature of the product, which has yet to be developed. MPLUGIN-204 recognize classical Maven objects as components

          • Major - Major loss of function.
          • Closed

          Activity

            People

              hboutemy Herve Boutemy
              hboutemy Herve Boutemy
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: