[ https://issues.apache.org/jira/browse/PROTON-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885760#comment-13885760 ]
ASF subversion and git services commented on PROTON-417: -------------------------------------------------------- Commit 1562574 from r...@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1562574 ] PROTON-253, PROTON-417, and PROTON-499: This change consits mostly of moving stuff around to avoid using the "test-jar" mechanism introduced into the proton-j build a while ago. It appears that use of this mechanism causes the maven build to be circularly self-dependent, i.e. it requires an older stale binary version of its own output in order to successfully complete the mvn compile stage. There are also some fairly small code changes included that make the bouncycastle dependency a runtime dependency rather than a compile-time dependency. > Remove/optionalize bouncycastle dependency > ------------------------------------------ > > Key: PROTON-417 > URL: https://issues.apache.org/jira/browse/PROTON-417 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j > Reporter: Rafael H. Schloming > Fix For: 0.7 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)