commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: Commons plugins
Date Thu, 20 Jun 2013 03:32:14 GMT
Thank you for taking the initiative and doing this work Sebb.

Gary

On Jun 19, 2013, at 19:45, sebb <sebbaz@gmail.com> wrote:

> I've been developing some Maven plugins in the Sandbox, and I now
> propose to move them to Commons proper.
>
> commons-javadocfix-plugin
> ====================
> Runs the Oracle JavadocFixTool as a Maven plugin or a Java
> command-line application.
> The tool was released by Oracle recently in order to fix up Javadoc
> files that have some javascript which is vulnerable to attack.
> The original Oracle tool has some bugs (e.g. did not delete temporary
> saved copy of original file on Windows) which have been fixed.
>
> Ideally the Maven aspect would be fixed by an update to the Maven
> Javadoc plugin, but that might take a while to implement.
> I've raised http://jira.codehaus.org/browse/MJAVADOC-370
>
> In the meantime it might be necessary to use it to implement the
> fuctionality ourselves.
>
> commons-digest-plugin
> =================
> This is a simple plugin that generates MD5 and SHA1 hashes for files
> in a directory.
> This is intended for use in simplifying the deployment of tarballs
> (source and binary packages).
>
> commons-gpg-plugin
> ===============
> Like the Digest plugin, but creates sigs for files in a directory.
> The Maven version of the plugin cannot sign arbitrary files, but I've
> raised an enancement request to add this functionality, so hopefully
> the Commons plugin won't be needed for too long.
>
> commons-staging-plugin
> ==================
> This handles the rest of the functions needed to deploy tarballs
> separately from Nexus.
> The main functions are upload of tarballs to the dist/dev directory
> and later release by moving the tarballs from dist/dev to dist/release
>
> I'm not entirely happy with the name "Staging", as it is only part of
> the function. The name can be changed if necessary.
>
> I intend to move the plugins tomorrow sometime unless there are any objections.
>
> The next stage will be to get some people to test them to see if they
> need to be improved, and then hopefully release them so they can start
> being used.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message