jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-592) Use only the standard Maven repository for dependencies
Date Mon, 30 Oct 2006 12:49:18 GMT
    [ http://issues.apache.org/jira/browse/JCR-592?page=comments#action_12445587 ] 
            
Roy T. Fielding commented on JCR-592:
-------------------------------------

The Day Spec License is the broadest possible license allowed under the JSPA (use of this
template is enforced by Sun legal as part of the review process prior to publication of the
Specification).  The JCP requires that this license be enforced through (at a minimum) a click-through
licensing agreement.  In other words, that license can only be used for personal experimentation
and distribution of bundles that include an independent implementation that passes the TCK.
 Apache Maven would require a separate license in order to distribute the JCR jar file to
third parties.

The CCLA that Day signed for Apache does not include the Specification and its associate API.
 JSPA rules do not allow us to transfer such a broad license to Apache due to the API compatibility
restrictions.
However, Day is able to extend additional license terms on its own that would not change the
specification agreement.  For example, Day could upload the JCR API jar file to the Maven
repository with a license addendum that states it may also be redistributed unmodified to
third parties for the purpose of building/compiling Java software, provided that further redistribution
of the JCR API jar file (such as when distributed with the result of that compilation) is
only allowed under the terms of the Day Specification License.

In any case, it is not okay for anyone other than Day to upload the jar to a repository. All
of the contribution agreements that feed IP into the JSR 170/283 process are funneled through
the Spec Lead, so it is safer to have the spec lead perform any actions that might lead to
copyright/patent issues down the line. [Those would be issues generated by the other EG members
-- Day does not have any such issues of its own].

Apache should probably ask the JCP to add Maven-style distribution as an additional (optional)
term to the standard template. That would allow Day to adopt the new term when 283 is published.


> Use only the standard Maven repository for dependencies
> -------------------------------------------------------
>
>                 Key: JCR-592
>                 URL: http://issues.apache.org/jira/browse/JCR-592
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: maven
>    Affects Versions: 0.9, 1.0, 1.0.1, 1.1
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.1.1
>
>
> The JCR API jars are now available in the standard Maven repository, see http://jira.codehaus.org/browse/MAVENUPLOAD-1050.
We could thus remove the dependency on the Day repository, as requested in http://jira.codehaus.org/browse/MEV-453.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message