[MNG-1353] Allow creating POJO config classes anywhere without requiring the plugin user to specify an implementation element

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0
• Component/s: Plugins and Lifecycle
• Assignee: Jason van Zyl
• Reporter: Vincent Massol
• Created: 28/Oct/05 05:02
• Updated: 07/Apr/15 12:25
• Resolved: 15/Jun/14 15:13

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.