You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Reşat SABIQ (JIRA)" <ji...@apache.org> on 2016/12/12 07:19:58 UTC
[jira] [Updated] (IVY-1553) PGP signing during publication
shouldn't require bouncy castle dependencies to be in .ant/lib or forking
another java process with classpath explicitly configured to contain bouncy
castle modules
[ https://issues.apache.org/jira/browse/IVY-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reşat SABIQ updated IVY-1553:
-----------------------------
Summary: PGP signing during publication shouldn't require bouncy castle dependencies to be in .ant/lib or forking another java process with classpath explicitly configured to contain bouncy castle modules (was: PGP signing during publication shouldn't require bouncy castle dependencies to be in .ant/lib)
> PGP signing during publication shouldn't require bouncy castle dependencies to be in .ant/lib or forking another java process with classpath explicitly configured to contain bouncy castle modules
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: IVY-1553
> URL: https://issues.apache.org/jira/browse/IVY-1553
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.4.0
> Reporter: Reşat SABIQ
> Labels: pgp
>
> With
> <signers>
> <pgp name="default-sig" keyId="${pgp.key}" password="${pgp.password}"/>
> </signers>
> in ivysettings.xml,
> ivy kept throwing CNFE until i put these dependencies in .ant/lib:
> <dependency org="org.bouncycastle" name="bcpg-jdk15on" rev="1.49" conf="default"/>
> <dependency org="org.bouncycastle" name="bcprov-jdk15on" rev="1.49" conf="default"/>
> I ended up putting the following comment in ivy.xml:
> <!-- First 2 currently must be in .ant/lib (pgp signer didn't work via dependency or ivycache manipulation, etc). -->
> P.S. I believe this issue is ongoing since 2012/13.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)