You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/05/18 18:28:12 UTC

[jira] Issue Comment Edited: (MNG-4680) Please fix license distribution model

    [ http://jira.codehaus.org/browse/MNG-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221650#action_221650 ] 

Benjamin Bentmann edited comment on MNG-4680 at 5/18/10 11:26 AM:
------------------------------------------------------------------

Hint: The art is to report concerns to the right address.

This issue tracker (MNG) is for the Maven core distribution as available from the download site. The Maven core is basically nothing more than a framework for build plugins. What files go into an artifact and what artifacts/files get deployed to repositories is for the most part a matter of the plugins being employed.

bq. the licence file was packaged properly in the bundle but it was never included in the central repository
So, if you have an issue with the contents of the central repository and its maintenance, you can try filling an issue in MEV or contact repo-maintainers@maven.apache.org. Maven core is not responsible for processing bundle uploads.

bq. Yet, the Maven distribution system doesn't actually enable adequate redistribution of the licences
You can include license files inside your artifacts or attach them as secondary artifacts, so I can't follow your reasoning in this regard.

      was (Author: bentmann):
    Hint: The art is to report concerns to the right address.

This issue tracker (MNG) is for the Maven core distribution as available from the download site. The Maven core is basically nothing more than a framework for build plugins. What files go into an artifact and what artifacts/files get deployed to repositories is for the most part a matter of the plugins being employed.

bq. the licence file was packaged properly in the bundle but it was never included in the central repository
So, if you have an issue with the contents of the central repository and its maintenance, you can try filling an issue in MEV or contact repo-maintainers@maven.apache.org.

bq. Yet, the Maven distribution system doesn't actually enable adequate redistribution of the licences
You can include license files inside your artifacts or attach them as secondary artifacts, so I can't follow your reasoning in this regard.
  
> Please fix license distribution model
> -------------------------------------
>
>                 Key: MNG-4680
>                 URL: http://jira.codehaus.org/browse/MNG-4680
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>            Reporter: Bruno Harbulot
>            Assignee: Benjamin Bentmann
>            Priority: Critical
>
> Most OSS licences mandate the redistribution of the licence with the software as a condition in the licence. A large number of projects, more particularly in the central repository, are redistributed without any mechanism to redistribute the licence correctly, thereby making the central repository be in breach of those licences.
> While there is a guideline in the "Introduction to the Standard Directory Layout" [1] to put the LICENSE.txt and NOTICE.txt file in the root directory, nothing seems to be done with them.
> In addition:
>   - Since version 2.1 of the maven-repository-plugin, LICENSE.txt is no longer included in the bundle created with repository:bundle-create.
>   - LICENSE.txt files in bundles uploaded via the JIRA/MAVENUPLOAD mechanism don't seem to appear in the central repository.
> Having <license>BSD</license> or <license>GPL</license> in the POM is not enough.
> (See related thread [2].)
> [1] http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> [2] http://markmail.org/thread/s5jsvatxbsynwajc#query:+page:1+mid:whtbsnnejszyad2h+state:results

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