commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Kitching (JIRA)" <>
Subject [jira] Commented: (COMMONSSITE-21) commons-parent-6 pom changes
Date Fri, 04 Jan 2008 18:08:34 GMT


Simon Kitching commented on COMMONSSITE-21:

Yes, it does seem that there is no official policy on license/notice files in svn. 

However I'm not convinced by the argument that since any dir can be checked out, there is
no logical place to put license/notice files in svn. The svn contents are very clearly structured
into modules which are "compilable units". Yes, theoretically someone could check out some
leaf directory then claim that the files "have no license information available", but that's
a pretty thin excuse. Anyone capable of reusing java code would know where the module ("compilable
unit") starts. That is the sensible point at which to check things out - and the license/notice
info should be available at that level.

It's just like putting copyright info inside the cover of a book. It doesn't need to be on
every page, because the book is the minimum distributable unit. But in the case of a book
series, it is not adequate to put the information in just one of the books in the set. Ok,
the analogy isn't perfect because books do not have a "raw" and "compiled" form both available
to users. But making source code available on the web via svn *is* publishing, and so notice/copyright
should be available there too, without requiring someone to look into a pom and determine
where a maven plugin will pull the information from during a build.

> commons-parent-6 pom changes
> ----------------------------
>                 Key: COMMONSSITE-21
>                 URL:
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Niall Pemberton
>         Attachments: commons-valdiator-generated-NOTICE.txt, COMMONSSITE-21-commons-parent-pom-v1.patch,
> Opening this ticket to discuss changes for Version 6 of the commons-parent pom.
> See thread: for related discussion/issues

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

View raw message