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

Randy Watler resolved JS2-1157.
-------------------------------

    Resolution: Fixed

Committed revision 929218

- Dependency to JUG LGPL libraries removed/stubbed out.
- Step2 sources committed to SCM

> Remove LGPL dependencies for Step2
> ----------------------------------
>
>                 Key: JS2-1157
>                 URL: https://issues.apache.org/jira/browse/JS2-1157
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.2.1
>         Environment: OpenID Google Step2 Implementation
>            Reporter: Randy Watler
>            Assignee: Randy Watler
>            Priority: Critical
>             Fix For: 2.2.1
>
>
> The jug dependency below is apparently LGPL. This has to be expunged before 
> OpenID support can be released as part of the installer.
> [INFO] |  |  \- com.google.step2:step2-common:jar:0:compile
> [INFO] |  |     +- org.openxri:openxri-syntax:jar:1.2.0:compile
> [INFO] |  |     |  \- com.ibm.icu:icu4j:jar:3.4.4:compile
> [INFO] |  |     +- org.openxri:openxri-client:jar:1.2.0:compile
> [INFO] |  |     |  +- jug:jug:jar:1.1.2:compile
> [INFO] |  |     |  +- xml-security:xmlsec:jar:1.3.0:compile
> [INFO] |  |     |  \- xalan:xalan:jar:2.4.1:compile (version managed from 
> 2.7.0)
> [INFO] |  |     +- org.apache.httpcomponents:httpclient:jar:4.0.1:compile
> [INFO] |  |     |  \- org.apache.httpcomponents:httpcore:jar:4.0.1:compile
> [INFO] |  |     \- org.jdom:jdom:jar:1.1:compile
> May also pull Step2 out of the  https://svn.bluesunrise.com and incorporate 
> into the Jetspeed build as a stand-alone jar to ensure visibilty of these 
> sources.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to