You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Richard Sand <rs...@idfconnect.com> on 2013/07/15 19:09:25 UTC
introducing maven-proguard-plugin
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
http://mavenproguard.sourceforge.net/project-summary.html. 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:
https://sourceforge.net/projects/mavenproguard/files/. 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: introducing maven-proguard-plugin
Posted by Richard Sand <rs...@idfconnect.com>.
Hi Alejandro - you're right. Actually I didn't put the right name in the
subject line! The actual artifact ID is "idfc-proguard-maven-plugin".
Best regards,
Richard
-----Original Message-----
From: Alejandro.Endo@miranda.com [mailto:Alejandro.Endo@miranda.com]
Sent: Monday, July 15, 2013 1:38 PM
To: Maven Users List
Subject: Re: introducing maven-proguard-plugin
if i'm not mistaken, maven-*-plugin is reserved for plugins developed by the
maven team, so you will probably be asked to rename your plugin
I can't find a reference to this claim, hence why so many people unknowingly
violate this convention. I wish it was mentioned in all the main
plugin-howto's
Hopefully someone else will complement this info
Alejandro Endo | Software Designer/Concepteur de logiciels
From: "Richard Sand" <rs...@idfconnect.com>
To: "'Maven Users List'" <us...@maven.apache.org>,
Date: 2013-07-15 01:09 PM
Subject: introducing maven-proguard-plugin
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
http://mavenproguard.sourceforge.net/project-summary.html. 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:
https://sourceforge.net/projects/mavenproguard/files/. 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
DISCLAIMER:
Privileged and/or Confidential information may be contained in this message.
If you are not the addressee of this message, you may not copy, use or
deliver this message to anyone. In such event, you should destroy the
message and kindly notify the sender by reply e-mail. It is understood that
opinions or conclusions that do not relate to the official business of the
company are neither given nor endorsed by the company.
Thank You.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: introducing maven-proguard-plugin
Posted by Al...@miranda.com.
if i'm not mistaken, maven-*-plugin is reserved for plugins developed by
the maven team, so you will probably be asked to rename your plugin
I can't find a reference to this claim, hence why so many people
unknowingly violate this convention. I wish it was mentioned in all the
main plugin-howto's
Hopefully someone else will complement this info
Alejandro Endo | Software Designer/Concepteur de logiciels
From: "Richard Sand" <rs...@idfconnect.com>
To: "'Maven Users List'" <us...@maven.apache.org>,
Date: 2013-07-15 01:09 PM
Subject: introducing maven-proguard-plugin
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
http://mavenproguard.sourceforge.net/project-summary.html. 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:
https://sourceforge.net/projects/mavenproguard/files/. 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Plugin name is "idfc-maven-proguard-plugin" (was re: introducing maven-proguard-plugin)
Posted by Stephen Connolly <st...@gmail.com>.
Thank you very much
On Tuesday, 16 July 2013, Richard Sand wrote:
> Hi Stephen - ok I made those changes. The site index.html has a prominent
> trademarks acknowledgement, and the license url now points to the plain
> text
> version.
>
> For usage, if you click on the Wiki on the sourceforge page it gives usage
> and an example pom.xml snippet. The link is here:
> https://sourceforge.net/p/mavenproguard/wiki/Home/. I added links to the
> sourceforge resources to the main site as well for convenience.
>
> The plugin API seems pretty straightforward to use. I think the #1 priority
> should be filling in all of the javadocs so that developers can understand
> the API. Most of the javadocs had no comments so it was problematic to
> figure out the right techniques to do things in the proper maven way. I
> think with this API its easy for plugin developers to go astray and perform
> activities that have negative downstream consequences to other plugins.
>
> Best regards,
>
> Richard
>
>
>
>
>
>
>
> -----Original Message-----
> From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com<javascript:;>
> ]
> Sent: Monday, July 15, 2013 4:26 PM
> To: Maven Users List
> Subject: Re: Plugin name is "idfc-maven-proguard-plugin" (was re:
> introducing maven-proguard-plugin)
>
> A couple of points:
>
> 1. You do not ACK the Apache marks: Apache, Apache Maven and Maven... Just
> stick it down the footer on at least the index page
>
> 2. You have linked to the HTML version of the GPL license, you should link
> to a text/plain version or the project license report gets fubar
>
> 3. Some examples of how to use are always welcomed by users
>
> Other than that, it would be great if you could give some feedback as to
> what we need to do in our docs to make developing plugins easier
>
> - Stephen
>
> On Monday, 15 July 2013, rsand wrote:
>
> > Sorry everyone for the misleading subject line, it was unintentional.
> >
> > -Richard
> >
> > Sent from my iPhone
> >
> > On Jul 15, 2013, at 2:01 PM, "Stephen Connolly" <
> > stephen.alan.connolly@gmail.com <javascript:;> <javascript:;>> 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
> > >> http://mavenproguard.sourceforge.net/project-summary.html. 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:
> > >> https://sourceforge.net/projects/mavenproguard/files/. 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:
> > >> users-unsubscribe@maven.apache.org <javascript:;>
> <javascript:;><javascript:;>
> > >> For additional commands, e-mail:
> > >> users-help@maven.apache.org <javascript:;><javascript:;>
> > <javascript:;>
> > >
> > > --
> > > Sent from my phone
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org<javascript:;>
> > <javascript:;> For additional commands, e-mail:
> > users-help@maven.apache.org <javascript:;><javascript:;>
> >
> >
>
> --
> Sent from my phone
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: users-help@maven.apache.org<javascript:;>
>
>
--
Sent from my phone
Re: Plugin name is "idfc-maven-proguard-plugin" (was re: introducing
maven-proguard-plugin)
Posted by "Mark H. Wood" <mw...@IUPUI.Edu>.
On Mon, Jul 15, 2013 at 11:36:19PM -0400, Richard Sand wrote:
[snip]
> The plugin API seems pretty straightforward to use. I think the #1 priority
> should be filling in all of the javadocs so that developers can understand
> the API. Most of the javadocs had no comments so it was problematic to
> figure out the right techniques to do things in the proper maven way. I
> think with this API its easy for plugin developers to go astray and perform
> activities that have negative downstream consequences to other plugins.
I'm sure that patches would be welcome, if you care to jot down what
you have learned as a start on improving the javadocs.
--
Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu
Machines should not be friendly. Machines should be obedient.
RE: Plugin name is "idfc-maven-proguard-plugin" (was re: introducing maven-proguard-plugin)
Posted by Richard Sand <rs...@idfconnect.com>.
Hi Stephen - ok I made those changes. The site index.html has a prominent
trademarks acknowledgement, and the license url now points to the plain text
version.
For usage, if you click on the Wiki on the sourceforge page it gives usage
and an example pom.xml snippet. The link is here:
https://sourceforge.net/p/mavenproguard/wiki/Home/. I added links to the
sourceforge resources to the main site as well for convenience.
The plugin API seems pretty straightforward to use. I think the #1 priority
should be filling in all of the javadocs so that developers can understand
the API. Most of the javadocs had no comments so it was problematic to
figure out the right techniques to do things in the proper maven way. I
think with this API its easy for plugin developers to go astray and perform
activities that have negative downstream consequences to other plugins.
Best regards,
Richard
-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
Sent: Monday, July 15, 2013 4:26 PM
To: Maven Users List
Subject: Re: Plugin name is "idfc-maven-proguard-plugin" (was re:
introducing maven-proguard-plugin)
A couple of points:
1. You do not ACK the Apache marks: Apache, Apache Maven and Maven... Just
stick it down the footer on at least the index page
2. You have linked to the HTML version of the GPL license, you should link
to a text/plain version or the project license report gets fubar
3. Some examples of how to use are always welcomed by users
Other than that, it would be great if you could give some feedback as to
what we need to do in our docs to make developing plugins easier
- Stephen
On Monday, 15 July 2013, rsand wrote:
> Sorry everyone for the misleading subject line, it was unintentional.
>
> -Richard
>
> Sent from my iPhone
>
> On Jul 15, 2013, at 2:01 PM, "Stephen Connolly" <
> stephen.alan.connolly@gmail.com <javascript:;>> 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
> >> http://mavenproguard.sourceforge.net/project-summary.html. 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:
> >> https://sourceforge.net/projects/mavenproguard/files/. 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:
> >> users-unsubscribe@maven.apache.org<javascript:;><javascript:;>
> >> For additional commands, e-mail:
> >> users-help@maven.apache.org<javascript:;>
> <javascript:;>
> >
> > --
> > Sent from my phone
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> <javascript:;> For additional commands, e-mail:
> users-help@maven.apache.org<javascript:;>
>
>
--
Sent from my phone
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Plugin name is "idfc-maven-proguard-plugin" (was re: introducing maven-proguard-plugin)
Posted by Stephen Connolly <st...@gmail.com>.
A couple of points:
1. You do not ACK the Apache marks: Apache, Apache Maven and Maven... Just
stick it down the footer on at least the index page
2. You have linked to the HTML version of the GPL license, you should link
to a text/plain version or the project license report gets fubar
3. Some examples of how to use are always welcomed by users
Other than that, it would be great if you could give some feedback as to
what we need to do in our docs to make developing plugins easier
- Stephen
On Monday, 15 July 2013, rsand wrote:
> Sorry everyone for the misleading subject line, it was unintentional.
>
> -Richard
>
> Sent from my iPhone
>
> On Jul 15, 2013, at 2:01 PM, "Stephen Connolly" <
> stephen.alan.connolly@gmail.com <javascript:;>> 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
> >> http://mavenproguard.sourceforge.net/project-summary.html. 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:
> >> https://sourceforge.net/projects/mavenproguard/files/. 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: users-unsubscribe@maven.apache.org<javascript:;><javascript:;>
> >> For additional commands, e-mail: users-help@maven.apache.org<javascript:;>
> <javascript:;>
> >
> > --
> > Sent from my phone
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: users-help@maven.apache.org<javascript:;>
>
>
--
Sent from my phone
Plugin name is "idfc-maven-proguard-plugin" (was re: introducing maven-proguard-plugin)
Posted by rsand <rs...@idfconnect.com>.
Sorry everyone for the misleading subject line, it was unintentional.
-Richard
Sent from my iPhone
On Jul 15, 2013, at 2:01 PM, "Stephen Connolly" <st...@gmail.com> 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
>> http://mavenproguard.sourceforge.net/project-summary.html. 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:
>> https://sourceforge.net/projects/mavenproguard/files/. 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: users-unsubscribe@maven.apache.org <javascript:;>
>> For additional commands, e-mail: users-help@maven.apache.org<javascript:;>
>
> --
> Sent from my phone
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: introducing maven-proguard-plugin
Posted by Stephen Connolly <st...@gmail.com>.
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
> http://mavenproguard.sourceforge.net/project-summary.html. 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:
> https://sourceforge.net/projects/mavenproguard/files/. 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: users-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: users-help@maven.apache.org<javascript:;>
>
>
--
Sent from my phone