On Thu, 2007-01-25 at 09:58 +1100, David Crossley wrote: > Gav.... wrote: > > > From: Thorsten Scherler > > > David Crossley wrote: > > > > Thorsten Scherler wrote: > > > > > > > > > > To make the version compile you need to download > > > > > the JSR 173 API from > > > > > http://www.ibiblio.org/maven2/stax/stax-api/1.0/stax-api-1.0.jar > > > > > and copy it to lib/api/. We cannot redistribute the API (it was once a > > > > > discussion on cocoon-dev when the jcr got introduced). > > > > > > > > Would you please explain that further. > > > > > > I cannot post any citation from the mail I referred since I just saw > > > that it was a private list where I read it. > > > > > > Bottom line of the mail was that the JSR-170 terms of license allowed by > > > Sun's lawyers for the JCR specification (which includes the JCR > > > interface jar) are not compatible with ASF. > > > > You sure about that ? I have not looked deeply into it so I apologise, but > > With me being on a number of Apache Mailing Lists, JSR-170 rang a bell > > When I saw it in your mail. > > Wait, you are both confusing the issue. Thorsten started talking > about JSR-173 then made a mistake and referred to JSR-170. > > Thorsten, please clearly explain.
I used JSR-170 as example. JCR specifications in general includes the JCR interface jar and the license AFAIK is not compatible with the ASF. salu2 > > > Please take a look at :- > > > > http://jackrabbit.apache.org/ (Jackrabbit) > > http://jcp.org/en/jsr/detail?id=170 (ASF is member of expert group) > > http://www.openwfe.org/openwfe-jcr-beancoder.html (Used with Maven) > > > > > Futher it was pointed out that the JCR API (as interface), will either > > > already be present in the J2SE engine (with or without an implementation > > > from java 6 up) or must be downloaded and installed by the user (either > > > directly in $JAVA_HOME/lib or into the location I pointed out before > > > (whiteboard/dispatcher/lib/api)). > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
