[jira] [Updated] (MPMD-371) Using two ruleset files with same name in different directories

[Bruno Harbulot (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPMD-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno Harbulot updated MPMD-371:

Summary: Using two ruleset files with same name in different directories  
(was: Cannot use two ruleset files with same name in different directories)

> Using two ruleset files with same name in different directories
> ---
>
> Key: MPMD-371
> URL: https://issues.apache.org/jira/browse/MPMD-371
> Project: Maven PMD Plugin
>  Issue Type: Bug
>  Components: PMD
>Affects Versions: 3.20.0
>Reporter: Bruno Harbulot
>Priority: Major
>
> It is not possible to rely on two ruleset files that share the same filename 
> (but are located in different directories).
> Here is an sample configuration for a multi-module project where there is a 
> common {{pmd-ruleset.xml}} file in the parent project and a 
> {{pmd-ruleset.xml}} file in each sub-module. (This is not limited to 
> multi-module projects, it could be any configuration where the same filename 
> is used in different directories.)
>  
> {code:java}
> 
>     org.apache.maven.plugins
>     maven-pmd-plugin
>     ${pmd-maven-plugin.version}
>     
>         
>             ${project.basedir}/pmd-ruleset.xml
>             ${project-root.basedir}/pmd-ruleset.xml
>         
>     
> {code}
>  
> The files specified in the {{}} elements are copied into 
> {{{}${project.build.directory}/pmd/rulesets{}}}, but only the actual filename 
> is taken into account during the copy, so the second copy overwrites the 
> first.
> This seems to be due to the implementation of 
> {{PmdReport.resolveRulesets(...)}} and {{PmdReport.getLocationTemp(...)}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MPMD-371) Cannot use two ruleset files with same name in different directories

[Bruno Harbulot (Jira)]

Bruno Harbulot created MPMD-371:
---

 Summary: Cannot use two ruleset files with same name in different 
directories
 Key: MPMD-371
 URL: https://issues.apache.org/jira/browse/MPMD-371
 Project: Maven PMD Plugin
  Issue Type: Bug
  Components: PMD
Affects Versions: 3.20.0
Reporter: Bruno Harbulot


It is not possible to rely on two ruleset files that share the same filename 
(but are located in different directories).

Here is an sample configuration for a multi-module project where there is a 
common {{pmd-ruleset.xml}} file in the parent project and a {{pmd-ruleset.xml}} 
file in each sub-module. (This is not limited to multi-module projects, it 
could be any configuration where the same filename is used in different 
directories.)

 
{code:java}

    org.apache.maven.plugins
    maven-pmd-plugin
    ${pmd-maven-plugin.version}
    
        
            ${project.basedir}/pmd-ruleset.xml
            ${project-root.basedir}/pmd-ruleset.xml
        
    
{code}
 

The files specified in the {{}} elements are copied into 
{{{}${project.build.directory}/pmd/rulesets{}}}, but only the actual filename 
is taken into account during the copy, so the second copy overwrites the first.

This seems to be due to the implementation of 
{{PmdReport.resolveRulesets(...)}} and {{PmdReport.getLocationTemp(...)}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] Commented: (MNG-4680) Please fix license distribution model

[Bruno Harbulot (JIRA)]

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

Bruno Harbulot commented on MNG-4680:
-

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

(I've just posted another e-mail on the users list in that thread.)

My reasoning is that redistribution of software is one of the key core features 
of Maven, and it's built its success upon distributing OSS software via the 
central repository; yet, it has too little, virtually nothing, to ensure that 
those licences are respected (considering that most of them are about the 
conditions of redistribution). The convention over configuration aspect seems 
to fail in that respect.

One suitable enhancement would be to have a licence file pulled along with the 
POM file for example, when fetching a new artifact.

> 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 BSD or GPL 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

[jira] Reopened: (MNG-4680) Please fix license distribution model

[Bruno Harbulot (JIRA)]

 [ 
http://jira.codehaus.org/browse/MNG-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno Harbulot reopened MNG-4680:
-


Sorry, but the Maven mechanism is flawed, it's not just a matter of contacting 
the project owners.

Firstly, I am one of these project owners as mentioned in the thread I cited 
above, and the licence file was packaged properly in the bundle but it was 
never included in the central repository, despite being bundled correctly.

Secondly, most OSS licences are about the conditions of *redistribution* of the 
software and Maven, via the central repository or more generally the repository 
system is *redistributing* software. Yet, the Maven distribution system doesn't 
actually enable adequate redistribution of the licences as they often require 
(e.g. BSD), or the documentation needs some serious fixing.

> 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 BSD or GPL 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

[jira] Created: (MNG-4680) Please fix license distribution model

[Bruno Harbulot (JIRA)]

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
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 BSD or GPL 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

[jira] Created: (MAVENUPLOAD-2400) log4j:log4j:jar:1.2.15 in central repository depends on external repository

[Bruno Harbulot (JIRA)]

log4j:log4j:jar:1.2.15 in central repository depends on external repository
---

 Key: MAVENUPLOAD-2400
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2400
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Bruno Harbulot


log4j:log4j:jar:1.2.15 has dependencies on artifacts that are not available via 
the central repository:
- com.sun.jdmk:jmxtools:jar:1.2.1
- com.sun.jmx:jmxri:jar:1.2.1
- javax.jms:jms:jar:1.1



-- 
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

[jira] Created: (MAVENUPLOAD-2399) org.opensaml:opensaml in central repository repends on external repositories

[Bruno Harbulot (JIRA)]

org.opensaml:opensaml in central repository repends on external repositories


 Key: MAVENUPLOAD-2399
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2399
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Bruno Harbulot


'org.opensaml:opensaml:2.2.1' has a dependency on 'org.opensaml:openws:1.2.0', 
which is not available from the central repository but from 
 which is a repository listed 
in that pom file.

-- 
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

[jira] Created: (MAVENUPLOAD-2293) Please upload jSSLutils 0.5.1

[Bruno Harbulot (JIRA)]

Please upload jSSLutils 0.5.1
-

 Key: MAVENUPLOAD-2293
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2293
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Bruno Harbulot


Hello, I'm the developer and project owner of jsslutils. Could you please 
upload this version of the project in the repository?

Thank you,

Bruno.

-- 
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

[jira] Created: (MAVENUPLOAD-2178) Please upload jSSLutils 0.5

[Bruno Harbulot (JIRA)]

Please upload jSSLutils 0.5
---

 Key: MAVENUPLOAD-2178
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2178
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Bruno Harbulot


Hello, I'm the developer and project owner of jsslutils. Could you please 
upload this project in the repository?

There is a test dependency to:
  * org.jsslutils:jsslutils-test-certificates:1.0.2
  
http://jsslutils.googlecode.com/files/jsslutils-test-certificates-1.0.2-bundle.jar
  * org.jsslutils:jsslutils-test-helpers:0.5
  
http://jsslutils.googlecode.com/files/jsslutils-test-helpers-0.5-bundle.jar

There is also this related module:
  * org.jsslutils:jsslutils-extra-apachehttpclient3:0.5
  
http://jsslutils.googlecode.com/files/jsslutils-extra-apachehttpclient3-0.5-bundle.jar

Thank you.

Bruno.

-- 
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

[jira] Created: (MAVENUPLOAD-2161) Please upload jSSLutils 0.4

[Bruno Harbulot (JIRA)]

Please upload jSSLutils 0.4
---

 Key: MAVENUPLOAD-2161
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2161
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Bruno Harbulot


Hello, I'm the developer and project owner of jsslutils. Could you please 
upload this project in the repository?

There is a test dependency to:
  * com.googlecode.jsslutils:jsslutils-test-certificates:1.0.1
  
http://jsslutils.googlecode.com/files/jsslutils-test-certificates-1.0.1-bundle.jar
  * com.googlecode.jsslutils:jsslutils-test-helpers:0.4
  
http://jsslutils.googlecode.com/files/jsslutils-test-helpers-0.4-bundle.jar

Thank you.

Bruno.

-- 
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

[jira] Closed: (MAVENUPLOAD-2047) Please upload jSSLutils 0.2.1

[Bruno Harbulot (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno Harbulot closed MAVENUPLOAD-2047.
---

Resolution: Duplicate

I've updated this with a more recent package:  MAVENUPLOAD-2054

> Please upload jSSLutils 0.2.1
> -
>
> Key: MAVENUPLOAD-2047
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2047
> Project: maven-upload-requests
>  Issue Type: Wish
>Reporter: Bruno Harbulot
>
> Hello, I'm the developer and project owner of jsslutils. Could you please 
> upload this project in the repository?
> There is a test-scoped dependency to 
> com.googlecode.jsslutils:jsslutils-test-certificates:1.0 (MAVENUPLOAD-2046).
> Thank you.
> Bruno.

-- 
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

[jira] Created: (MAVENUPLOAD-2054) Please upload jSSLutils 0.3

[Bruno Harbulot (JIRA)]

Please upload jSSLutils 0.3
---

 Key: MAVENUPLOAD-2054
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2054
 Project: maven-upload-requests
  Issue Type: Wish
Reporter: Bruno Harbulot


Hello, I'm the developer and project owner of jsslutils. Could you please 
upload this project in the repository?

There is a test-scoped dependency to 
com.googlecode.jsslutils:jsslutils-test-certificates:1.0 (MAVENUPLOAD-2046).

Thank you.

Bruno.

-- 
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

[jira] Closed: (MAVENUPLOAD-2044) Please upload jSSLutils 0.2

[Bruno Harbulot (JIRA)]

 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno Harbulot closed MAVENUPLOAD-2044.
---

Resolution: Duplicate

Sorry, I was suggested to bundle the resources required for the tests in a 
separate bundle. I've thus submitted a new issue in MAVENUPLOAD-2047.

> Please upload jSSLutils 0.2
> ---
>
> Key: MAVENUPLOAD-2044
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2044
> Project: maven-upload-requests
>  Issue Type: Wish
>Reporter: Bruno Harbulot
>
> Hello, I'm the developer and project owner of jsslutils. Could you please 
> upload this project in the repository?
> Thank you.
> Bruno.

-- 
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

[jira] Created: (MAVENUPLOAD-2047) Please upload jSSLutils 0.2.1

[Bruno Harbulot (JIRA)]

Please upload jSSLutils 0.2.1
-

 Key: MAVENUPLOAD-2047
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2047
 Project: maven-upload-requests
  Issue Type: Wish
Reporter: Bruno Harbulot


Hello, I'm the developer and project owner of jsslutils. Could you please 
upload this project in the repository?

There is a test-scoped dependency to 
com.googlecode.jsslutils:jsslutils-test-certificates:1.0 (MAVENUPLOAD-2046).

Thank you.

Bruno.

-- 
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

[jira] Created: (MAVENUPLOAD-2046) Please upload jSSLutils test certificates 1.0

[Bruno Harbulot (JIRA)]

Please upload jSSLutils test certificates 1.0
-

 Key: MAVENUPLOAD-2046
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2046
 Project: maven-upload-requests
  Issue Type: Wish
Reporter: Bruno Harbulot


Hello, I'm the developer and project owner of jsslutils. Could you please 
upload this bundle in the repository?

Thank you.

Bruno.

-- 
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

[jira] Created: (MAVENUPLOAD-2044) Please upload jSSLutils 0.2

[Bruno Harbulot (JIRA)]

Please upload jSSLutils 0.2
---

 Key: MAVENUPLOAD-2044
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2044
 Project: maven-upload-requests
  Issue Type: Wish
Reporter: Bruno Harbulot


Hello, I'm the developer and project owner of jsslutils. Could you please 
upload this project in the repository?

Thank you.

Bruno.

-- 
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