Re: Maven brings “test” transitive dependency as “compile”

2020-05-22 Thread Debraj Manna
Thanks Andy for replying. maven dependency:tree -Dverbose does not seem to work for me. It gives me the below message ... [INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ delete --- [INFO] Verbose not supported since maven-dependency-plugin 3.0 [INFO]

Re: Maven brings “test” transitive dependency as “compile”

2020-05-22 Thread Andy Feldman
On Fri, May 22, 2020 at 6:31 AM Debraj Manna wrote: > bookkeeper-common is in test scope but still netty-common is showing up as > compile dependency. > Is it possible that netty-common is a transitive dependency of another dependency as well? Running dependency:tree does not show all paths to

Re: bad links

2020-05-22 Thread Greg Chabala
Looks like most of these were fixed in April with this commit: https://github.com/apache/maven-deploy-plugin/commit/5378b4936866a927260b893dfd81abb2f4ceb1ef and there's an open PR from 2018 for the dead example link: https://github.com/apache/maven-deploy-plugin/pull/2 On Fri, May 22, 2020 at

Re: bad links

2020-05-22 Thread Anders Hammar
Works for me. /Anders (mobile) Den fre 22 maj 2020 21:54Greg Chabala skrev: > It looks to me that some of the inline links in the Usage paragraph are > broken: > user mailing list - links to > https://maven.apache.org/plugins/maven-deploy-plugin/mail-lists.html which > 404s > mail archive -

Re: bad links

2020-05-22 Thread Greg Chabala
It looks to me that some of the inline links in the Usage paragraph are broken: user mailing list - links to https://maven.apache.org/plugins/maven-deploy-plugin/mail-lists.html which 404s mail archive - also links to https://maven.apache.org/plugins/maven-deploy-plugin/mail-lists.html issue

Re: bad links

2020-05-22 Thread Karl Heinz Marbaise
Hi Robert, On 22.05.20 19:21, Roger Pack wrote: As a note all the url's under "usages" here: https://maven.apache.org/plugins/maven-deploy-plugin/index.html are 404's... Cheers! Unfortunately I can not acknowledge this? working fine from my site. Yes they are shown as "not secure" cause

bad links

2020-05-22 Thread Roger Pack
As a note all the url's under "usages" here: https://maven.apache.org/plugins/maven-deploy-plugin/index.html are 404's... Cheers! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: Maven brings “test” transitive dependency as “compile”

2020-05-22 Thread Debraj Manna
Thanks Tomo for replying. No I don't have any dependencyManagement specified in my parent pom. I have placed the effective pom here . mvn dependency:tree -Dverbose does not work for me. Below is the result I got. Am I

slf4j-jcl-1.0.1: Checksum validation failed

2020-05-22 Thread Tomo Suzuki
Hi Maven users, Does anyone know why slf4j-jcl-1.0.1's checksum is invalid in Maven Central? I'm investigating the following warning message: [WARNING] Could not validate integrity of download from https://repo1.maven.org/maven2/org/slf4j/slf4j-jcl/1.0.1/slf4j-jcl-1.0.1.pom: Checksum validation

Re: Maven brings “test” transitive dependency as “compile”

2020-05-22 Thread Tomo Suzuki
Hi Debraj, That's strange. "mvn dependency:tree -Dverbose" gives more information. "mvn help:effective-pom" may give you some information for netty-comon. By any change, does the parent (or poms imported by parent) declare dependencyManagement for netty-common? On Fri, May 22, 2020 at 9:31 AM

Maven brings “test” transitive dependency as “compile”

2020-05-22 Thread Debraj Manna
Hi In my project I am observing that maven 3.6.3 is bringing the test transitive dependency as compile. My understanding is that transitive dependency coming from test scope should also have test scope. Can someone let me know is my understanding wrong? When I run "mvn dependency:tree" for my

Distribution of buildinfo together with artifacts to Maven Central

2020-05-22 Thread Konrad Windszus
Hi, the buildinfo file (generated by https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin ) is useful to check reproducability. Is it supposed to be uploaded to Maven Central along with the artifact (with which