Details
-
Type:
Task
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
This is really important for several reasons:
- I don't like to clutter my main plugin package with POJO classes. For the Cargo m2 plugin I have 7-8 POJO classes and I'd like to move them to a different package
- I need to reuse existing POJOs from another jar and it's just too stupid to have to duplicate all the code or write wrapper classes with only getter/setters.
I think the best solution would be to accept @implementation javadoc tags that would map a parameter to an implementation. This would need to work not only for Mojo classes but also for POJO classes being used for configuration.
Actually It would be even better to offer a mapping file for this. The reason is that I would like to reuse POJOs from an external jar but I don't want to add @implementation tags to the java of this external jar... At least it should be an option I think...