Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: API, Plugin Plugin
-
Labels:None
-
Number of attachments :
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?
Issue Links
- depends upon
-
MPLUGIN-1
Maven fails while developing plugin with 1.5 compliant sources
-
-
MPLUGIN-110
Make easier to pass parameters into MojoDescriptorExtractors
-
Activity
| 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] http://jira.codehaus.org/browse/MPLUGIN-1 [2] http://jira.codehaus.org/browse/QDOX-94 |
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] [2] |
| Link |
This issue depends upon |
| Component/s | Plugin Plugin [ 13021 ] | |
| Component/s | API [ 13118 ] |
| Attachment | trunk.patch [ 59380 ] |
Maven plugin include/excludes configuration