[ 
https://issues.apache.org/jira/browse/SM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff MAURY updated SM-2369:
---------------------------
    Description: 
I'm using some of the bundles under the org.apache.servicemix.bundles groupId 
in our Eclipse based product. I noticed that some of them (at least this is 
true for org.apache.servicemix.bundles.bcpg-jdk15on/1.50_1) are signed with an 
expired certificate (2012) that may cause users to be troubled during 
installation/update
I would prefer to have it not signed at all than signed with an expired 
certificate.

  was:I'm using some of the bundles under the org.apache.servicemix.bundles 
groupId in our Eclipse based product. I noticed that some of them (at least 
this is true for org.apache.servicemix.bundles.bcpg-jdk15on/1.50_1) are signed 
with an expired certificate (2012) that may cause users to be troubled during 
installation/update


> Common bundles under org.apache.servicemix.bundles signed with expired 
> certificate
> ----------------------------------------------------------------------------------
>
>                 Key: SM-2369
>                 URL: https://issues.apache.org/jira/browse/SM-2369
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: Jeff MAURY
>
> I'm using some of the bundles under the org.apache.servicemix.bundles groupId 
> in our Eclipse based product. I noticed that some of them (at least this is 
> true for org.apache.servicemix.bundles.bcpg-jdk15on/1.50_1) are signed with 
> an expired certificate (2012) that may cause users to be troubled during 
> installation/update
> I would prefer to have it not signed at all than signed with an expired 
> certificate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to