maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rsand <>
Subject Plugin name is "idfc-maven-proguard-plugin" (was re: introducing maven-proguard-plugin)
Date Mon, 15 Jul 2013 18:34:35 GMT
Sorry everyone for the misleading subject line, it was unintentional. 


Sent from my iPhone

On Jul 15, 2013, at 2:01 PM, "Stephen Connolly" <> wrote:

> Please refrain from referring to your plugin as the maven ____ plugin.
> Maven and Apache Maven are trademarks of the Apache Foundation and as such
> their use requires some clarity.
> We (the Maven project) have sought guidance as to how others can use our
> mark and the guidance we got is that if the other work is clearly a
> separate work from Maven, eg "XYZ's ____ plugin for Maven" then that is
> something we can permit.
> The brief check of your site on my phone looks ok (not sure if you ack the
> marks though) but the email subject is not a good use.
> We have to demonstrate that we actively protect our marks when
> inappropriate use is brought to our attention... So ease don't refer to it
> as a "maven ____ plugin" again.
> Thank you for developing your plugin and growing our community, BTW
> On Monday, 15 July 2013, Richard Sand wrote:
>> Hi all,
>> I've published version 0.8 of my obfuscation plugin, which can be used to
>> invoke ProGuard to obfuscate Maven artifacts. It is a Maven3 plugin and
>> requires Java6. I've tried to integrate it as well as possible into the
>> maven world to minimize the amount of configuration needed for it to
>> automatically find the proper files to obfuscate and create a nice usable
>> output.
>> The plugin website is
>> I've opened a
>> ticket to create a Sonatype project for it, so it can be included in the
>> central repository, but for now if you want to try it out you can download
>> it from SourceForge directly:
>> The source code,
>> SVN,
>> tickets etc. can also be found there.
>> I've still got one major maven integration issue, and that's with adding
>> the
>> result of the obfuscator back into maven via attachArtifact. If you use the
>> plugin, leave the "attach" property as false (the default) and use the
>> resulting jar(s) from the obfuscator via maven assembly. I e-mailed the
>> list
>> about that issue a few days ago so if anyone has any insight into that I'd
>> appreciate any advice!
>> Anyway I hope someone finds this plugin helpful. Thanks!
>> Best regards,
>> Richard
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: <javascript:;>
>> For additional commands, e-mail:<javascript:;>
> -- 
> Sent from my phone

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message