commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COMMONSSITE-21) commons-parent-6 pom changes
Date Mon, 17 Dec 2007 20:01:44 GMT

    [ https://issues.apache.org/jira/browse/COMMONSSITE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552513
] 

Sebb commented on COMMONSSITE-21:
---------------------------------

I think the NOTICE and LICENSE files should be present in SVN at the top-level of each tree.


This is already the case for the commons projects I looked at.

I've asked for confirmation of this on the legal discuss list.

I also think that the N & L files really ought to be manually created to ensure that the
requirements are met.

They don't change very frequently, so regeneration is not an issue.
And if it is confirmed that the N & L files need to be in SVN, then generating them automatically
is pointless.

> commons-parent-6 pom changes
> ----------------------------
>
>                 Key: COMMONSSITE-21
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-21
>             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,
COMMONSSITE-21-commons-parent-pom-v2.patch
>
>
> Opening this ticket to discuss changes for Version 6 of the commons-parent pom.
> See thread: http://tinyurl.com/39eo9z 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.


Mime
View raw message