[jira] [Commented] (SUREFIRE-1304) VM crash when using reportsDirectory pointing to parent module and maven parallel build
[
https://issues.apache.org/jira/browse/SUREFIRE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900732#comment-15900732
]
Tibor Digana commented on SUREFIRE-1304:
[~davidj-okta]
If this issue appears you see no tests executes like this?
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> VM crash when using reportsDirectory pointing to parent module and maven
> parallel build
> ---
>
> Key: SUREFIRE-1304
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1304
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
> Environment: windows 7 x86 64
>Reporter: Jérôme Van Der Linden
>Assignee: Tibor Digana
>Priority: Critical
> Fix For: Backlog
>
>
> In my parent pom, i've configured the surefire plugin with
> {{$\{basedir}/../surefire-reports}}
> So that all reports go to the parent folder (i have one parent module with n
> submodules just below). I need to centralize all reports from all modules in
> order to use another tool on them.
> If i do this and use *mvn -T 1C* to use parallel build, i have the following
> error :
> {{The forked VM terminated without saying properly goodbye. VM crash or
> System.exit called}}
> If i remove the reportsDirectory, no more problem, but all reports stay in
> submodules... I could use an ant task to copy files at the end of tests but
> it sucks...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1340) add a kind of progress status to surefire output
[
https://issues.apache.org/jira/browse/SUREFIRE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900727#comment-15900727
]
Tibor Digana commented on SUREFIRE-1340:
[~romain.manni-bucau]
You mean JUnit Suite.class?
This requires investigating events coming from junit's {{RunListener}} if
descriptions of child test classes within the suite are fired. If not, then
this feature has no chance.
What if the child tests are running in parallel and what if suites are jvm
forks are running in parallel?
> add a kind of progress status to surefire output
>
>
> Key: SUREFIRE-1340
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1340
> Project: Maven Surefire
> Issue Type: New Feature
>Reporter: Romain Manni-Bucau
>
> ATM surefire executes tests but for big suites no way to know where we are in
> the execution exactly. What about adding a kind of line prefix showing it:
> {code}
> [124/1254] normal output
> [124/1254] another normal output
> [126/1254] another normal output after 2 tests finished
> ...
> {code}
> This would at least allow to know where we are. Idea would be to have a
> counter in the "executor" and just show it when there is something on
> stdout/stderr.
> Of course it will require a new configuration flag to activate it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MJAR-233) What happened to finalName?!
[ https://issues.apache.org/jira/browse/MJAR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900056#comment-15900056 ] Karl Heinz Marbaise commented on MJAR-233: -- Please use the users list for such questions and not JIRA! > What happened to finalName?! > > > Key: MJAR-233 > URL: https://issues.apache.org/jira/browse/MJAR-233 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.0.2 >Reporter: Matthew >Assignee: Robert Scholte > > I've updated my maven-jar-plugin from 2.6 to 3.0.2 and it no longer supports > the jar.finalName property. There's no mention of it in the documents either. > There's some clue in the code that it's been renamed "maven.jar.finalName" > but this doesn't seem to work for me (nor is it documented on the webpage). > Am I missing something? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MJAR-233) What happened to finalName?!
[ https://issues.apache.org/jira/browse/MJAR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900046#comment-15900046 ] Bikramjit Singh commented on MJAR-233: -- Hi [~khmarbaise] can you please point me to how do I give finalName for different jar files in assembly-plugin Thanks > What happened to finalName?! > > > Key: MJAR-233 > URL: https://issues.apache.org/jira/browse/MJAR-233 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.0.2 >Reporter: Matthew >Assignee: Robert Scholte > > I've updated my maven-jar-plugin from 2.6 to 3.0.2 and it no longer supports > the jar.finalName property. There's no mention of it in the documents either. > There's some clue in the code that it's been renamed "maven.jar.finalName" > but this doesn't seem to work for me (nor is it documented on the webpage). > Am I missing something? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MDEP-557) In dependency analysis, support Spring Boot style intentional transitive compile-time dependencies
M. Justin created MDEP-557:
--
Summary: In dependency analysis, support Spring Boot style
intentional transitive compile-time dependencies
Key: MDEP-557
URL: https://issues.apache.org/jira/browse/MDEP-557
Project: Maven Dependency Plugin
Issue Type: New Feature
Components: analyze
Reporter: M. Justin
Priority: Minor
h1. Request
It would be useful if using Spring Boot "starter" dependencies as intended
didn't cause warnings with dependency:analyze (and related goals).
h1. Background
Spring Boot has a notion of "starter" dependencies. One of the primary
purposes of starter dependencies is to transitively bring in numerous other
dependencies to be used at both runtime and compile time. Per [Spring Boot's
documentation|http://docs.spring.io/spring-boot/docs/1.5.1.RELEASE/reference/htmlsingle/#using-boot-starter]:
{quote}
Starters are a set of convenient dependency descriptors that you can include in
your application. You get a one-stop-shop for all the Spring and related
technology that you need, without having to hunt through sample code and copy
paste loads of dependency descriptors. For example, if you want to get started
using Spring and JPA for database access, just include the
spring-boot-starter-data-jpa dependency in your project, and you are good to go.
The starters contain a lot of the dependencies that you need to get a project
up and running quickly and with a consistent, supported set of managed
transitive dependencies.
{quote}
However, this is at odds with the analysis done by
[dependency:analyze|https://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html]
(and similar goals in the dependency plugin). The analyze goals will warn
that the starter projects are "unused declared dependencies" and any
compile-time dependencies that are transitively brought in this way will
produce "used undeclared dependencies" warnings. Note that this warning
behavior is consistent with the [Maven dependency
documentation|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope]
where it states that it is intended that all compile dependencies be
explicitly listed, rather than transitively used at compile time:
{quote}it is intended that \[transitive compile dependencies\] should be
runtime scope instead, so that all compile dependencies must be explicitly
listed - however, there is the case where the library you depend on extends a
class from another library, forcing you to have available at compile time. For
this reason, compile time dependencies remain as compile scope even when they
are transitive.{quote}
As a concrete example, here are the warnings generated by {{mvn
dependency:analyze}} on Spring Boot's own "[Getting
Started|https://spring.io/guides/gs/spring-boot/]"; example:
{code}Used undeclared dependencies found:
org.springframework:spring-web:jar:4.3.6.RELEASE:compile
org.springframework.boot:spring-boot-test:jar:1.5.1.RELEASE:test
org.springframework.boot:spring-boot-test-autoconfigure:jar:1.5.1.RELEASE:test
org.springframework:spring-test:jar:4.3.6.RELEASE:test
org.springframework.boot:spring-boot:jar:1.5.1.RELEASE:compile
org.hamcrest:hamcrest-library:jar:1.3:test
org.springframework:spring-context:jar:4.3.6.RELEASE:compile
junit:junit:jar:4.12:test
org.springframework.boot:spring-boot-autoconfigure:jar:1.5.1.RELEASE:compile
org.springframework:spring-beans:jar:4.3.6.RELEASE:compile
Unused declared dependencies found:
org.springframework.boot:spring-boot-starter-web:jar:1.5.1.RELEASE:compile
org.springframework.boot:spring-boot-starter-test:jar:1.5.1.RELEASE:test
org.springframework.boot:spring-boot-starter-actuator:jar:1.5.1.RELEASE:compile{code}
My initial thought was that perhaps Spring Boot was misuing the Maven
dependency mechanism through their approach, however that is not their
interpretation (see the discussion at
[spring-boot#8341|https://github.com/spring-projects/spring-boot/issues/8341]).
So, assuming I'm interpreting things correctly, it seems like the thought is
that Spring Boot's usage of dependencies is A-OK. Given this, and the impact
of Spring Boot in the Java ecosystem, it seems like it would be good for there
to be support for this pattern within Maven's dependency analysis. I'm not
sure what the most appropriate mechanism for this would be, however (and
whether the dependency plugin is the primary place it should be supported). Is
this just something that should be configurable within the dependency:analyze
plugin itself? Are the starter dependencies a new class of dependency that
should be called out within Maven? Is this something where the starter
dependency should be able to declare that its compile-time dependencies are
meant to be exported and directly used?
h1. Workaround
The obv
[jira] [Commented] (MCOMPILER-290) Fix invalid comment out in the examples of the module-info documentation
[
https://issues.apache.org/jira/browse/MCOMPILER-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899282#comment-15899282
]
ASF GitHub Bot commented on MCOMPILER-290:
--
GitHub user aajisaka opened a pull request:
https://github.com/apache/maven-plugins/pull/106
[MCOMPILER-290] Fix invalid comment out in the examples of module-info
documentation
* Add missing `-->` in module-info.apt.vm.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aajisaka/maven-plugins MCOMPILER-290
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-plugins/pull/106.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #106
commit 99099a04e4e8ccc8c5fa7530b928c02889b2598e
Author: Akira Ajisaka
Date: 2017-03-07T11:19:45Z
[MCOMPILER-290] Fix invalid comment out in the examples of module-info
documentation
> Fix invalid comment out in the examples of the module-info documentation
>
>
> Key: MCOMPILER-290
> URL: https://issues.apache.org/jira/browse/MCOMPILER-290
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Reporter: Akira Ajisaka
>Priority: Minor
>
> Missing {{-->}} in the following comment.
> {code}
>
[jira] [Updated] (MCOMPILER-290) Fix invalid comment out in the examples of the module-info documentation
[
https://issues.apache.org/jira/browse/MCOMPILER-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated MCOMPILER-290:
Summary: Fix invalid comment out in the examples of the module-info
documentation (was: Invalid comment in the examples of the module-info
documentation)
> Fix invalid comment out in the examples of the module-info documentation
>
>
> Key: MCOMPILER-290
> URL: https://issues.apache.org/jira/browse/MCOMPILER-290
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Reporter: Akira Ajisaka
>Priority: Minor
>
> Missing {{-->}} in the following comment.
> {code}
>
[jira] [Created] (MCOMPILER-290) Invalid comment in the examples of the module-info documentation
Akira Ajisaka created MCOMPILER-290:
---
Summary: Invalid comment in the examples of the module-info
documentation
Key: MCOMPILER-290
URL: https://issues.apache.org/jira/browse/MCOMPILER-290
Project: Maven Compiler Plugin
Issue Type: Bug
Reporter: Akira Ajisaka
Priority: Minor
Missing {{-->}} in the following comment.
{code}
