[jira] [Created] (SUREFIRE-1516) Should surefire specialize test runner when test isolation (i.e., fork) is needed?
Fork Script created SUREFIRE-1516:
-
Summary: Should surefire specialize test runner when test
isolation (i.e., fork) is needed?
Key: SUREFIRE-1516
URL: https://issues.apache.org/jira/browse/SUREFIRE-1516
Project: Maven Surefire
Issue Type: New Feature
Components: Maven Surefire Plugin
Affects Versions: 2.21.0
Reporter: Fork Script
We observed that {code:java} mvn test -DforkCount=1 -DreuseForks=false {code}
has high overhead for several projects we recently used.
We developed a specific runner for this option, which reduces test execution
time by 49% on average. (Please see detailed results in the table below.)
[Here|https://github.com/forkscript/maven-surefire/commit/38f102f0165f081dd28c6a3023e0b052662857f0]
is a link to our commit (see ForkStarter.java:388). Our approach is hackish,
but we believe it can be engineered better if needed. Is this of interest to
surefire? We would be happy to discuss this further and provide more results.
Detailed results are below. Machine we used: Intel i7-6700U CPU @ 3.40GHz with
16GB of RAM, running Ubuntu 17.10. We can share our script used to collect the
numbers.
|| project || maven current (sec) || maven with our hack (sec) || time reduced
by ||
| activiti | 1300.54 | 1069.20 | 17% |
| bukkit | 18.98 | 4.80 | 74% |
| closurecompiler | 399.42 | 271.68 | 31% |
| commonscodec | 46.98 | 13.85 | 70% |
| commonsio | 107.35 | 67.41 | 37% |
| commonslang | 89.70 | 35.39 | 60% |
| commonsmath | 391.20 | 110.79 | 71% |
| commonsnet | 74.50 | 59.46 | 20% |
| commonsvalidator | 37.30 | 13.24 | 64% |
| configuration | 126.73 | 62.37 | 50% |
| crypto | 23.75 | 7.14 | 69% |
| gedcom4j | 195.43 | 64.10 | 67% |
| graphhopper | 90.80 | 41.25 | 54% |
| jaxx | 36.00 | 23.33 | 35% |
| la4j | 15.23 | 7.60 | 50% |
| openfire | 28.52 | 18.51 | 35% |
| retrofit | 53.22 | 35.36 | 33% |
| scribejava | 13.35 | 4.32 | 67% |
| vectorz | 37.90 | 11.19 | 70% |
| ztexec | 23.94 | 17.75 | 25% |
| Avg. | 155.54 | 96.93 | 49% |
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps) you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
How is it that the Maven build does _not_ even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only and
not the one defined in my own {{pom.xml}}?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the {{}} that I have explicitly defined in my {{pom.xml}}. The
{{shrinkwrap-bom}} artifact does exist in
[https://artifacts.example.com/repository/maven/] and can be fetched no problem
if it is explicitly defined in my {{pom.xml}} but defining it explicitly would
be a work-around and I cannot use this work-around in my situation.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445118#comment-16445118
]
Alan Czajkowski edited comment on MNG-6397 at 4/20/18 2:12 AM:
---
[~khmarbaise]
1. I appreciate your "work around" suggestion, and I've already thought of
trying this, but this is not an acceptable solution for me as this build goes
into a build system where I am not able to modify any {{settings.xml}} file.
Everything related to the build must be completely self-contained inside the
{{pom.xml}}, as this is a natural expectation of Maven, hence why I am logging
this as a "bug" because the build *should* work naturally without me having to
define mirrors.
2. It is _not_ interesting to see {{Connection reset}} because at the very
beginning of the description I explained the firewall situation. The firewall
here is _not_ causing anything to break in Maven. Maven is simply ignoring/not
respecting my {{}} definition in my own {{pom.xml}}.
was (Author: alan-czajkowski):
[~khmarbaise]
1. I appreciate your "work around" suggestion, and I've already thought of
trying this, but this is not an acceptable solution for me as this build goes
into a build system where I am not able to modify any {{settings.xml}} file.
Everything related to the build must be completely self-contained inside the
{{pom.xml}}, as this is a natural expectation of Maven, hence why I am logging
this as a "bug" because the build *should* work naturally without me having to
define mirrors.
2. It is _not_ interesting to see {{Connection reset}} because at the very
beginning of the description I explained the firewall situation. The firewall
here is not causing anything to break in Maven. Maven is simply ignoring/not
respecting my {{}} definition in my own {{pom.xml}}.
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> ${spring.boot.version}
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
>
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Component/s: POM
Artifacts and Repositories
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> ${spring.boot.version}
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I did not even reference this repo {{spring-milestone
> ([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
> When you go down the Spring Boot rabbit hole (go into the
> {{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
> structure a few jumps) you'll eventually get to a parent-pom
> {{spring-boot-dependencies}} with this definition:
> {code:xml}
> ...
>
>
>
> false
>
> spring-milestone
> Spring Milestone
> https://repo.spring.io/milestone
>
>
>
> true
>
>
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Labels: maven (was: )
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> ${spring.boot.version}
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I did not even reference this repo {{spring-milestone
> ([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
> When you go down the Spring Boot rabbit hole (go into the
> {{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
> structure a few jumps) you'll eventually get to a parent-pom
> {{spring-boot-dependencies}} with this definition:
> {code:xml}
> ...
>
>
>
> false
>
> spring-milestone
> Spring Milestone
> https://repo.spring.io/milestone
>
>
>
> true
>
> spring-snapshot
> Spring Snapshot
>
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps) you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
How is it that the Maven build does _not_ even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only and
not the one defined in my own {{pom.xml}}?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the {{}} that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps) you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
How is it that the Maven build does _not_ even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only and
not the one defined in my own {{pom.xml}}?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps) you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Environment:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T15:39:06-04:00)
Maven home: /usr/local/share/maven
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
was:
$ mvn -v
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T15:39:06-04:00)
Maven home: /usr/local/share/maven
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails (due to firewall restrictions)_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> ${spring.boot.version}
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I did not even
[jira] [Commented] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445118#comment-16445118
]
Alan Czajkowski commented on MNG-6397:
--
[~khmarbaise]
1. I appreciate your "work around" suggestion, and I've already thought of
trying this, but this is not an acceptable solution for me as this build goes
into a build system where I am not able to modify any {{settings.xml}} file.
Everything related to the build must be completely self-contained inside the
{{pom.xml}}, as this is a natural expectation of Maven, hence why I am logging
this as a "bug" because the build *should* work naturally without me having to
define mirrors.
2. It is _not_ interesting to see {{Connection reset}} because at the very
beginning of the description I explained the firewall situation. The firewall
here is not causing anything to break in Maven. Maven is simply ignoring/not
respecting my {{}} definition in my own {{pom.xml}}.
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: $ mvn -v
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails (due to firewall restrictions)_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> ${spring.boot.version}
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
>
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps) you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444869#comment-16444869
]
Karl Heinz Marbaise edited comment on MNG-6397 at 4/19/18 10:10 PM:
You should configure your repository manager correctly in your {{settings.xml}}
and define a
mirrorOf entry to redirect all request to your internal repository manager ...
It also interesting to see things like this: {{: Connection reset -> [Help
1]...}} ?
was (Author: khmarbaise):
You should configure your repository manager correctly in your {{settings.xml}}
and define a mirrorOf entry to redirect all request to your internal repository
manager ...
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: $ mvn -v
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails (due to firewall restrictions)_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> ${spring.boot.version}
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I did not even reference this repo {{spring-milestone
> ([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
> When you go down the Spring Boot rabbit hole (go into the
> {{spring-boot-starter-web}}'s {{pom.xml}} and
[jira] [Commented] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444869#comment-16444869
]
Karl Heinz Marbaise commented on MNG-6397:
--
You should configure your repository manager correctly in your {{settings.xml}}
and define a mirrorOf entry to redirect all request to your internal repository
manager ...
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> -
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.0, 3.5.2, 3.5.3
> Environment: $ mvn -v
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails (due to firewall restrictions)_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> ${spring.boot.version}
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I did not even reference this repo {{spring-milestone
> ([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
> When you go down the Spring Boot rabbit hole (go into the
> {{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
> structure a few jumps) you'll eventually get to a parent-pom
> {{spring-boot-dependencies}} with this definition:
> {code:xml}
> ...
>
>
>
> false
>
> spring-milestone
> Spring Milestone
>
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps) you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
*How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
structure a few jumps, you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
*How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up it parent-pom
structure a few jumps, you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:xml}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
*How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
Could not resolve dependencies for project
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to
collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up it parent-pom
structure a few jumps, you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:java}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
*How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project
maven-multi-module-demo-jboss-backend: Could not resolve dependencies for
project
com.example.pipe:maven-multi-module-demo-jboss-backend:war:1.0.0-SNAPSHOT:
Failed to collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up it parent-pom
structure a few jumps, you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:java}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
*How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Czajkowski updated MNG-6397:
-
Description:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project
maven-multi-module-demo-jboss-backend: Could not resolve dependencies for
project com.td.pipe:maven-multi-module-demo-jboss-backend:war:1.0.0-SNAPSHOT:
Failed to collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up it parent-pom
structure a few jumps, you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:java}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
*How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency resolution bug to me as the Maven
build does not even make a single attempt at trying to get {{shrinkwrap-bom}}
from the repository that I have explicitly defined in my {{pom.xml}}.*
was:
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
[jira] [Created] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition
Alan Czajkowski created MNG-6397:
Summary: Maven Transitive Dependency Resolution Does Not Respect
Repository Definition
Key: MNG-6397
URL: https://issues.apache.org/jira/browse/MNG-6397
Project: Maven
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.5.3, 3.5.2, 3.5.0
Environment: $ mvn -v
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T15:39:06-04:00)
Maven home: /usr/local/share/maven
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
Reporter: Alan Czajkowski
_*Note:* I am trying to do a build behind a firewall which means I cannot
access the Internet, I can only access my internal Maven repository inside my
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/
works fine_
- _grabbing artifacts from anywhere fails (due to firewall restrictions)_
Let's begin:
My {{pom.xml}} has the following:
{code:xml}
...
...
org.springframework.boot
spring-boot-starter-web
${spring.boot.version}
...
...
...
central
Public
https://artifacts.example.com/repository/maven/
true
true
...
...
{code}
The {{dependency:tree}} for the Spring Boot dependency above is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
| +-
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
| | +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
| | +-
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
| | \-
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
| +-
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
| | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
| +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
| | +- javax.validation:validation-api:jar:2.0.1.Final:compile
| | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
| | \- com.fasterxml:classmate:jar:1.3.1:compile
| \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}
How is it that the build fails as such:
{code:java}
...
Downloading:
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading:
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project
maven-multi-module-demo-jboss-backend: Could not resolve dependencies for
project com.td.pipe:maven-multi-module-demo-jboss-backend:war:1.0.0-SNAPSHOT:
Failed to collect dependencies at
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
artifact descriptor for
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
When you go down the Spring Boot rabbit hole (go into the
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up it parent-pom
structure a few jumps, you'll eventually get to a parent-pom
{{spring-boot-dependencies}} with this definition:
{code:java}
...
false
spring-milestone
Spring Milestone
https://repo.spring.io/milestone
true
spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot
false
rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones
...
{code}
*How is it that the Maven build does not even attempt to reach out to
[https://artifacts.example.com/repository/maven/] to try to find the missing
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only?
*This seems like a transitive dependency
[jira] [Commented] (MSHARED-695) Move checksum creation from install part to deploy part
[ https://issues.apache.org/jira/browse/MSHARED-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444822#comment-16444822 ] Hudson commented on MSHARED-695: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-695 #4 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-695/4/ > Move checksum creation from install part to deploy part > --- > > Key: MSHARED-695 > URL: https://issues.apache.org/jira/browse/MSHARED-695 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: maven-artifact-transfer-0.10.0 > > > We should remove the checksum generation from install parts and move them > consistently to the deploy part instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINVOKER-235) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MINVOKER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444780#comment-16444780 ] Hudson commented on MINVOKER-235: - Build failed in Jenkins: Maven TLP » maven-invoker-plugin » master #14 See https://builds.apache.org/job/maven-box/job/maven-invoker-plugin/job/master/14/ > Upgrade plexus-utils 3.1.0 > -- > > Key: MINVOKER-235 > URL: https://issues.apache.org/jira/browse/MINVOKER-235 > Project: Maven Invoker Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MCHANGES-387) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MCHANGES-387: Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MCHANGES-387 URL: https://issues.apache.org/jira/browse/MCHANGES-387 Project: Maven Changes Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MINVOKER-234) Upgrade maven-shared-utils to 3.2.1
[ https://issues.apache.org/jira/browse/MINVOKER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINVOKER-234. Resolution: Done Done in [ab95f2b74e8f39c23cbdd1690aff640a9be30aee|https://gitbox.apache.org/repos/asf?p=maven-invoker-plugin.git;a=commitdiff;h=ab95f2b74e8f39c23cbdd1690aff640a9be30aee] > Upgrade maven-shared-utils to 3.2.1 > --- > > Key: MINVOKER-234 > URL: https://issues.apache.org/jira/browse/MINVOKER-234 > Project: Maven Invoker Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WAGON-518) AbstractHttpClientWagon#putFromStream reads entire content to memory
[
https://issues.apache.org/jira/browse/WAGON-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444572#comment-16444572
]
Chris Lott commented on WAGON-518:
--
Latest workaround: use LightweightHttpWagon which does not override the
putFromStream() method. Got tripped up by a null-pointer exception so now I set
the authenticator field as shown below, please advise on correct usage.
{code:java}
LightweightHttpWagon lw = new LightweightHttpWagon();
lw.setAuthenticator(new LightweightHttpWagonAuthenticator());
{code}
> AbstractHttpClientWagon#putFromStream reads entire content to memory
>
>
> Key: WAGON-518
> URL: https://issues.apache.org/jira/browse/WAGON-518
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.12
>Reporter: Chris Lott
>Priority: Major
>
> Method putFromSteam in class AbstractHttpClientWagon seems to violate the
> implied contract of working with streams. It uses much memory because it
> first consumes the input stream argument, then transfers that content. The
> code that consumes the stream is in the private class
> RequestEntityImplementation ctor:
> {code:java}
> byte[] bytes = IOUtil.toByteArray( stream );{code}
> Please revise it, if possible, to behave more like the superclass
> StreamWagon's putFromStream method, which does the transfer straight from the
> input stream.
> We are attempting to PUT some 150MB artifacts in a java microservice that
> runs with rather sharp memory limits. As a local workaround we increased the
> JVM's -Xmx argument but that way lies madness.
> Thanks in advance for any suggestions or workarounds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MENFORCER-281) RequirePluginVersions broken with "CI Friendly versions"
[
https://issues.apache.org/jira/browse/MENFORCER-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444384#comment-16444384
]
ASF GitHub Bot commented on MENFORCER-281:
--
jglick commented on issue #28: [MENFORCER-281] added IT to show the issue.
URL: https://github.com/apache/maven-enforcer/pull/28#issuecomment-382808112
As 5311c5742da760e2910eda39698c62f7cfb3e46e specifically, with
ad0a84368f97a335a9455f04ec04bfbbb10ac49e being the fix AFAICT.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> RequirePluginVersions broken with "CI Friendly versions"
>
>
> Key: MENFORCER-281
> URL: https://issues.apache.org/jira/browse/MENFORCER-281
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 1.4.1, 3.0.0-M1
>Reporter: James Nord
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
>
> Maven
> [3.5.0|https://maven.apache.org/docs/3.5.0/release-notes.html#Overview_about_the_changes]
> [introduced CI friendly
> versions|https://maven.apache.org/maven-ci-friendly.html].
> However when used with [multi module
> project|https://maven.apache.org/maven-ci-friendly.html#Multi_Module_Setup]
> the enforcer fails the build as it can not resolve the parent.
> The bug is that the parent resolution of a module in the reactor is
> attempting to use the untransposed version.
> e.g.
> {noformat}
> INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ sub-module
> ---
> [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions
> failed with message:
> Failure to find com.acme.product:parent:pom:0.9.8-${revision}SNAPSHOT in
> https://repo.acme.com/content/groups/all was cached in the local repository,
> resolution will not be reattempted until the update interval of acme-internal
> has elapsed or updates are forced
> com.acme.product:parent:pom:0.9.8-${revision}SNAPSHOT
> from the specified remote repositories:
> acme-internal (https://repo.acme.com/content/groups/all, releases=true,
> snapshots=true)
> {noformat}
> to reproduce create a new multi module project as per the linked page above.
> Add the enforcer plugin and rule to the build
> run {{mvn -Drevision=1.2.3-SNAPSHOT}} and watch the build fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] jglick commented on issue #28: [MENFORCER-281] added IT to show the issue.
jglick commented on issue #28: [MENFORCER-281] added IT to show the issue. URL: https://github.com/apache/maven-enforcer/pull/28#issuecomment-382808112 As 5311c5742da760e2910eda39698c62f7cfb3e46e specifically, with ad0a84368f97a335a9455f04ec04bfbbb10ac49e being the fix AFAICT. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (WAGON-518) AbstractHttpClientWagon#putFromStream reads entire content to memory
[
https://issues.apache.org/jira/browse/WAGON-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lott updated WAGON-518:
-
Description:
Method putFromSteam in class AbstractHttpClientWagon seems to violate the
implied contract of working with streams. It uses much memory because it first
consumes the input stream argument, then transfers that content. The code that
consumes the stream is in the private class RequestEntityImplementation ctor:
{code:java}
byte[] bytes = IOUtil.toByteArray( stream );{code}
Please revise it, if possible, to behave more like the superclass StreamWagon's
putFromStream method, which does the transfer straight from the input stream.
We are attempting to PUT some 150MB artifacts in a java microservice that runs
with rather sharp memory limits. As a local workaround we increased the JVM's
-Xmx argument but that way lies madness.
Thanks in advance for any suggestions or workarounds.
was:
Method putFromSteam in class AbstractHttpClientWagon consumes much memory
because it first consumes the input stream argument, THEN transfers what it
read. The code that consumes the stream is in the private class
RequestEntityImplementation ctor:
{code:java}
byte[] bytes = IOUtil.toByteArray( stream );{code}
Please revise it, if possible, to behave more like the superclass StreamWagon's
putFromStream method, which does the transfer straight from the input stream.
We are attempting to PUT some 150MB artifacts in a java microservice that runs
with rather sharp memory limits. As a local workaround we increased the JVM's
-Xmx argument but that way lies madness.
Thanks in advance for any suggestions or workarounds.
> AbstractHttpClientWagon#putFromStream reads entire content to memory
>
>
> Key: WAGON-518
> URL: https://issues.apache.org/jira/browse/WAGON-518
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.12
>Reporter: Chris Lott
>Priority: Major
>
> Method putFromSteam in class AbstractHttpClientWagon seems to violate the
> implied contract of working with streams. It uses much memory because it
> first consumes the input stream argument, then transfers that content. The
> code that consumes the stream is in the private class
> RequestEntityImplementation ctor:
> {code:java}
> byte[] bytes = IOUtil.toByteArray( stream );{code}
> Please revise it, if possible, to behave more like the superclass
> StreamWagon's putFromStream method, which does the transfer straight from the
> input stream.
> We are attempting to PUT some 150MB artifacts in a java microservice that
> runs with rather sharp memory limits. As a local workaround we increased the
> JVM's -Xmx argument but that way lies madness.
> Thanks in advance for any suggestions or workarounds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (WAGON-518) AbstractHttpClientWagon#putFromStream reads entire content to memory
Chris Lott created WAGON-518:
Summary: AbstractHttpClientWagon#putFromStream reads entire
content to memory
Key: WAGON-518
URL: https://issues.apache.org/jira/browse/WAGON-518
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http
Affects Versions: 2.12
Reporter: Chris Lott
Method putFromSteam in class AbstractHttpClientWagon consumes much memory
because it first consumes the input stream argument, THEN transfers what it
read. The code that consumes the stream is in the private class
RequestEntityImplementation ctor:
{code:java}
byte[] bytes = IOUtil.toByteArray( stream );{code}
Please revise it, if possible, to behave more like the superclass StreamWagon's
putFromStream method, which does the transfer straight from the input stream.
We are attempting to PUT some 150MB artifacts in a java microservice that runs
with rather sharp memory limits. As a local workaround we increased the JVM's
-Xmx argument but that way lies madness.
Thanks in advance for any suggestions or workarounds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINVOKER-234) Upgrade maven-shared-utils to 3.2.1
[ https://issues.apache.org/jira/browse/MINVOKER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444239#comment-16444239 ] Hudson commented on MINVOKER-234: - Build succeeded in Jenkins: Maven TLP » maven-invoker-plugin » master #13 See https://builds.apache.org/job/maven-box/job/maven-invoker-plugin/job/master/13/ > Upgrade maven-shared-utils to 3.2.1 > --- > > Key: MINVOKER-234 > URL: https://issues.apache.org/jira/browse/MINVOKER-234 > Project: Maven Invoker Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-332) Changed download templates of plugins not to reference .md5 anymore
[
https://issues.apache.org/jira/browse/MNGSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444142#comment-16444142
]
Hudson commented on MNGSITE-332:
Build unstable in Jenkins: Maven TLP » maven-invoker » master #13
See https://builds.apache.org/job/maven-box/job/maven-invoker/job/master/13/
> Changed download templates of plugins not to reference .md5 anymore
> ---
>
> Key: MNGSITE-332
> URL: https://issues.apache.org/jira/browse/MNGSITE-332
> Project: Maven Project Web Site
> Issue Type: Task
>Reporter: Karl Heinz Marbaise
>Priority: Critical
>
> Currently we have links to md5 checksums for the plugin download pages this
> has to be changed into links to {{sha1}} and {{sha256}} instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCM-869) gitexe list() implemented incorrectly
[ https://issues.apache.org/jira/browse/SCM-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443880#comment-16443880 ] Chris Graham commented on SCM-869: -- I just checked the Jazz provider I wrote (and I looked at most of the others to see what they were actually doing). The Jazz provider does a remote file list, which is what the docs wanted. [https://www.ibm.com/support/knowledgecenter/SSYMRC_4.0.0/com.ibm.team.scm.doc/topics/list_remotefiles.html] > gitexe list() implemented incorrectly > - > > Key: SCM-869 > URL: https://issues.apache.org/jira/browse/SCM-869 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-gitexe >Affects Versions: 1.9.5, 1.9.6 >Reporter: Ilya Basin >Priority: Major > > Taking the Svn implementation as a model, ScmProvider.list() should be > implemented as follows: > * The command must directly query the remote repository for files > * A local working copy is unnecessary and if it doesn't exist, the remote > repository must not be checked out. > * fileSet.getBasedir() indicates where to run the scm binary. The > recommended value is ".". > * fileSet.getFileList() indicates the files to list > * repository indicates the repo URL > Git (among other SCMs) does not support listing remote files, so the command > should just fail. > For listing files in a working copy, users should call the > ScmProvider.status() method instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MSITE-812) Missing '/' in log when deploying documentation by site:stage
[
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443766#comment-16443766
]
Akira Ajisaka edited comment on MSITE-812 at 4/19/18 9:05 AM:
--
Thank you for your review, [~hboutemy]!
bq. what happens to "mvn site:stage
-DstagingDirectory=/Users/ajisaka/YARN-7736/" ?
The same. This is because the stagingDirectory is normalized by the following
source code.
{code:title=org/apache/maven/plugins/site/deploy/SiteStageMojo.java}
/**
* Staging directory location. This needs to be an absolute path, like
* C:\stagingArea\myProject\ on Windows or
* /stagingArea/myProject/ on Unix.
* If this is not specified, the site will be staged in
${project.build.directory}/staging.
*
* @since 2.3
*/
@Parameter( property = "stagingDirectory" )
private File stagingDirectory;
{code}
{code:title=java.io.File}
public File(String pathname) {
if (pathname == null) {
throw new NullPointerException();
}
this.path = fs.normalize(pathname);
this.prefixLength = fs.prefixLength(this.path);
}
{code}
Therefore, we don't need to check whether the staging directory ends with '/'
or not. Should I update the patch to use the utility
(AbstractDeployMojo#appendSlash) in case there are some changes in
stagingDirectory?
was (Author: ajisakaa):
bq. what happens to "mvn site:stage
-DstagingDirectory=/Users/ajisaka/YARN-7736/" ?
The same. This is because the stagingDirectory is normalized by the following
source code.
{code:title=org/apache/maven/plugins/site/deploy/SiteStageMojo.java}
/**
* Staging directory location. This needs to be an absolute path, like
* C:\stagingArea\myProject\ on Windows or
* /stagingArea/myProject/ on Unix.
* If this is not specified, the site will be staged in
${project.build.directory}/staging.
*
* @since 2.3
*/
@Parameter( property = "stagingDirectory" )
private File stagingDirectory;
{code}
{code:title=java.io.File}
public File(String pathname) {
if (pathname == null) {
throw new NullPointerException();
}
this.path = fs.normalize(pathname);
this.prefixLength = fs.prefixLength(this.path);
}
{code}
Therefore, we don't need to check whether the staging directory ends with '/'
or not. Should I update the patch to use the utility
(AbstractDeployMojo#appendSlash) in case there are some changes in
stagingDirectory?
> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}}
> {noformat}
> [INFO]
>
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSITE-812) Missing '/' in log when deploying documentation by site:stage
[
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443766#comment-16443766
]
Akira Ajisaka commented on MSITE-812:
-
bq. what happens to "mvn site:stage
-DstagingDirectory=/Users/ajisaka/YARN-7736/" ?
The same. This is because the stagingDirectory is normalized by the following
source code.
{code:title=org/apache/maven/plugins/site/deploy/SiteStageMojo.java}
/**
* Staging directory location. This needs to be an absolute path, like
* C:\stagingArea\myProject\ on Windows or
* /stagingArea/myProject/ on Unix.
* If this is not specified, the site will be staged in
${project.build.directory}/staging.
*
* @since 2.3
*/
@Parameter( property = "stagingDirectory" )
private File stagingDirectory;
{code}
{code:title=java.io.File}
public File(String pathname) {
if (pathname == null) {
throw new NullPointerException();
}
this.path = fs.normalize(pathname);
this.prefixLength = fs.prefixLength(this.path);
}
{code}
Therefore, we don't need to check whether the staging directory ends with '/'
or not. Should I update the patch to use the utility
(AbstractDeployMojo#appendSlash) in case there are some changes in
stagingDirectory?
> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}}
> {noformat}
> [INFO]
>
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #183: junit5
Tibor17 commented on issue #183: junit5 URL: https://github.com/apache/maven-surefire/pull/183#issuecomment-382634520 @marcphilipp Yes this is useful. I will analyze the dependencies in our code and I will try to use minimum conflicting dependencies. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
