You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2008/02/20 01:00:28 UTC
[jira] Updated: (MPLUGIN-15) Support includes/excludes
[ http://jira.codehaus.org/browse/MPLUGIN-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MPLUGIN-15:
-----------------------------------
Description:
Support advanced scanner configuration (e.g. includes/excludes), just like the compiler plugin does. This allows to restrict the sources the plugin scans, rationale see compiler plugin.
This also would help working around QDOX not supporting JDK 1.5 (see [1] and [2]).
If this is wanted and somebody tells me the best way, I'll gladly implement it. I looked at the code and noticed a "brute force" approach would mean adding the scanner configuration to the plugin MOJO and propagating it through MojoScanner.populatePluginDescriptor and MojoDescriptorExtractor.execute (changing the intefaces). Does not sound like the best option... The next thing would be to add the configuration to PluginDescriptor (maybe other plugins might want to use this feature, too..). The third option would be to add it to some component manager that is available, but escaped me while looking at the code.
Any suggestions?
[1] MPLUGIN-1
[2] QDOX-94
was:
Support advanced scanner configuration (e.g. includes/excludes), just like the compiler plugin does. This allows to restrict the sources the plugin scans, rationale see compiler plugin.
This also would help working around QDOX not supporting JDK 1.5 (see [1] and [2]).
If this is wanted and somebody tells me the best way, I'll gladly implement it. I looked at the code and noticed a "brute force" approach would mean adding the scanner configuration to the plugin MOJO and propagating it through MojoScanner.populatePluginDescriptor and MojoDescriptorExtractor.execute (changing the intefaces). Does not sound like the best option... The next thing would be to add the configuration to PluginDescriptor (maybe other plugins might want to use this feature, too..). The third option would be to add it to some component manager that is available, but escaped me while looking at the code.
Any suggestions?
[1] http://jira.codehaus.org/browse/MPLUGIN-1
[2] http://jira.codehaus.org/browse/QDOX-94
> Support includes/excludes
> -------------------------
>
> Key: MPLUGIN-15
> URL: http://jira.codehaus.org/browse/MPLUGIN-15
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Reporter: Jochen Kuhnle
>
> Support advanced scanner configuration (e.g. includes/excludes), just like the compiler plugin does. This allows to restrict the sources the plugin scans, rationale see compiler plugin.
> This also would help working around QDOX not supporting JDK 1.5 (see [1] and [2]).
> If this is wanted and somebody tells me the best way, I'll gladly implement it. I looked at the code and noticed a "brute force" approach would mean adding the scanner configuration to the plugin MOJO and propagating it through MojoScanner.populatePluginDescriptor and MojoDescriptorExtractor.execute (changing the intefaces). Does not sound like the best option... The next thing would be to add the configuration to PluginDescriptor (maybe other plugins might want to use this feature, too..). The third option would be to add it to some component manager that is available, but escaped me while looking at the code.
> Any suggestions?
> [1] MPLUGIN-1
> [2] QDOX-94
--
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