[jira] [Assigned] (MJAVADOC-585) Incorrect quoting and escaping of nonProxyHosts-information from settings.xml
[
https://issues.apache.org/jira/browse/MJAVADOC-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MJAVADOC-585:
---
Assignee: (was: Michael Osipov)
> Incorrect quoting and escaping of nonProxyHosts-information from settings.xml
> -
>
> Key: MJAVADOC-585
> URL: https://issues.apache.org/jira/browse/MJAVADOC-585
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.1.0
> Environment: Maven 3.6.0 on RHEL 7.6 using OpenJDK 1.8.9.191 and
> Bash; Maven 3.6.0 on Windows 7 using Oracle JDK 8 Update 201 and Windows-CMD
>Reporter: Paul Busch
>Priority: Major
> Fix For: next-release
>
>
> At my development site, I am behind a proxy server. That proxy server is
> configured in my {{settings.xml}} in a corresponding
> {{proxies/proxy}}-section.
> For site-deployments I use an internal server named {{my-site-host}}.
> To bypass the proxy for access to {{my-site-host}} and several other hosts in
> the local network, there is a {{nonProxyHosts}}-element in the
> proxy-configuration-section of my {{settings.xml}} which looks like this:
> {code:java}
> my-site-host|my-nexus-host
> {code}
> In an internal project {{linking-project,}} which uses a class {{LinkTarget}}
> from another internal project {{link-target}} in its API, I would like to
> have the class {{LinkTarget}} in the Javadocs of project {{linking-project}}
> to be displayed as links to the Javadocs of project {{link-target}}. The
> Javadocs of project {{link-target}} are published on {{my-site-host}} as part
> of a maven-site. To achieve the linking I have configured the
> {{maven-javadoc-plugin}} in {{linking-project}} as follows:
> {code:java}
>
>
> http://my-site-host/link-target/0.1.0-SNAPSHOT/apidocs
>
>
> {code}
> When the report {{javadoc:javadoc}} or the goal {{javadoc:jar}} is executed
> during the build, I get the following warning:
> {code:java}
> [WARNING] javadoc: warning - Error fetching URL:
> http://my-site-host/link-target/0.1.0-SNAPSHOT/apidocs/
> {code}
> As a result, class {{LinkTarget}} in the generated Javadocs is displayed with
> its fully qualified class name and not as a link. The expected behavior would
> be class {{LinkTarget}} being displayed using its local name only and with an
> underlying link to the Javadocs of that class. The problem occurs on both
> Linux and Windows.
> The problem also occurs when executing the {{javadoc.(sh|bat)}} script, which
> is generated in {{target/site/apidocs}} when {{-Ddebug=true}} is used (on
> Linux using Bash; on Windows using Windows-CMD).
> The problem seems to be in the handling of the {{nonProxyHosts}}-information
> from the {{settings.xml}} in {{AbstractJavadocMojo}}. In method
> {{addProxyArg(Commandline)}} this information is (in two places) handled as
> follows:
> {code:java}
> cmd.createArg().setValue( "-J-Dhttp.nonProxyHosts=\""
> + httpProxy.getNonProxyHosts().replace( "|", "^|" ) + "\"" );
> {code}
> When the report/goal is executed, the {{Commandline}}-object is delegated to
> {{CommandLineUtils.executeCommandLine(...)}} which in the end delegates to
> the {{javadoc}}-program using {{Runtime.exec(...)}}. {{Runtime.exec(...)}} is
> fed the command line parts as an array of Strings and apparently does not
> need any quoting and escaping. When looking at it in a debugger the
> {{nonProxyHosts}}-information – escaped with the code above – is passed to
> the {{javadoc}}-program as
> {{"-J-Dhttp.nonProxyHosts=\"my-site-host^|my-nexus-host\""}}. I guess this
> value is split by the {{javadoc}}-program at the pipe symbol, resulting in
> {{"my-site-host^}} and {{my-nexus-host"}} as the two host names. Thus the
> {{javadoc}}-program bypasses the proxy for the nonexisting/nonsense host name
> {{"my-site-host^}} (with a leading quote and a trailing caret) but uses the
> proxy for the actual host {{my-site-host}} causing the malfuntion and the
> warning.
> For the sake of the report/goal-execution the above code could be fixed as
> follows:
> {code:java}
> cmd.createArg().setValue( "-J-Dhttp.nonProxyHosts=" +
> httpProxy.getNonProxyHosts() );
> {code}
> i.e. no quoting and no escaping of pipe symbols.
> This code change albeit completely breaks the generated
> {{javadoc.(sh|bat)}}-scripts generated in {{target/site/apidocs}} with
> {{-Ddebug=true}}. While {{Runtime.exec(...)}} *must not* have quoting and
> escaping, Windows-CMD and Bash, for which the scripts are generated, *need*
> special handling. Otherwise the pipe symbols in {{nonProxyHosts}} will be
> interpreted as redirection of output to the input of another program.
> The following aspects need to be observed regarding the generation of
[jira] [Closed] (SUREFIRE-1464) Failsafe plugin exposes slf4j-jdk14 dependency
[
https://issues.apache.org/jira/browse/SUREFIRE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1464.
--
Resolution: Fixed
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=8109b4ff96775a42e397ea549feb36a21f1ba5ec
> Failsafe plugin exposes slf4j-jdk14 dependency
> --
>
> Key: SUREFIRE-1464
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1464
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, JUnit 5.x support, Maven Failsafe Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 Pro
> Oracle Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T09:58:13+02:00)
>Reporter: Frank Seidinger
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> I'm testing a spring-boot application using current spring-boot-startet
> When running the integration tests I get the following output from SLF4J:
> {{SLF4J: The requested version 1.5.6 by your slf4j binding is not compatible
> with [1.6, 1.7]}}
> And afterwords a lot of {{AbstracMethodError}} failures. Here is one example:
> {noformat}
> java.lang.AbstractMethodError:
> org.slf4j.impl.JDK14LoggerAdapter.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> {noformat}
> The version 1.5.6 reported by SLF4J is not any dependency of my project but a
> direct dependency of the maven-failsafe-plugin, whereas my project uses slf4j
> 1.7.22.
> The relevant dependencies reported by {{mvn dependency:tree -Dverbose
> -Dscope=test}} are:
> {noformat}
> [INFO] +- org.axonframework:axon-core:jar:3.1:compile
> [INFO] | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed from
> 1.7.22; omitted for duplicate)
> [INFO] | +- com.thoughtworks.xstream:xstream:jar:1.4.9:compile
> [INFO] | \- xpp3:xpp3:jar:1.1.4c:compile
> [INFO] +- org.springframework:spring-core:jar:4.3.13.RELEASE:compile
> [INFO] | \- commons-logging:commons-logging:jar:1.2:compile
> [INFO] +-
> org.springframework.boot:spring-boot-starter-data-jpa:jar:1.5.9.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.5.9.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | \-
> (org.springframework:spring-context:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.5.9.RELEASE:compile
> [INFO] | | | \-
> (org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.5.9.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.11:compile
> [INFO] | | | | +- ch.qos.logback:logback-core:jar:1.1.11:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.25:compile
> [INFO] | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | +- (org.springframework:spring-core:jar:4.3.13.RELEASE:compile -
> omitted for duplicate)
> [INFO] | | \- org.yaml:snakeyaml:jar:1.17:runtime
> [INFO] | +-
> org.springframework.data:spring-data-jpa:jar:1.11.9.RELEASE:compile
> [INFO] | | +-
> org.springframework.data:spring-data-commons:jar:1.13.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed
> from 1.7.22; omitted for duplicate)
> [INFO] | | | \- (org.slf4j:jcl-over-slf4j:jar:1.7.25:runtime - omitted for
> duplicate)
> [INFO] | | +- org.springframework:spring-orm:jar:4.3.13.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | |
[jira] [Commented] (MNG-6725) Skip '.mavenrc' via MAVEN_SKIP_RC=1 and '-Dmaven.skip.rc=true' on child ITs (by default on Jenkins CI).
[
https://issues.apache.org/jira/browse/MNG-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914289#comment-16914289
]
Hudson commented on MNG-6725:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6695 #2
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6695/2/
> Skip '.mavenrc' via MAVEN_SKIP_RC=1 and '-Dmaven.skip.rc=true' on child ITs
> (by default on Jenkins CI).
> ---
>
> Key: MNG-6725
> URL: https://issues.apache.org/jira/browse/MNG-6725
> Project: Maven
> Issue Type: Task
> Components: Integration Tests
> Environment: ASF Jenkins CI
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
>
> This is related to the problem with MAVEN_OPTS.
> If Jenkins has global '.mavenrc' then the environment variables are merged
> with local ones and applied in Maven JVM which is controlled by
> $MVN_HOME/bin/mvn
> If you want to isolate the JVM from global '.mavenrc', you have to set
> environment variable to non-zero length value, i.e. MAVEN_SKIP_RC=1.
> This commit controls skipping '.mavenrc' in
> {{AbstractMavenIntegrationTestCase}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MNG-6731) Jetty getLocalPort() returns -1 resulting in build failures
[
https://issues.apache.org/jira/browse/MNG-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914290#comment-16914290
]
Hudson commented on MNG-6731:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6695 #2
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6695/2/
> Jetty getLocalPort() returns -1 resulting in build failures
> ---
>
> Key: MNG-6731
> URL: https://issues.apache.org/jira/browse/MNG-6731
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We observed sporadic errors [1] fir the project {{core-its}} on Jenkins.
> So I started haveing a look and I say the JavaDoc of the method
> {{getlocalPort}} saying that {{-1}} is returned if the connector is not open.
> So I decided to use [2] and wait until the server is up. This was of course
> wrong because the status of the server is set to {{STARTED}} immediatelly
> after the method {{Server.start()}}. So therefore I was googling a little bit
> and I found that Hadoop [3] had this problem too in 2010. Whole problem was
> with a bug in Jetty server which is {{race condition}}. The article has a
> link to Jetty's Jira with reported bug {{JETTY-748}}. According to the
> annoucements [4] from Eclipse/Jetty, the bug "{{JETTY-748 Prevent race close
> of socket by old acceptor threads}}" was fixed in the version
> {{jetty-7.2.1.v2010}}. So I decided to use that version but I found that
> the class {{HashUserRealm}} was deleted and there is no support and no
> further development of {{org.mortbay}}. Eclipse continues with the
> development of Jerry 9.
> All I did in this issue was to rewrite 38 integration tests to Jetty 9 API
> and the fix for {{JETTY-748}} is right there.
> [1]:
> Error message in logs: [WARNING] Could not transfer metadata
> org.apache.maven.its.mng4554/maven-metadata.xml from/to central
> (http://localhost:-1/repo-1): Connect to localhost:80 [localhost/127.0.0.1,
> localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect
> [2]:
> {code:java}
> while ( !server.isRunning() || !server.isStarted() )
> {
> if ( server.isFailed() )
> {
> fail( "Couldn't bind the server socket to a free port!" );
> }
> Thread.sleep( 100L );
> }
> {code}
> [3]:
> https://www.bountysource.com/issues/987313-jetty-returns-1-resulting-in-hadoop-masters-slaves-to-fail-during-startup
> [4]:
> https://www.eclipse.org/lists/jetty-dev/msg00537.html
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MNG-6720) MultiThreadedBuilder: wait for parallel running projects when using --fail-fast
[ https://issues.apache.org/jira/browse/MNG-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914288#comment-16914288 ] Hudson commented on MNG-6720: - Build succeeded in Jenkins: Maven TLP » maven » MNG-6695 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6695/2/ > MultiThreadedBuilder: wait for parallel running projects when using > --fail-fast > --- > > Key: MNG-6720 > URL: https://issues.apache.org/jira/browse/MNG-6720 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.5.4, 3.6.1 >Reporter: Stefan Oehme >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.2 > > Time Spent: 40m > Remaining Estimate: 0h > > When a project fails using --fail-fast mode, other projects that are > currently running in parallel are not finished before the "session finished" > event is sent. This leads to issues for extensions that rely on the > documented order of events, which says that "session finished" is only sent > "after all projects have been finished/skipped". > In our case, we close a service on "session finished", and that service is > needed to execute goals. The goals that were running in parallel at that time > then fail, saying that our service was closed, giving our users the > impression that there is a bug in our code. > The relevant line is > [here|https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/internal/builder/multithreaded/MultiThreadedBuilder.java#L179]. > Instead of using `poll`, which simply returns when the parallel projects > aren't finished yet, the code should shut down the executor and wait for it > to complete the outstanding parallel work. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (MINDEXER-123) Fix an InputStream leak in indexer-reader Utils
[
https://issues.apache.org/jira/browse/MINDEXER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914100#comment-16914100
]
Hudson commented on MINDEXER-123:
-
Build succeeded in Jenkins: Maven TLP » maven-indexer » master #20
See https://builds.apache.org/job/maven-box/job/maven-indexer/job/master/20/
> Fix an InputStream leak in indexer-reader Utils
> ---
>
> Key: MINDEXER-123
> URL: https://issues.apache.org/jira/browse/MINDEXER-123
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Stephen Buergler
>Priority: Trivial
>
> There is a leak of an InputReader in Utils.
> {code:java}
> /**
> * Creates and loads {@link Properties} from provided {@link Resource} if
> exists, and closes the resource. If not
> * exists, returns {@code null}.
> */
> public static Properties loadProperties( final Resource resource )
> throws IOException
> {
> final InputStream inputStream = resource.read();
> if ( inputStream == null )
> {
> return null;
> }
> return loadProperties( resource.read() );
> }
> {code}
> Depending on how the Resource is implemented this probably leaks the
> InputStream returned by the first .read() call. I'm under the understanding
> that .read() should return a new InputStream every time it is called but I
> don't have any evidence that that is true other than that's how the Resource
> in the unit test is implemented.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [maven] Tibor17 commented on issue #262: [MNG-6695] Improve speed in collection merging
Tibor17 commented on issue #262: [MNG-6695] Improve speed in collection merging URL: https://github.com/apache/maven/pull/262#issuecomment-524252280 In one hand this may speed up performace but on the second hand it will consume more memory because these three variables represent a cache: https://github.com/apache/maven/pull/262/commits/bb86cccb83011a381fcbe8ad556e2c3f2915ec5b#diff-8a011471e51290138c022976dea0d55fR2789 What's the lifecycle of these objects and when are they freed? Did we make any measurements on big projects? This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven] Tibor17 commented on issue #262: [MNG-6695] Improve speed in collection merging
Tibor17 commented on issue #262: [MNG-6695] Improve speed in collection merging URL: https://github.com/apache/maven/pull/262#issuecomment-524247725 Can we use this fix in the release 3.6.2? This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven] michael-o commented on issue #262: [MNG-6695] Improve speed in collection merging
michael-o commented on issue #262: [MNG-6695] Improve speed in collection merging URL: https://github.com/apache/maven/pull/262#issuecomment-524247908 @hboutemy. Is that OK for you if all passes? This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (MNG-6695) Improve speed in collection merging
[ https://issues.apache.org/jira/browse/MNG-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6695: Fix Version/s: 3.6.x-candidate 3.6.2 > Improve speed in collection merging > --- > > Key: MNG-6695 > URL: https://issues.apache.org/jira/browse/MNG-6695 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.6.1 >Reporter: Guillaume Nodet >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.2, 3.6.x-candidate > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (MNG-6695) Improve speed in collection merging
[ https://issues.apache.org/jira/browse/MNG-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-6695: --- Assignee: Michael Osipov > Improve speed in collection merging > --- > > Key: MNG-6695 > URL: https://issues.apache.org/jira/browse/MNG-6695 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.6.1 >Reporter: Guillaume Nodet >Assignee: Michael Osipov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [maven] michael-o commented on issue #262: [MNG-6695] Improve speed in collection merging
michael-o commented on issue #262: [MNG-6695] Improve speed in collection merging URL: https://github.com/apache/maven/pull/262#issuecomment-524244571 I have now pushed a rebased and squashed branch to GitBox. Waiting for Jekins to run the jobs... This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [Assigned] (SUREFIRE-1584) Rerun Failing Tests with JUnit 5
[ https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1584: -- Assignee: Tibor Digana > Rerun Failing Tests with JUnit 5 > > > Key: SUREFIRE-1584 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1584 > Project: Maven Surefire > Issue Type: New Feature > Components: JUnit 5.x support, Maven Surefire Report Plugin >Affects Versions: 2.22.0 >Reporter: Tic Tac >Assignee: Tibor Digana >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M4 > > Attachments: FlakyReruns.png > > > The very useful feature for integration tests ¨[Rerun Failing > Tests|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]¨ > is currently only supported for the very outdated JUnit 4. > The documentation says: ¨This feature is supported only for JUnit 4.x.¨ > Can you please support this feature for JUnit 5.3 or later? -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SUREFIRE-1584) Rerun Failing Tests with JUnit 5
[ https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1584: --- Fix Version/s: 3.0.0-M4 > Rerun Failing Tests with JUnit 5 > > > Key: SUREFIRE-1584 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1584 > Project: Maven Surefire > Issue Type: New Feature > Components: JUnit 5.x support, Maven Surefire Report Plugin >Affects Versions: 2.22.0 >Reporter: Tic Tac >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M4 > > Attachments: FlakyReruns.png > > > The very useful feature for integration tests ¨[Rerun Failing > Tests|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]¨ > is currently only supported for the very outdated JUnit 4. > The documentation says: ¨This feature is supported only for JUnit 4.x.¨ > Can you please support this feature for JUnit 5.3 or later? -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (SUREFIRE-1688) Junit Platform test with failing @BeforeAll does not fail the build
[
https://issues.apache.org/jira/browse/SUREFIRE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914062#comment-16914062
]
Tibor Digana edited comment on SUREFIRE-1688 at 8/23/19 8:50 AM:
-
[~Brand]
This is probably old status of 3.0.0-SNAPSHOT.
Can you provide a pull-request with integration test (a new method
{{testBeforeAllFailed}})?
See the class {{JUnitPlatformIT}}.
I think the test will fail as expected.
was (Author: tibor17):
[~Brand]
This is probably old status of 3.0.0-SNAPSHOT.
Can you provide a pull-request with integration test (a new method
{{testBeforeAllFailed}})?
See the class {{JUnitPlatformIT}}.
I think the will fail as expected.
> Junit Platform test with failing @BeforeAll does not fail the build
> ---
>
> Key: SUREFIRE-1688
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1688
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Reporter: Guy Brand
>Priority: Major
>
> When using Surefire {{3.0.0-SNAPSHOT}} and JUnit Platform {{5.4.2}} the
> following test does not fail the Maven build.
> {code:java}
> import org.junit.jupiter.api.Test;
> import org.junit.jupiter.api.BeforeAll;
> import org.junit.jupiter.api.Assertions;
> public class Tests {
> @BeforeAll
> public static void beforeAll() { Assertions.fail("BeforeAll fail"); }
> @Test
> public void test() { Assertions.fail("Test fail"); }
> }
> {code}
> And its output:
> {code}
> [INFO] --- maven-surefire-plugin:3.0.0-SNAPSHOT:test (default-test) @
> top-level-project ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running Tests
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015
> s - in Tests
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {code}
> When removing the {{@BeforeAll}} annotation/method it fails as expected.
> {{3.0.0-M3}} version of Surefire works as expected:
> {code}
> [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
> top-level-project ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running Tests
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.008
> s <<< FAILURE! - in Tests
> [ERROR] Tests Time elapsed: 0.007 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: BeforeAll fail
> at Tests.beforeAll(Tests.java:7)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] Tests.beforeAll:7 BeforeAll fail
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.373 s
> [INFO] Finished at: 2019-08-20T16:20:16+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test)
> on project top-level-project: There are test failures.
> {code}
> For all the tests Maven 3.6.1 has been used.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (SUREFIRE-1688) Junit Platform test with failing @BeforeAll does not fail the build
[
https://issues.apache.org/jira/browse/SUREFIRE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914062#comment-16914062
]
Tibor Digana commented on SUREFIRE-1688:
[~Brand]
This is probably old status of 3.0.0-SNAPSHOT.
Can you provide a pull-request with integration test (a new method
{{testBeforeAllFailed}})?
See the class {{JUnitPlatformIT}}.
I think the will fail as expected.
> Junit Platform test with failing @BeforeAll does not fail the build
> ---
>
> Key: SUREFIRE-1688
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1688
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Reporter: Guy Brand
>Priority: Major
>
> When using Surefire {{3.0.0-SNAPSHOT}} and JUnit Platform {{5.4.2}} the
> following test does not fail the Maven build.
> {code:java}
> import org.junit.jupiter.api.Test;
> import org.junit.jupiter.api.BeforeAll;
> import org.junit.jupiter.api.Assertions;
> public class Tests {
> @BeforeAll
> public static void beforeAll() { Assertions.fail("BeforeAll fail"); }
> @Test
> public void test() { Assertions.fail("Test fail"); }
> }
> {code}
> And its output:
> {code}
> [INFO] --- maven-surefire-plugin:3.0.0-SNAPSHOT:test (default-test) @
> top-level-project ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running Tests
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015
> s - in Tests
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {code}
> When removing the {{@BeforeAll}} annotation/method it fails as expected.
> {{3.0.0-M3}} version of Surefire works as expected:
> {code}
> [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
> top-level-project ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running Tests
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.008
> s <<< FAILURE! - in Tests
> [ERROR] Tests Time elapsed: 0.007 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: BeforeAll fail
> at Tests.beforeAll(Tests.java:7)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] Tests.beforeAll:7 BeforeAll fail
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.373 s
> [INFO] Finished at: 2019-08-20T16:20:16+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test)
> on project top-level-project: There are test failures.
> {code}
> For all the tests Maven 3.6.1 has been used.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (SUREFIRE-1464) Failsafe plugin exposes slf4j-jdk14 dependency
[
https://issues.apache.org/jira/browse/SUREFIRE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914051#comment-16914051
]
Tibor Digana commented on SUREFIRE-1464:
[~fseidinger]
[~jonbell]
Sorry for this issue, there is a fix and the build is currently running.
https://builds.apache.org/job/maven-box/job/maven-surefire/job/SUREFIRE-1464/
> Failsafe plugin exposes slf4j-jdk14 dependency
> --
>
> Key: SUREFIRE-1464
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1464
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, JUnit 5.x support, Maven Failsafe Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 Pro
> Oracle Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T09:58:13+02:00)
>Reporter: Frank Seidinger
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> I'm testing a spring-boot application using current spring-boot-startet
> When running the integration tests I get the following output from SLF4J:
> {{SLF4J: The requested version 1.5.6 by your slf4j binding is not compatible
> with [1.6, 1.7]}}
> And afterwords a lot of {{AbstracMethodError}} failures. Here is one example:
> {noformat}
> java.lang.AbstractMethodError:
> org.slf4j.impl.JDK14LoggerAdapter.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> {noformat}
> The version 1.5.6 reported by SLF4J is not any dependency of my project but a
> direct dependency of the maven-failsafe-plugin, whereas my project uses slf4j
> 1.7.22.
> The relevant dependencies reported by {{mvn dependency:tree -Dverbose
> -Dscope=test}} are:
> {noformat}
> [INFO] +- org.axonframework:axon-core:jar:3.1:compile
> [INFO] | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed from
> 1.7.22; omitted for duplicate)
> [INFO] | +- com.thoughtworks.xstream:xstream:jar:1.4.9:compile
> [INFO] | \- xpp3:xpp3:jar:1.1.4c:compile
> [INFO] +- org.springframework:spring-core:jar:4.3.13.RELEASE:compile
> [INFO] | \- commons-logging:commons-logging:jar:1.2:compile
> [INFO] +-
> org.springframework.boot:spring-boot-starter-data-jpa:jar:1.5.9.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.5.9.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | \-
> (org.springframework:spring-context:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.5.9.RELEASE:compile
> [INFO] | | | \-
> (org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.5.9.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.11:compile
> [INFO] | | | | +- ch.qos.logback:logback-core:jar:1.1.11:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.25:compile
> [INFO] | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | +- (org.springframework:spring-core:jar:4.3.13.RELEASE:compile -
> omitted for duplicate)
> [INFO] | | \- org.yaml:snakeyaml:jar:1.17:runtime
> [INFO] | +-
> org.springframework.data:spring-data-jpa:jar:1.11.9.RELEASE:compile
> [INFO] | | +-
> org.springframework.data:spring-data-commons:jar:1.13.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed
> from 1.7.22; omitted for duplicate)
> [INFO] | | | \- (org.slf4j:jcl-over-slf4j:jar:1.7.25:runtime - omitted for
> duplicate)
> [INFO] | | +- org.springframework:spring-orm:jar:4.3.13.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
>
[jira] [Assigned] (SUREFIRE-1464) Failsafe plugin exposes slf4j-jdk14 dependency
[
https://issues.apache.org/jira/browse/SUREFIRE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1464:
--
Assignee: Tibor Digana
> Failsafe plugin exposes slf4j-jdk14 dependency
> --
>
> Key: SUREFIRE-1464
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1464
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, JUnit 5.x support, Maven Failsafe Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 Pro
> Oracle Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T09:58:13+02:00)
>Reporter: Frank Seidinger
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> I'm testing a spring-boot application using current spring-boot-startet
> When running the integration tests I get the following output from SLF4J:
> {{SLF4J: The requested version 1.5.6 by your slf4j binding is not compatible
> with [1.6, 1.7]}}
> And afterwords a lot of {{AbstracMethodError}} failures. Here is one example:
> {noformat}
> java.lang.AbstractMethodError:
> org.slf4j.impl.JDK14LoggerAdapter.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> {noformat}
> The version 1.5.6 reported by SLF4J is not any dependency of my project but a
> direct dependency of the maven-failsafe-plugin, whereas my project uses slf4j
> 1.7.22.
> The relevant dependencies reported by {{mvn dependency:tree -Dverbose
> -Dscope=test}} are:
> {noformat}
> [INFO] +- org.axonframework:axon-core:jar:3.1:compile
> [INFO] | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed from
> 1.7.22; omitted for duplicate)
> [INFO] | +- com.thoughtworks.xstream:xstream:jar:1.4.9:compile
> [INFO] | \- xpp3:xpp3:jar:1.1.4c:compile
> [INFO] +- org.springframework:spring-core:jar:4.3.13.RELEASE:compile
> [INFO] | \- commons-logging:commons-logging:jar:1.2:compile
> [INFO] +-
> org.springframework.boot:spring-boot-starter-data-jpa:jar:1.5.9.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.5.9.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | \-
> (org.springframework:spring-context:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.5.9.RELEASE:compile
> [INFO] | | | \-
> (org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.5.9.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.11:compile
> [INFO] | | | | +- ch.qos.logback:logback-core:jar:1.1.11:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.25:compile
> [INFO] | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | +- (org.springframework:spring-core:jar:4.3.13.RELEASE:compile -
> omitted for duplicate)
> [INFO] | | \- org.yaml:snakeyaml:jar:1.17:runtime
> [INFO] | +-
> org.springframework.data:spring-data-jpa:jar:1.11.9.RELEASE:compile
> [INFO] | | +-
> org.springframework.data:spring-data-commons:jar:1.13.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed
> from 1.7.22; omitted for duplicate)
> [INFO] | | | \- (org.slf4j:jcl-over-slf4j:jar:1.7.25:runtime - omitted for
> duplicate)
> [INFO] | | +- org.springframework:spring-orm:jar:4.3.13.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-jdbc:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
>
[jira] [Updated] (SUREFIRE-1464) Failsafe plugin exposes slf4j-jdk14 dependency
[
https://issues.apache.org/jira/browse/SUREFIRE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1464:
---
Fix Version/s: 3.0.0-M4
> Failsafe plugin exposes slf4j-jdk14 dependency
> --
>
> Key: SUREFIRE-1464
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1464
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, JUnit 5.x support, Maven Failsafe Plugin
>Affects Versions: 2.19.1
> Environment: Windows 10 Pro
> Oracle Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T09:58:13+02:00)
>Reporter: Frank Seidinger
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> I'm testing a spring-boot application using current spring-boot-startet
> When running the integration tests I get the following output from SLF4J:
> {{SLF4J: The requested version 1.5.6 by your slf4j binding is not compatible
> with [1.6, 1.7]}}
> And afterwords a lot of {{AbstracMethodError}} failures. Here is one example:
> {noformat}
> java.lang.AbstractMethodError:
> org.slf4j.impl.JDK14LoggerAdapter.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> {noformat}
> The version 1.5.6 reported by SLF4J is not any dependency of my project but a
> direct dependency of the maven-failsafe-plugin, whereas my project uses slf4j
> 1.7.22.
> The relevant dependencies reported by {{mvn dependency:tree -Dverbose
> -Dscope=test}} are:
> {noformat}
> [INFO] +- org.axonframework:axon-core:jar:3.1:compile
> [INFO] | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed from
> 1.7.22; omitted for duplicate)
> [INFO] | +- com.thoughtworks.xstream:xstream:jar:1.4.9:compile
> [INFO] | \- xpp3:xpp3:jar:1.1.4c:compile
> [INFO] +- org.springframework:spring-core:jar:4.3.13.RELEASE:compile
> [INFO] | \- commons-logging:commons-logging:jar:1.2:compile
> [INFO] +-
> org.springframework.boot:spring-boot-starter-data-jpa:jar:1.5.9.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.5.9.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | \-
> (org.springframework:spring-context:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.5.9.RELEASE:compile
> [INFO] | | | \-
> (org.springframework.boot:spring-boot:jar:1.5.9.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.5.9.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.11:compile
> [INFO] | | | | +- ch.qos.logback:logback-core:jar:1.1.11:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.25:compile
> [INFO] | | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.25:compile
> [INFO] | | | \- (org.slf4j:slf4j-api:jar:1.7.25:compile - version
> managed from 1.7.22; omitted for duplicate)
> [INFO] | | +- (org.springframework:spring-core:jar:4.3.13.RELEASE:compile -
> omitted for duplicate)
> [INFO] | | \- org.yaml:snakeyaml:jar:1.17:runtime
> [INFO] | +-
> org.springframework.data:spring-data-jpa:jar:1.11.9.RELEASE:compile
> [INFO] | | +-
> org.springframework.data:spring-data-commons:jar:1.13.9.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +- (org.slf4j:slf4j-api:jar:1.7.25:compile - version managed
> from 1.7.22; omitted for duplicate)
> [INFO] | | | \- (org.slf4j:jcl-over-slf4j:jar:1.7.25:runtime - omitted for
> duplicate)
> [INFO] | | +- org.springframework:spring-orm:jar:4.3.13.RELEASE:compile
> [INFO] | | | +-
> (org.springframework:spring-beans:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-core:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | +-
> (org.springframework:spring-jdbc:jar:4.3.13.RELEASE:compile - omitted for
> duplicate)
> [INFO] | | | \-
