[
https://jira.codehaus.org/browse/MNG-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348087#comment-348087
]
Jason van Zyl commented on MNG-1353:
------------------------------------
After 10 years, I don't think we're going to do this :-)
> Allow creating POJO config classes anywhere without requiring the plugin user
> to specify an implementation element
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-1353
> URL: https://jira.codehaus.org/browse/MNG-1353
> Project: Maven 2 & 3
> Issue Type: Task
> Components: Plugins and Lifecycle
> Affects Versions: 2.0
> Reporter: Vincent Massol
> Assignee: Jason van Zyl
> Fix For: Issues to be reviewed for 3.x
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
