uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Klügl <peter.klu...@averbis.com>
Subject Re: signing Jars
Date Wed, 27 Jan 2016 10:34:29 GMT
Here are some first observations:

- the ant task for the soap service should be called right before
"Compress plugin Jars using pack200" (parent-pom: maven-antrun-plugin ->
- in case the features are need to be signed, they have also to be
copied to ${toBePacked} or something similar
- the ant task should be called on all jars in that folder (or also an
additional one for the features)

Some consequences:
- we would call the fee based signing service each time we build the
update site with the apache-release profile. I actually do this
sometimes to build snapshot update sites (a different solution is surely
possible). However, we do this also for *every* release candidate. (For
ruta, that would have been three times just because of some bugs). I do
not have a good feeling about that. Maybe it's better to sign the
bundles manually only for accepted release candidates (with additional
- in order to integrate the ant task, we need to change the parent pom.
Meaning we need to do a parent pom release. Meaning we need to update
the parent pom version in our update site. Meaning we have to cancel
both release candidates.

Any opinions?



Am 27.01.2016 um 10:24 schrieb Peter Klügl:
> Marshall, are you able to access the test system?
> https://test-securesigning.websecurity.symantec.com/csportal/
> Am 27.01.2016 um 10:17 schrieb Peter Klügl:
>> Am 26.01.2016 um 22:09 schrieb Marshall Schor:
>>> On 1/26/2016 5:20 AM, Peter Klügl wrote:
>>>> ...
>>>> ect all this info...
>>>> Should we just copy the implementation to some of our (build) projects?
>>> It would be good to automate this of course.  I think that would take using the
>>> SOAP interface with the Ant script done by the Apache TomCat project.
>>> However, some basic info on our web site for posterity once we forget how this
>>> all works would be good - pointers to other pages that describe how it all
>>> works, how to use the test stuff, etc.
>>> -Marshall
>> Yes, I will create/extend a page once it is up and running.
>> Best,
>> Peter

View raw message