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-79) maven-remote-resources-plugin is skipped by default + recent apache parent pom uses the same version
Date Mon, 15 Dec 2014 15:47:14 GMT

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

Sebb commented on COMMONSSITE-79:
---------------------------------

NOTICE and LICENSE files need to be present at the top level of SVN anyway, because we publish
the URLs and all distributions need to have N&L files.

Also NOTICE files may vary between Commons components.

bq. LICENSE on the other hand is the same everywhere,

If a component includes 3rd party files, then their license must either be included in the
LICENSE file, or the must be a pointer to the 3rd party license in the LICENSE file.
In both cases the LICENSE file is non-standard. Though of course the first part of the text
is standard across all ASF projects.

If the component does not have N&L files included in SVN, how can one tell if this is
deliberate, or an accidental omission?

The solution to all of these requirements is to ensure that N&L are at the top-level of
the SCM tree and included them in the release archives and jars as appropriate.

> maven-remote-resources-plugin is skipped by default + recent apache parent pom uses the
same version
> ----------------------------------------------------------------------------------------------------
>
>                 Key: COMMONSSITE-79
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-79
>             Project: Commons All
>          Issue Type: Bug
>            Reporter: Romain Manni-Bucau
>
> Solution: remove declaration of this plugin in commons parent pom



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message