[jira] [Commented] (SUREFIRE-1261) surefire hangs of failed tests and keeps lock on surefirebooter on Windows preventing clean
[
https://issues.apache.org/jira/browse/SUREFIRE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15518369#comment-15518369
]
Tibor Digana commented on SUREFIRE-1261:
[~hohwille]
[~joerg.hohwil...@sdm.de]
[~jo...@j-hohwiller.de]
Have you tried to follow my advice with {{kill}} ?
> surefire hangs of failed tests and keeps lock on surefirebooter on Windows
> preventing clean
> ---
>
> Key: SUREFIRE-1261
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1261
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.17, 2.19.1
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\project\software\maven
> Java version: 1.8.0_66, vendor: Oracle Corporation
> Java home: C:\project\software\java\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"
>Reporter: Jörg Hohwiller
>Assignee: Tibor Digana
>
> I have Spring-Tests run with surefire in a plain commandline maven build on
> windows. For whatever reason many tests fail with spring initialization
> exception. If I cancel the build in this case ([ctrl][c]) and then restart a
> clean build maven failes to delete the target directory. Using sysinternal
> tools I traced down that a java.exe process is hanging that locks a JAR
> called surefirebooter located in target. This is IMHO the forked process from
> the maven surefire plugin that was not terminated properly when the maven
> process was cancelled.
> You might need to register a shutdown hook in maven-surefire that properly
> cleans up the forked process. But this is just a brute guess...
> http://stackoverflow.com/questions/17465117/maven-surefirebooter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6090) CI friendly properties break submodule builds
[
https://issues.apache.org/jira/browse/MNG-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517083#comment-15517083
]
Mirko Friedenhagen commented on MNG-6090:
-
Hello [~hwellmann],
* I created a sample project (at https://gitlab.com/mfriedenhagen/mng6090/) and
could reproduce the behavior, see:
https://gitlab.com/mfriedenhagen/mng6090/pipelines/4355078. There are two CI
jobs which firstly {{install}} all modules and then try to verify s2 alone
(called "first all, then only s2").
> CI friendly properties break submodule builds
> -
>
> Key: MNG-6090
> URL: https://issues.apache.org/jira/browse/MNG-6090
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9
>Reporter: Harald Wellmann
>
> h3. Scenario
> A multi-module project where the parent version is one of the CI friendly
> properties, e.g. $\{revision\} as outlined in
> http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/.
> There are two submodules submodule1 and submodule2 such that submodule2
> depends on submodule1.
> h3. Expected behaviour
> Each submodule can be built by itself, e.g.
> {code}
> mvn clean install -Drevision=1.0.0-SNAPSHOT -pl submodule2
> {code}
> or
> {code}
> cd submodule2; mvn clean install -Drevision=1.0.0-SNAPSHOT
> {code}
> h3. Actual behaviour
> This does not work for submodule2 or in general any module that depends on a
> module from the same reactor.
> Maven cannot resolve the property variable in the referenced parent POM
> version and fails the build:
> {code}
> [ERROR] Failed to execute goal on project submodule2: Could not resolve
> dependencies for project com.example:submodule2:jar:1.0.0-SNAPSHOT: Failed to
> collect dependencies at com.example:submodule1:jar:1.0.0-SNAPSHOT: Failed to
> read artifact descriptor for com.example:submodule1:jar:1.0.0-SNAPSHOT: Could
> not find artifact com.exammple:parent:pom:${revision} -> [Help 1]
> {code}
>
> There is no problem building submodule1 or the entire reactor.
> Same problem observed with a local build from master (3.4.0-SNAPSHOT).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-6095) mvn script warns on Solaris
[
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516645#comment-15516645
]
Christian Schulte commented on MNG-6095:
This issue should have been fixed on master already. Can you please test a
recent 3.4.0-SNAPSHOT available from
[here|https://builds.apache.org/view/All/job/maven-3.3-release-status-build/]
and report if those messages disappear.
> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Priority: Minor
> Labels: solaris
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation SunOS 5.11 11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local:
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local:
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MJAVADOC-387) Handle JDK8 -Xdoclint
[
https://issues.apache.org/jira/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516457#comment-15516457
]
Stian Soiland-Reyes commented on MJAVADOC-387:
--
Any progress on this?
I must agree that it's not very good of Oracle to have added an activated
default which must be disabled with a (previously unknown) "nonstandard option".
The use of Maven activation profiles is not a good workaround. So I would go
with Tubbs' solution - default is as-is, and a new
{{whatever}} will add {{-Xdoclint:whatever}} without any
validation. There can be a special recognition of {{none}}
which means {{-Xdoclint:none}} on JDK 8++ but nothing on JDK 7--. Use of any
other {{}} in pre-Java 8 should log a warning (not be bluntly passed
as -Xdoclint). {{}} can be equivalent to {{-Xdoclint}} - the
arbitrarily selected profile built in to the Javadoc distro.
I don't know what the behaviour should be for non-Oracle / non-OpenJDK javadoc
which may not hava doclint - but at least with a special option it's possible
to fix that generally in the javadoc plugin as opposed to the use of profiles
and {{additionalparam}}.
> Handle JDK8 -Xdoclint
> -
>
> Key: MJAVADOC-387
> URL: https://issues.apache.org/jira/browse/MJAVADOC-387
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
>Reporter: scolebourne2
>
> The Oracle team have added the doclint tool to JDK 8. The tool validates
> Javadoc as part of a standard Javadoc run. Unfortunately, with the default
> settings, it rejects many HTML elements that are perfectly acceptable to
> browsers, and all invalid Javadoc references (@links). This is likely to
> prove very unpopular with developers.
> Action needed:
> 1) Provide a maven-javadoc-plugin configuration item and property that can
> control the doclint tool (currently this requires using additionalparam
> AFAICT).
> 2) Apply the {{-Xdoclint:none}} option by default, so that doclint is opt-in,
> not opt-out (ie. fix Oracle's messed up default). This will also make it much
> easier for developers to handle migration to JDK 8.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6095) mvn script warns on Solaris
[
https://issues.apache.org/jira/browse/MNG-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Mashkov updated MNG-6095:
Description:
I can see warnings at every build complaining about local
{noformat}
local: not found [No such file or directory]
{noformat}
See full excerpt
{noformat}
sol ❯ vagrant ssh
Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
Oracle Corporation SunOS 5.11 11.3September 2015
vagrant@solaris:~$ mvn --version
/export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local: not
found [No such file or directory]
/export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local: not
found [No such file or directory]
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T11:41:47-05:00)
Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
Java version: 1.8.0_60, vendor: Oracle Corporation
Java home: /usr/jdk/instances/jdk1.8.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
{noformat}
However it looks like it doesn't cause any real issues
was:
I can see warnings at every build complaining about local
{noformat}
local: not found [No such file or directory]
{noformat}
See full excerpt
{noformat}
sol ❯ vagrant ssh
⏎
Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
Oracle Corporation SunOS 5.11 11.3September 2015
vagrant@solaris:~$ mvn --version
/export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local: not
found [No such file or directory]
/export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local: not
found [No such file or directory]
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T11:41:47-05:00)
Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
Java version: 1.8.0_60, vendor: Oracle Corporation
Java home: /usr/jdk/instances/jdk1.8.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
{noformat}
However it looks like it doesn't cause any real issues
> mvn script warns on Solaris
> ---
>
> Key: MNG-6095
> URL: https://issues.apache.org/jira/browse/MNG-6095
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.3.9
> Environment: Solaris 11.3, ksh 93u, maven 3.3.9
>Reporter: Sergey Mashkov
>Priority: Minor
> Labels: solaris
>
> I can see warnings at every build complaining about local
> {noformat}
> local: not found [No such file or directory]
> {noformat}
> See full excerpt
> {noformat}
> sol ❯ vagrant ssh
> Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
> Oracle Corporation SunOS 5.11 11.3September 2015
> vagrant@solaris:~$ mvn --version
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local:
> not found [No such file or directory]
> /export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local:
> not found [No such file or directory]
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /usr/jdk/instances/jdk1.8.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
> {noformat}
> However it looks like it doesn't cause any real issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MNG-6095) mvn script warns on Solaris
Sergey Mashkov created MNG-6095:
---
Summary: mvn script warns on Solaris
Key: MNG-6095
URL: https://issues.apache.org/jira/browse/MNG-6095
Project: Maven
Issue Type: Bug
Components: Command Line
Affects Versions: 3.3.9
Environment: Solaris 11.3, ksh 93u, maven 3.3.9
Reporter: Sergey Mashkov
Priority: Minor
I can see warnings at every build complaining about local
{noformat}
local: not found [No such file or directory]
{noformat}
See full excerpt
{noformat}
sol ❯ vagrant ssh
⏎
Last login: Fri Sep 23 07:56:07 2016 from 10.0.2.2
Oracle Corporation SunOS 5.11 11.3September 2015
vagrant@solaris:~$ mvn --version
/export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[200]: local: not
found [No such file or directory]
/export/home/vagrant/.sdkman/candidates/maven/current/bin/mvn[201]: local: not
found [No such file or directory]
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T11:41:47-05:00)
Maven home: /export/home/vagrant/.sdkman/candidates/maven/current
Java version: 1.8.0_60, vendor: Oracle Corporation
Java home: /usr/jdk/instances/jdk1.8.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "sunos", version: "5.11", arch: "amd64", family: "unix"
{noformat}
However it looks like it doesn't cause any real issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
