www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manfred Moser (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LEGAL-333) Maven Central Repository terms are incompatible with the Apache License
Date Mon, 25 Sep 2017 02:22:00 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178452#comment-16178452
] 

Manfred Moser edited comment on LEGAL-333 at 9/25/17 2:21 AM:
--------------------------------------------------------------

Again.. there is nothing to do here. I am a Maven committer and Maven does NOT have a centralized
distribution model at all. It just has a built in default that points to the Central Repository.
It has all the configuration mechanism built in to completely change the default to whatever
you. Just set up your settings.xml to point whatever else you want to use. 

Feel free to set up your own repository and use it as a replacement. In fact there are multiple
repository manager that are designed to do just that.

https://maven.apache.org/repository-management.html

And you can use tools such as my Maven Repository Provisioner to get stuff into your own repo
as desired. 
https://github.com/simpligility/maven-repository-tools/tree/master/maven-repository-provisioner

I agree with the idea to close this issue. There is really no real problem. 



was (Author: simpligility):
Again.. there is nothing to do here. I am a Maven committer and Maven does NOT have a centralized
distribution model at all. It just has a built in default that points to the Central Repository.
It has all the configuration mechanism built in to completely change the default to whatever
you. Just set up your settings.xml to point whatever else you want to use. 

Feel free to set up your own repository and use it as a replacement. In fact there are multiple
repository manager that are designed to do just that.

https://maven.apache.org/repository-management.html

And you can use tools such as my Maven Repository Provisioner to get stuff into your own repo
as desired. 
https://github.com/simpligility/maven-repository-tools/tree/master/maven-repository-provisioner



> Maven Central Repository terms are incompatible with the Apache License
> -----------------------------------------------------------------------
>
>                 Key: LEGAL-333
>                 URL: https://issues.apache.org/jira/browse/LEGAL-333
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Carte Project
>            Assignee: Chris A. Mattmann
>
> All or nearly all of the ASF's Java software projects are distributed through the Maven
Central Repository operated by Sonatype, Inc. Their "full terms of service" (as they are described
in [this page|http://central.sonatype.org/pages/ossrh-guide.html]) can be found here:
> [http://central.sonatype.org/pages/central-repository-producer-terms.html]
> The "Indemnity for Submissions" clause states:
> bq. You agree to indemnify and hold harmless Sonatype and its affiliates, suppliers,
partners, officers, agents, and employees from and against any claim, demand, losses, damages
or expenses (including reasonable attorney's fees) arising from your Submissions.
> To me, the obligation to indemnify against any claim "arising from your Submissions"
sounds somewhat incompatible with the 8 and 9 clauses of the [Apache License 2.0|http://www.apache.org/licenses/LICENSE-2.0].
And my understanding is that all of the ASF's Maven artifacts are nearly-automatically deployed
on that repository.
> Am I missing something?  Any comments?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message