+1

> On Jan 24, 2018, at 4:05 PM, Gary Gregory <[email protected]> wrote:
> 
> +1
> 
> Gary
> 
>> On Wed, Jan 24, 2018 at 1:35 AM, Benedikt Ritter <[email protected]> wrote:
>> 
>> Hello Mark,
>> 
>> +1 In my opinion this is exactly what Commons should be doing.
>> 
>> Regards,
>> Benedikt
>> 
>> Mark Thomas <[email protected]> schrieb am Di., 23. Jan. 2018 um 07:34 Uhr:
>> 
>>> All,
>>> 
>>> As you may know, the ASF has been using a code signing service for a
>>> number of years provided by Symantec. We use it to sign Commons Daemon
>>> Windows binaries.
>>> 
>>> The code signing service has a web based GUI and a SOAP based API.
>>> Tomcat has written an Ant task to use the SOAP API and Sling has taken
>>> this used and used it as the basis for a Maven plug-in.
>>> 
>>> Currently, the Ant task is hosted within the Tomcat codebase and the
>>> Maven plug-in within Sling. Both communities would like to move this to
>>> a better home where it can more easily be re-used by other Apache
>>> projects and other organisations using Symantec's code signing service.
>>> 
>>> After some thought and discussion, we (Robert Munteanu and I) would like
>>> to propose this code signing component as a new component at Commons.
>>> Our reasons for this are as follows:
>>> 
>>> - The code is written in Java
>>> - It is a relatively small component
>>> - It is a utility likely to be of interest to multiple Apache projects
>>> - If it is going to be re-used across multiple projects, it needs to be
>>>  formally released and that requires a PMC
>>> 
>>> If accepted the plan would be:
>>> - commit the original Tomcat code for the Ant task
>>> - refactor it to allow re-use of code common to the Ant task and Maven
>>>  plug-in
>>> - add the Maven plug-in
>>> - release it as a single JAR that provided both the Ant task and the
>>>  Maven plug-in
>>> - Ongoing review and maintenance (there are a couple of areas that could
>>>  benefit from some improvement)
>>> 
>>> Thoughts? Comments?
>>> 
>>> Mark
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>> 
>>> 
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to