[ http://jira.codehaus.org/browse/MNG-1353?page=comments#action_49532 ]
Vincent Massol commented on MNG-1353: ------------------------------------- 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... > Allow creating POJO config classes anywhere without requiring the plugin user > to specify an implementation element > ------------------------------------------------------------------------------------------------------------------ > > Key: MNG-1353 > URL: http://jira.codehaus.org/browse/MNG-1353 > Project: Maven 2 > Type: Task > Components: maven-core > Versions: 2.0 > Reporter: Vincent Massol > Assignee: Jason van Zyl > > > 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 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
