Re: Resolving MDEP-98, 187, 194 and 354

[Ian Brandt]

Thanks Hervé!  I'm on Pacific time, 9 hours behind you.  I'll do my best to be 
available for e-mail from 6PM your time.  I'll also be in the #maven IRC 
channel on irc.codehaus.org as ianbrandt if that's easier.

Regards,

Ian

On Jul 31, 2012, at 10:30 PM, Hervé BOUTEMY wrote:

> I will take a look at it tonight, after work (Paris time :) )
> 
> I don't know if I will need more explanations or not, but if you can be 
> online 
> at this time to reply to mails, it can spped up our eventual discussions
> 
> Regards,
> 
> Hervé
> 
> Le mardi 31 juillet 2012 19:28:25 Ian Brandt a écrit :
>> Greetings,
>> 
>> I'm working on an m2e connector for the Maven Dependency Plugin:
>> 
>> https://github.com/ianbrandt/m2e-maven-dependency-plugin
>> 
>> The very first bug report filed against it appears to actually just be a
>> manifestation of the long outstanding MDEP-98/187/194/354:
>> 
>> http://jira.codehaus.org/browse/MDEP-98
>> http://jira.codehaus.org/browse/MDEP-187
>> http://jira.codehaus.org/browse/MDEP-194
>> http://jira.codehaus.org/browse/MDEP-354
>> 
>> There have been patches attached to these JIRA's over the years, the latest
>> of which I believe is on MDEP-194.  Correct me if I'm wrong, but I notice
>> no recent committer activity.
>> 
>> Is there anything I could do to help expedite the resolution of this bug? 
>> Would it help if I wrangled the patches into a pull request on the GitHub
>> mirror?  Are more test cases needed?
>> 
>> Thanks,
>> 
>> Ian
>> 
>> P.S. If anyone knows the answer to my last Maven Dependency Plugin related
>> question that would be great too:
>> 
>> <http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3CD6E6D74A-
>> 7454-4043-B2D2-E3232025CF47%40ianbrandt.com%3E>
>> - To
>> unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Resolving MDEP-98, 187, 194 and 354

[Ian Brandt]

Greetings,

I'm working on an m2e connector for the Maven Dependency Plugin:

https://github.com/ianbrandt/m2e-maven-dependency-plugin

The very first bug report filed against it appears to actually just be a 
manifestation of the long outstanding MDEP-98/187/194/354:

http://jira.codehaus.org/browse/MDEP-98
http://jira.codehaus.org/browse/MDEP-187
http://jira.codehaus.org/browse/MDEP-194
http://jira.codehaus.org/browse/MDEP-354

There have been patches attached to these JIRA's over the years, the latest of 
which I believe is on MDEP-194.  Correct me if I'm wrong, but I notice no 
recent committer activity.

Is there anything I could do to help expedite the resolution of this bug?  
Would it help if I wrangled the patches into a pull request on the GitHub 
mirror?  Are more test cases needed?

Thanks,

Ian

P.S. If anyone knows the answer to my last Maven Dependency Plugin related 
question that would be great too: 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Custom type converter for Mojo configuration?

[Ian Brandt]

I too would like to know if it is possible for plugins to define custom 
converters for  handling.

I notice the maven-toolchain-plugin seems to be doing something along these 
lines:

http://svn.apache.org/viewvc/maven/plugins/tags/maven-toolchains-plugin-1.0/src/main/resources/META-INF/plexus/components.xml?view=markup

http://svn.apache.org/viewvc/maven/plugins/tags/maven-toolchains-plugin-1.0/src/main/java/org/apache/maven/plugin/toolchain/ToolchainConverter.java?view=markup

Is this acceptable public API?

The Maven Dependency Plugin takes  and  as a comma 
separated list of patterns that map to String.  Most other Maven plugins seem 
to use a collection (e.g. String[]) and nested / elements.  
With a custom ConfigurationConverter the plugin could be extended to accept 
both formats:

one/**,two/**

...and...


one/**
two/**


This would maintain backwards compatibility, and be arguably more elegant than 
introducing new parameters such as /.  With the 
additional parameters you'd have to define what happens when both versions are 
present.  Would you throw an exception, ignore one, or merge them in some order 
of precedence? I'd think it better to just avoid the issue.

Ian


On Apr 18, 2012, at 12:33 AM, Xie Jilei wrote:

> (From: http://stackoverflow.com/questions/10188534/)
> 
> I need to use custom type, e.g., `LunarDate`, in my Mojo object:
> 
>class MyMojo extends AbstractMojo {
> 
>/** @parameter */
>LunarDate lunarDate;
> 
>}
> 
> And I want to configure the parameter in `` section in
> pom.xml.
> 
>
> 丁丑年二月初四
>
> 
> (The type `LunarDate` is just an example to illustrate the question)
> 
> I've already had the type converters, but how to enable them?


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org