You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Greg Trasuk (JIRA)" <ji...@apache.org> on 2013/08/08 06:06:47 UTC
[jira] [Resolved] (RIVER-424) jsk-policy.jar is not published to
Maven Central
[ https://issues.apache.org/jira/browse/RIVER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Trasuk resolved RIVER-424.
-------------------------------
Resolution: Fixed
Fix Version/s: River_2.2.2
Fixed in 2.2 branch revision 1511568.
Added jsk-policy to poms and deploy_river.groovy script.
> jsk-policy.jar is not published to Maven Central
> ------------------------------------------------
>
> Key: RIVER-424
> URL: https://issues.apache.org/jira/browse/RIVER-424
> Project: River
> Issue Type: Bug
> Components: build
> Affects Versions: River_2.2.1
> Reporter: Greg Trasuk
> Assignee: Greg Trasuk
> Fix For: River_2.2.2
>
>
> The dynamic policy provider (net.jini.security.policy.DynamicPolicy et al) is created in the build as libe-ext/jsk-policy.jar, but it isn't published to Maven Central.
> We need to create a pom file similar to poms/jsk-resources.pom and then release it to the Maven repository.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira