[ http://jira.codehaus.org/browse/MPLUGIN-22?page=all ]

Jochen Kuhnle updated MPLUGIN-22:
---------------------------------

    Attachment: MPLUGIN-22-maven-plugin-tools-api.patch

Updated patch. Older one is obsolete.

> Allow specification of mojo extractors to be used
> -------------------------------------------------
>
>                 Key: MPLUGIN-22
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-22
>             Project: Maven 2.x Plugin Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.2
>            Reporter: Jochen Kuhnle
>             Fix For: 2.2
>
>         Attachments: MPLUGIN-22-maven-plugin-plugin.patch, 
> MPLUGIN-22-maven-plugin-plugin.patch, 
> MPLUGIN-22-maven-plugin-tools-api.patch, 
> MPLUGIN-22-maven-plugin-tools-api.patch
>
>
> With the attached patch, plugin plugin configuration is extended with a 
> section "extractors". This allows the user to specify which descripters are 
> to be used in the project.
> The main reason for this patch are the JDK 1.5 problems with the Java 
> extractor, which can be turned off with this patch. Also, there are projects 
> that provide an extractor that uses Java 5 annotations [1], so there may be 
> two kinds of extractors for the same language in the future. With this, the 
> user should decide which one to use.
> The patch changes maven-plugin-plugin and maven-tools-api. It does not change 
> the default behaviour (use all extractors). Unit tests are included.
> Example:
> <plugin>
>   <artifactId>maven-plugin-plugin</artifactId>
>   <version>2.2-SNAPSHOT</version>
>   <configuration>
>     <!-- Use all extractors -->
>     <extractors/>
>     <!-- Use no extractors -->
>     <extractors>
>       <extractor/>
>     </extractors>
>     <!-- Use only bsh extractor -->
>     <extractors>
>       <extractor>bsh</extractor>
>     </extractors>
>   </configuration>
> </plugin>
> [1] http://sourceforge.net/projects/mvn-anno-mojo

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to