[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389037#comment-16389037
]
Andrew Potter commented on SUREFIRE-1422:
-
I tried again with the latest version of alpine, and it looks like that
version's default ps fails on the -p flag instead of ignoring it. You can see
for yourself by running the container:
{code:java}
$ docker run -it alpine
/ # /bin/ps -o etime= -p 1
/bin/ps: unrecognized option: p
BusyBox v1.27.2 (2017-12-12 10:41:50 GMT) multi-call binary.
Usage: ps [-o COL1,COL2=HEADER]
Show list of processes
-o COL1,COL2=HEADER Select columns for display
/ #
/ # apk add --update procps
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
(1/6) Installing libintl (0.19.8.1-r1)
(2/6) Installing ncurses-terminfo-base (6.0_p20171125-r0)
(3/6) Installing ncurses-terminfo (6.0_p20171125-r0)
(4/6) Installing ncurses-libs (6.0_p20171125-r0)
(5/6) Installing libproc (3.3.12-r3)
(6/6) Installing procps (3.3.12-r3)
Executing busybox-1.27.2-r7.trigger
OK: 13 MiB in 17 packages
/ #
/ # /bin/ps -o etime= -p 1
00:18{code}
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389027#comment-16389027
]
Andrew Potter edited comment on SUREFIRE-1422 at 3/7/18 5:04 AM:
-
I tried with 2.21.0, but I also just ran `ps` on the image. -p is not
supported by the default ps, so the output was formatted differently before I
installed procps in the image. After installing procps, the ps output looked
correct. Downgrading to 2.19.1 fixed my builds for now.
was (Author: apottere):
I tried with 2.21.0, but I also just ran `ps` on the image. -p is not
supported by the default ps, so the output was formatted differently before I
installed procps in the image. After installing procps, the ps output looked
correct. Downgrading to 0.19.1 fixed my builds for now.
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389027#comment-16389027
]
Andrew Potter edited comment on SUREFIRE-1422 at 3/7/18 4:57 AM:
-
I tried with 2.21.0, but I also just ran `ps` on the image. -p is not
supported by the default ps, so the output was formatted differently before I
installed procps in the image. After installing procps, the ps output looked
correct. Downgrading to 0.19.1 fixed my builds for now.
was (Author: apottere):
I tried with 2.21.0, but I also just ran `ps` on the image. -p is not
supported by the default ps, so the output looked was formatted differently
before I installed procps in the image. After installing procps, the ps output
looked correct. Downgrading to 0.19.1 fixed my builds for now.
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389027#comment-16389027
]
Andrew Potter commented on SUREFIRE-1422:
-
I tried with 2.21.0, but I also just ran `ps` on the image. -p is not
supported by the default ps, so the output looked was formatted differently
before I installed procps in the image. After installing procps, the ps output
looked correct. Downgrading to 0.19.1 fixed my builds for now.
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388787#comment-16388787
]
Tibor Digana commented on SUREFIRE-1422:
[~apottere]
Did you try with Version {{2.21.0}}?
The command is {{/bin/ps -o etime= -p 123}}.
How it should be on alpine?
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1422) Forking fails on Linux if /bin/ps isn't available
[
https://issues.apache.org/jira/browse/SUREFIRE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388687#comment-16388687
]
Andrew Potter commented on SUREFIRE-1422:
-
I'm having the same problem as [~raehalme], default ps on alpine doesn't
support -p.
> Forking fails on Linux if /bin/ps isn't available
> -
>
> Key: SUREFIRE-1422
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1422
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1
> Environment: Linux (Debian 9 with OpenJDK 8)
>Reporter: Emmanuel Bourg
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> Hi,
> With the changes introduced by SUREFIRE-1302 I'm now experiencing a failure
> on Linux when the fork mode is enabled:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project foo: There are test failures.
> [ERROR]
> [ERROR] Please refer to /foo/target/surefire-reports for the individual test
> results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> {code}
> I traced the issue back to the PpidChecker class, the code assumes that
> {{/bin/ps}} or {{/usr/bin/ps}} exist but this isn't guaranteed (especially on
> trimmed down containers commonly used for continuous integration).
> It would be nice to have a fallback mechanism when ps isn't available, or at
> least check its existence and display an explicit message stating that it
> must be installed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MCOMPILER-205) maven-compiler-plugin: incremental compilation broken
[
https://issues.apache.org/jira/browse/MCOMPILER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388587#comment-16388587
]
ASF GitHub Bot commented on MCOMPILER-205:
--
monperrus commented on a change in pull request #3: [MCOMPILER-205] fixes
incremental compilation
URL:
https://github.com/apache/maven-compiler-plugin/pull/3#discussion_r172674360
##
File path:
src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java
##
@@ -750,36 +750,16 @@ else if (
CompilerConfiguration.CompilerReuseStrategy.ReuseSame.getStrategy().eq
IncrementalBuildHelperRequest incrementalBuildHelperRequest = null;
-if ( useIncrementalCompilation )
+if ( !useIncrementalCompilation )
{
getLog().debug( "useIncrementalCompilation enabled" );
Review comment:
good point! fixed.
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
> maven-compiler-plugin: incremental compilation broken
> -
>
> Key: MCOMPILER-205
> URL: https://issues.apache.org/jira/browse/MCOMPILER-205
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
>Reporter: Lukas Fryc
>Priority: Major
> Attachments: hello.tgz, ignore-package-info.patch,
> no-class-in-java-file.zip, only-recompile-changed.patch
>
>
> When we do {{clean}} -> {{compile}} -> {{compile}}, all Java sources are
> re-compiled for second compilation steps:
> {code}
> [framework]$ mvn clean
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> [framework]$ mvn compile
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @
> richfaces-framework ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 915 source files to
> /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
> ...
> {code}
> The source code of the affected project:
> https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] monperrus commented on a change in pull request #3: [MCOMPILER-205] fixes incremental compilation
monperrus commented on a change in pull request #3: [MCOMPILER-205] fixes
incremental compilation
URL:
https://github.com/apache/maven-compiler-plugin/pull/3#discussion_r172674360
##
File path:
src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java
##
@@ -750,36 +750,16 @@ else if (
CompilerConfiguration.CompilerReuseStrategy.ReuseSame.getStrategy().eq
IncrementalBuildHelperRequest incrementalBuildHelperRequest = null;
-if ( useIncrementalCompilation )
+if ( !useIncrementalCompilation )
{
getLog().debug( "useIncrementalCompilation enabled" );
Review comment:
good point! fixed.
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] [Commented] (MSHARED-696) Add missing Maven Version 3.5.2 to ArtifactDeployerTest
[ https://issues.apache.org/jira/browse/MSHARED-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388501#comment-16388501 ] Hudson commented on MSHARED-696: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #11 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/11/ > Add missing Maven Version 3.5.2 to ArtifactDeployerTest > --- > > Key: MSHARED-696 > URL: https://issues.apache.org/jira/browse/MSHARED-696 > 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: Minor > Fix For: maven-artifact-transfer-0.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-697) Add Maven Version 3.5.3 to all Integration tests after releasing Maven 3.5.3
Karl Heinz Marbaise created MSHARED-697: --- Summary: Add Maven Version 3.5.3 to all Integration tests after releasing Maven 3.5.3 Key: MSHARED-697 URL: https://issues.apache.org/jira/browse/MSHARED-697 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 Fix For: maven-artifact-transfer-0.10.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-696) Add missing maven version 3.5.2 to ArtifactDeployerTest
Karl Heinz Marbaise created MSHARED-696: --- Summary: Add missing maven version 3.5.2 to ArtifactDeployerTest Key: MSHARED-696 URL: https://issues.apache.org/jira/browse/MSHARED-696 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 Fix For: maven-artifact-transfer-0.10.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-696) Add missing Maven Version 3.5.2 to ArtifactDeployerTest
[ https://issues.apache.org/jira/browse/MSHARED-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-696: Summary: Add missing Maven Version 3.5.2 to ArtifactDeployerTest (was: Add missing maven version 3.5.2 to ArtifactDeployerTest) > Add missing Maven Version 3.5.2 to ArtifactDeployerTest > --- > > Key: MSHARED-696 > URL: https://issues.apache.org/jira/browse/MSHARED-696 > 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: Minor > Fix For: maven-artifact-transfer-0.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SUREFIRE-1495) Encoding of TXT report file should be configured by ${project.reporting.outputEncoding} and MOJO parameter encoding
Tibor Digana created SUREFIRE-1495:
--
Summary: Encoding of TXT report file should be configured by
${project.reporting.outputEncoding} and MOJO parameter encoding
Key: SUREFIRE-1495
URL: https://issues.apache.org/jira/browse/SUREFIRE-1495
Project: Maven Surefire
Issue Type: New Feature
Reporter: Tibor Digana
Assignee: Tibor Digana
Fix For: 3.0.0-M1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1490) Change header of the Failsafe Report
[ https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1490: --- Fix Version/s: 3.0.0-M1 > Change header of the Failsafe Report > > > Key: SUREFIRE-1490 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1490 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Report Plugin >Affects Versions: 2.20.1 >Reporter: Ivan Fedotov >Assignee: Tibor Digana >Priority: Minor > Fix For: 3.0.0-M1 > > > Hi! > I noted that the Failsafe Report's header is "Surefire Report", which is > quite confusing. > Can you fix this? > Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-695) Move checksum creation from install part to deploy part
Karl Heinz Marbaise created MSHARED-695: --- Summary: 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 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] [Closed] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHARED-656.
---
Resolution: Fixed
Done in
[7f700aab95d0e5dffbbf2b0c967c6582e8a0d557|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=7f700aab95d0e5dffbbf2b0c967c6582e8a0d557]
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-0.10.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
> Based on the usage of tools like Takari plugin testing we need to lift up the
> build requirements to JDK 8 minimum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388404#comment-16388404
]
Hudson commented on MSHARED-656:
Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #10
See
https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/10/
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
> Based on the usage of tools like Takari plugin testing we need to lift up the
> build requirements to JDK 8 minimum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SUREFIRE-1494) Make Provider surefire-junit47 default provider and deprecate surefire-junit4 Provider
Tibor Digana created SUREFIRE-1494: -- Summary: Make Provider surefire-junit47 default provider and deprecate surefire-junit4 Provider Key: SUREFIRE-1494 URL: https://issues.apache.org/jira/browse/SUREFIRE-1494 Project: Maven Surefire Issue Type: New Feature Reporter: Tibor Digana Fix For: 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SUREFIRE-1493) Maven Plugin API 3.0
Tibor Digana created SUREFIRE-1493: -- Summary: Maven Plugin API 3.0 Key: SUREFIRE-1493 URL: https://issues.apache.org/jira/browse/SUREFIRE-1493 Project: Maven Surefire Issue Type: New Feature Reporter: Tibor Digana Fix For: 3.0.0-M1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1466) Surefire fails on a dummy:dummy dependency with a authenticating proxy
[
https://issues.apache.org/jira/browse/SUREFIRE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1466:
---
Fix Version/s: (was: 3.0)
3.0.0-M1
> Surefire fails on a dummy:dummy dependency with a authenticating proxy
> --
>
> Key: SUREFIRE-1466
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1466
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.18.1, 2.20.1
> Environment: Stack traces with Maven 3.3.9, but also tried with latest
>Reporter: J.Cranendonk
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> We have a rather limited environment, internet is available through an
> authenticated proxy, and most things we get from a company nexus.
> Getting artifacts from either works fine, but it seems surefire does
> something fancy that breaks and ends in a ArtifactResolutionException
> regarding proxy authentication, related to a dummy:dummy artifact (which
> seems to be some hacky provider classpath resolving things in surefire?).
> Error message:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project BsnkInterfaceHandlerService: Unable to generate classpath:
> org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get
> dependency information for
> org.apache.maven.surefire:surefire-junit4:jar:2.18.1: Failed to retrieve POM
> for org.apache.maven.surefire:surefire-junit4:jar:2.18.1: Could not transfer
> artifact org.apache.maven.surefire:surefire-junit4:pom:2.18.1 from/to
> prog-sys-development (https:// to know :)>/nexus/content/groups/prog-sys-development): Not authorized by
> proxy , ReasonPhrase:authenticationrequired.
> [ERROR] org.apache.maven.surefire:surefire-junit4:jar:2.18.1
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] prog-sys-development (https:// want you to know :)>/nexus/content/groups/prog-sys-development,
> releases=true, snapshots=false)
> [ERROR] Path to dependency:
> [ERROR] 1) dummy:dummy:jar:1.0
> [ERROR] -> [Help 1]{noformat}
> Stack trace of the issue (first):
> {noformat}
> Thread [main] (Suspended (exception ArtifactResolutionException))
>
> DefaultArtifactCollector(DefaultLegacyArtifactCollector).recurse(ArtifactResolutionResult,
> ResolutionNode, Map>, ManagedVersionMap,
> ArtifactResolutionRequest, ArtifactMetadataSource, ArtifactFilter,
> List, List) line: 576
>
> DefaultArtifactCollector(DefaultLegacyArtifactCollector).collect(Set,
> Artifact, Map, ArtifactResolutionRequest,
> ArtifactMetadataSource, ArtifactFilter, List,
> List) line: 144
> DefaultArtifactResolver.resolve(ArtifactResolutionRequest) line: 493
> DefaultArtifactResolver.resolveWithExceptions(ArtifactResolutionRequest)
> line: 348
> DefaultArtifactResolver.resolveTransitively(Set, Artifact,
> Map, ArtifactRepository, List,
> ArtifactMetadataSource, ArtifactFilter, List,
> List) line: 342
> DefaultArtifactResolver.resolveTransitively(Set, Artifact,
> Map, ArtifactRepository, List,
> ArtifactMetadataSource, ArtifactFilter, List) line: 321
>
> DefaultArtifactResolver.resolveTransitively(Set, Artifact,
> Map, ArtifactRepository, List,
> ArtifactMetadataSource, ArtifactFilter) line: 286
> DefaultArtifactResolver.resolveTransitively(Set, Artifact,
> ArtifactRepository, List, ArtifactMetadataSource,
> ArtifactFilter) line: 261
> SurefireDependencyResolver.resolveArtifact(Artifact, Artifact) line: 125
>
> SurefireDependencyResolver.getProviderClasspath(String, String, Artifact)
> line: 140
> AbstractSurefireMojo$JUnit4ProviderInfo.getProviderClasspath() line: 2392
>
>
> SurefirePlugin(AbstractSurefireMojo).createStartupConfiguration(ProviderInfo,
> ClassLoaderConfiguration) line: 1473
> SurefirePlugin(AbstractSurefireMojo).createForkStarter(ProviderInfo,
> ForkConfiguration, ClassLoaderConfiguration, RunOrderParameters, Log) line:
> 1758
> SurefirePlugin(AbstractSurefireMojo).executeProvider(ProviderInfo,
> DefaultScanResult) line: 987
>
> SurefirePlugin(AbstractSurefireMojo).executeAfterPreconditionsChecked(DefaultScanResult)
> line: 824
> SurefirePlugin(AbstractSurefireMojo).execute() line: 722
> DefaultBuildPluginManager.executeMojo(MavenSession, MojoExecution) line:
> 134
> MojoExecutor.execute(MavenSession, MojoExecution, ProjectIndex,
> DependencyContext) line: 207
> MojoExecutor.execute(MavenSession, MojoExecution, ProjectIndex,
> DependencyContext, PhaseRecorder) line: 153
> MojoExecutor.execute(MavenSession, List, ProjectIndex)
> line: 145
>
[jira] [Updated] (SUREFIRE-1130) Remove TODO and deprecated code in surefire 3.0
[ https://issues.apache.org/jira/browse/SUREFIRE-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1130: --- Description: Resolve TODOs. Java 1.7 and similar related to 7. Resolve deprecated classes and methods. was: Resolve TODOs. Java 1.7 and similar related to 7. > Remove TODO and deprecated code in surefire 3.0 > --- > > Key: SUREFIRE-1130 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1130 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M1 > > > Resolve TODOs. > Java 1.7 and similar related to 7. > Resolve deprecated classes and methods. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1130) Remove TODO and deprecated code in surefire 3.0
[ https://issues.apache.org/jira/browse/SUREFIRE-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1130: --- Description: Resolve TODOs. Java 1.7 and similar related to 7. was: Resolve: //todo add @Override in surefire 3.0 running on the top of JDK 6 > Remove TODO and deprecated code in surefire 3.0 > --- > > Key: SUREFIRE-1130 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1130 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M1 > > > Resolve TODOs. > Java 1.7 and similar related to 7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1130) Remove TODO and deprecated code in surefire 3.0
[ https://issues.apache.org/jira/browse/SUREFIRE-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1130: --- Fix Version/s: (was: 3.0) 3.0.0-M1 > Remove TODO and deprecated code in surefire 3.0 > --- > > Key: SUREFIRE-1130 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1130 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M1 > > > Resolve: > //todo add @Override in surefire 3.0 running on the top of JDK 6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1365) Allow environment variables to be read from a file, instead of set as a Map
[ https://issues.apache.org/jira/browse/SUREFIRE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1365: --- Fix Version/s: (was: 3.0-RC1) > Allow environment variables to be read from a file, instead of set as a Map > --- > > Key: SUREFIRE-1365 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1365 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Darius Cooper >Assignee: Tibor Digana >Priority: Minor > Fix For: 3.0 > > > With 12-factors apps and deployment on platforms like OpenShift, there a new > push on using Environment Variables for configuration. When running > Integration tests with Failsafe, it would be nice to set the same variables > as will be set to the target environment. > Often, there's a file that contains the variables in a key-value pair format, > just like a properties file. It would be nice to be able to read that same > file in while setting environment variables for Failsafe and also when > deploying. > (There may be some type of simple file-formatting differences, but that's > typically easy to handle in an automated way.) > failsafe:integration-test supports an "environmentVariables" parameter. It > would nice if it could support an "environmentVariablesFile" parameter that > allowed a simple properties-style file to be read in an set as environment > variables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1384) Add ProviderInfo for JUnit Plattform to enable automatic provider lookup
[ https://issues.apache.org/jira/browse/SUREFIRE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1384: --- Fix Version/s: (was: 3.0-RC1) 3.0.0-M2 > Add ProviderInfo for JUnit Plattform to enable automatic provider lookup > > > Key: SUREFIRE-1384 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1384 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support >Reporter: Benedikt Ritter >Priority: Major > Fix For: 3.0.0-M2 > > > In order to enable automatic provider lookup for JUnit Plattform/JUnit 5, we > need to add the corresponding ProviderInfo implementation to > AbstractSurefireMojo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1331) Bump version number
[ https://issues.apache.org/jira/browse/SUREFIRE-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1331: --- Fix Version/s: (was: 3.0-RC1) 3.0.0-M2 > Bump version number > --- > > Key: SUREFIRE-1331 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1331 > Project: Maven Surefire > Issue Type: Task >Reporter: Benedikt Ritter >Priority: Major > Fix For: 3.0.0-M2 > > > Currently the version in 3.0-rc1 branch is 2.19.2-SNAPSHOT. We should bump it > to 3.0.0-SNAPSHOT. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1330) JUnit 5 surefire-provider code donation
[ https://issues.apache.org/jira/browse/SUREFIRE-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1330: --- Fix Version/s: (was: 3.0-RC1) 3.0.0-M2 > JUnit 5 surefire-provider code donation > --- > > Key: SUREFIRE-1330 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1330 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Benedikt Ritter >Assignee: Tibor Digana >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M2 > > Attachments: junit-platform-surefire-provider.zip > > > The JUnit team wishes to contribute their surefire provider implementation > for JUnit 5 to the Maven team. > The code is currently located at GitHub: > https://github.com/junit-team/junit5/tree/master/junit-platform-surefire-provider > They have recently relicensed the code under terms of Apache License 2.0: > https://github.com/junit-team/junit5/issues/541 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SUREFIRE-1214) Experimental SPI @ Java 1.6 as in-plugin process Extensions API
[ https://issues.apache.org/jira/browse/SUREFIRE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1214. -- Resolution: Won't Fix Fix Version/s: (was: 3.0-RC1) Another very simple mechanism should be used. Configuration parameter using: implements="impl class" > Experimental SPI @ Java 1.6 as in-plugin process Extensions API > --- > > Key: SUREFIRE-1214 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1214 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > > in-plugin process API should handle current MOJO execution and enable the > user to modify Tests Processor as well as ordering and filtering tests to be > executed afterwards in forked process. > This preprocessing is needed in other features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1213) MOJO pre-integration-test and post-integration-test
[ https://issues.apache.org/jira/browse/SUREFIRE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1213: --- Fix Version/s: (was: 3.0-RC1) Backlog > MOJO pre-integration-test and post-integration-test > --- > > Key: SUREFIRE-1213 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1213 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: Backlog > > > Introduce MOJO phase pre-integration-test and post-integration-test. > Introduce JSR 223 miscellaneous scriptables (BashShell, JavaScript, Nashorn). > The goal is to run environment setup and cleanup before/after integration > tests. > For the sake of Surefire build already requires JDK 6 (javac 1.5 still used) > these two MOJOs will be added as experimental implementations of Surefire 3.0 > which will be built on the top of Java 1.6. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-726) Test list preprocessor support for tests to be run
[ https://issues.apache.org/jira/browse/SUREFIRE-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-726: -- Fix Version/s: (was: 3.0-RC1) > Test list preprocessor support for tests to be run > -- > > Key: SUREFIRE-726 > URL: https://issues.apache.org/jira/browse/SUREFIRE-726 > Project: Maven Surefire > Issue Type: New Feature >Affects Versions: 2.9 >Reporter: Janmejay Singh >Priority: Major > Fix For: 3.0 > > Attachments: > 0001-Adds-test-list-preprocessor-support-which-loads-an-o.patch, > 0002-Integration-test-for-preprocessor.-2-modules-one-pro.patch, > 0003-exposed-testPreprocessor-configuration-parameter-as-.patch, > 0004-exposed-testPreprocessor-for-IntegrationTestMojo-as-.patch > > > This exposes an interface(named TestListPreprocessor, which has a method > named preprocessTestClasses) that can be implemented by a user and injected > into surefire plugin configuration to have it used for preprocessing list of > tests to be run. Given the original test list, user's preprocessing algorithm > can choose to prune or reorder the list and return it back from > TestListPreprocessor#preprocessTestClasses, which is then used as the list of > tests to be executed. > The patches attached expose a configuration element named "testPreprocessor" > the default value of which is "none". User can choose to set it to a value > matching the format > "[::]" and have > the class loaded and called with list of tests to be run. The list of tests > returned by the call is then considered for execution. > Patch description: > The feature is done in 2 patches. Description follows: > 0001-Adds-test-list-preprocessor-support-which-loads-an-o.patch > This patch actually adds the feature and unit tests. It adds the interface, > an abstraction that encapsulates aforementioned configuration, booter > serialization/deserialization, directory-scanner changes etc. The changes > have effect in both forked and in-process execution mode. > 0002-Integration-test-for-preprocessor.-2-modules-one-pro.patch > This patch adds an integration test for preprocessor feature. The integration > test uses a 2 module setup, where the first module implements the > TestListPreprocessor interface which selects only even indexed test classes > from the list passed in. The second module(which depends on first) uses the > artifact from first and uses the following configuration: > > > > test.preprocessor.EvenTestOnlyPreprocessor[org.apache.maven.plugins.surefire:preprocessor-impl:1.0-SNAPSHOT] > > > The test then asserts that only 2(0th and 2nd) of the 4 test classes the > second module has are executed. > The patches are created on a git-svn clone using format-patch, please use > 'patch -p1 < 0001-Adds...'(while in the trunk directory) to apply the patches > on svn repository. If using git-svn, git-am can be directly be invoked. > The patches are done over > http://svn.apache.org/repos/asf/maven/surefire/trunk@1091357 (trunk HEAD) so > should apply cleanly on any recent enough revision. > === > Context: > http://stackoverflow.com/questions/5124823/reducing-the-build-time-hudson > http://code.google.com/p/tlb/issues/detail?id=1 > http://test-load-balancer.github.com -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-701) showSuccess option for test reports: show reports only for failed tests
[ https://issues.apache.org/jira/browse/SUREFIRE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-701: -- Fix Version/s: (was: 3.0-RC1) 3.0 > showSuccess option for test reports: show reports only for failed tests > --- > > Key: SUREFIRE-701 > URL: https://issues.apache.org/jira/browse/SUREFIRE-701 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Affects Versions: 2.8 >Reporter: Alexander Klimetschek >Priority: Major > Fix For: 3.0 > > Attachments: showsuccess.patch > > > Use case: > When you have a few tests, and some of them fail during > development/refactoring, you find yourself repeatedly looking into > target/surefire-reports to open the test report (txt) files with the errors > and stack traces to analyze them. However, by default reports will be written > also for successful tests, and both in txt and xml format (the xml files can > already be omitted using disableXmlReport=false). This makes it hard to find > the files that contain the failed tests. > Solution proposal: > Just as the maven-surefire-report-plugin already has a showSuccess option, > that, if set to "false", will not report successful tests, the same should be > available for the maven-surefire-plugin and the normal test goal. > Either set "-DshowSuccess=false" on the command line or define > "false" in the maven-surefire-plugin configuration > of the pom, and reports for successful tests should not be written to the > reports directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-528) Splitting tests names in two categories : success and failure
[ https://issues.apache.org/jira/browse/SUREFIRE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-528: -- Fix Version/s: (was: 3.0-RC1) 3.0.0-M1 > Splitting tests names in two categories : success and failure > - > > Key: SUREFIRE-528 > URL: https://issues.apache.org/jira/browse/SUREFIRE-528 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Affects Versions: 2.0 (2.2 plugin) >Reporter: Emmanuel Lecharny >Priority: Major > Fix For: 3.0 > > > We have to check all the *.txt files to find the ones which contain some > errors. The fact that failed tests are listed before does not help a lot when > you have hundred of tests run with sometime lot of logs. > I would rather propose that we either create two sub-directories > (failure/success) or that we postfix tests. > A good example : > ... > Tests run: 197, Failures: 1, Errors: 0, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > Please refer to > /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports for the > individual test results. > ... > Would be better to have : > Please refer to > /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports/failure for > the individual test failures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-528) Splitting tests names in two categories : success and failure
[ https://issues.apache.org/jira/browse/SUREFIRE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-528: -- Fix Version/s: (was: 3.0.0-M1) 3.0 > Splitting tests names in two categories : success and failure > - > > Key: SUREFIRE-528 > URL: https://issues.apache.org/jira/browse/SUREFIRE-528 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Affects Versions: 2.0 (2.2 plugin) >Reporter: Emmanuel Lecharny >Priority: Major > Fix For: 3.0 > > > We have to check all the *.txt files to find the ones which contain some > errors. The fact that failed tests are listed before does not help a lot when > you have hundred of tests run with sometime lot of logs. > I would rather propose that we either create two sub-directories > (failure/success) or that we postfix tests. > A good example : > ... > Tests run: 197, Failures: 1, Errors: 0, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > Please refer to > /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports for the > individual test results. > ... > Would be better to have : > Please refer to > /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports/failure for > the individual test failures. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-526) Better support for other plugins to determine which tests are included/excluded and the order the tests get run
[ https://issues.apache.org/jira/browse/SUREFIRE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-526: -- Fix Version/s: (was: 3.0-RC1) > Better support for other plugins to determine which tests are > included/excluded and the order the tests get run > --- > > Key: SUREFIRE-526 > URL: https://issues.apache.org/jira/browse/SUREFIRE-526 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Nick Pellow >Priority: Major > Fix For: 3.0 > > > Currently, it is possible to provide the 'test' pattern to the > maven-surefire-plugin to include/exclude specific tests to be run. > This can be set on the MavenProject instance of any plugin which runs prior > to the surefire plugin. > Since this is just a pattern of tests to include, it has the following > shortcomings: > * To excludes a single test, you need to add _all_ tests, minus the test to > exclude > * The order of the test patterns is not used when the tests get run. > If there is no better means to control which tests get run and in which order > from outside the surefire plugin, how do you suggest this be achieved? > This may require changes to maven core to allow attributes > be set as well as Properties. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1474) Java 1.7 as minimum
[ https://issues.apache.org/jira/browse/SUREFIRE-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1474: --- Fix Version/s: (was: 3.0-RC1) 3.0.0-M1 > Java 1.7 as minimum > --- > > Key: SUREFIRE-1474 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1474 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1212) @Component is deprecated. @Parameter should be used instead.
[ https://issues.apache.org/jira/browse/SUREFIRE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1212: --- Fix Version/s: (was: 3.0-RC1) 3.0.0-M1 > @Component is deprecated. @Parameter should be used instead. > > > Key: SUREFIRE-1212 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1212 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M1 > > > From Maven Mailinglist > http://maven.40175.n5.nabble.com/maven-surefire-git-commit-SUREFIRE-refactoring-after-Sonar-report-td5856512.html > Hi Tibor, > just noticed this: > @Component > -protected MavenSession session; > +private MavenSession session; > could you make a @Parameter of it, because the @Component is deprecated. > See also https://issues.apache.org/jira/browse/MPLUGIN-257 > Actually, I would expect warnings from maven-plugin-plugin about this... > thanks, > Robert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SUREFIRE-1446) Isolated Classloader cant resolve JVM class w/o null constructor
[
https://issues.apache.org/jira/browse/SUREFIRE-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1446.
--
Resolution: Invalid
No response from the user after 3 months.
The class {{com.sun.xml.internal.ws.api.SOAPVersion}} is available in JDK8.
> Isolated Classloader cant resolve JVM class w/o null constructor
>
>
> Key: SUREFIRE-1446
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1446
> Project: Maven Surefire
> Issue Type: Test
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: mvn -version
> maven=3.3.3
> JAVA_HOME=JDK_1.8
>Reporter: Martin Gainty
>Assignee: Tibor Digana
>Priority: Blocker
> Attachments: RuntimeExceptionsAsyncMepTest.java
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> I need to load com.sun.xml.internal.ws.api.SOAPVersion which doesnt have null
> constructor
> surefire-plugin reflection methods cannot resolve the class e.g.
> {code}
> //LOAD in com.sun.xml.internal.ws.api.SOAPVersion into maven-surefire-plugin
> @Test
> java.lang.Class soapVersionClazz=null;
> ClassLoader soapVersionClassloader =
> com.sun.xml.internal.ws.api.SOAPVersion.class.getClassLoader();
> //always the case
> if(soapVersionClassloader==null) {
> soapVersionClassloader=Thread.currentThread().getContextClassLoader();
> }
> String soapVersionString="com.sun.xml.internal.ws.api.SOAPVersion";
> System.out.println("RuntimeExceptionsAsyncMepTest::getPort LNE 566
> soapVersionClassloader="+soapVersionClassloader);
> try {
> soapVersionClazz=soapVersionClassloader.loadClass(soapVersionString);
> }
> catch(ClassNotFoundException cnfe) {
> System.out.println("RuntimeExceptionsAsyncMepTest::getPort LINE 561 throws
> ClassNotFoundException message="+cnfe.getMessage());
> }
> System.out.println("RuntimeExceptionsAsyncMepTest::getPort LINE 564
> soapVersionClazz="+soapVersionClazz);
> com.sun.xml.internal.ws.api.SOAPVersion soapVersion =null;
> try {
>
> soapVersion=(com.sun.xml.internal.ws.api.SOAPVersion)soapVersionClazz.newInstance();
> }
> catch(InstantiationException iae) {
> System.out.println("RuntimeExceptionsAsyncMepTest::getPort LINE 572 throws
> InstantiationException message="+iae.getMessage());
> }
> catch(IllegalAccessException illegal) {
> System.out.println("RuntimeExceptionsAsyncMepTest::getPort LINE 573 throws
> IllegalAccessException message="+illegal.getMessage());
> }
> System.out.println("RuntimeExceptionsAsyncMepTest::getPort LINE 574
> soapVersion="+soapVersion);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6371) Use ServiceLoader mechanism in JDK9 in maven plugins
[
https://issues.apache.org/jira/browse/MNG-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388141#comment-16388141
]
Robert Scholte commented on MNG-6371:
-
We've tried to solve MNG-6275 for Maven 3.5.2, but didn't succeed. With the way
Maven works with ClassLoaders it is not that straight forward. Still looking
for the right solution.
> Use ServiceLoader mechanism in JDK9 in maven plugins
>
>
> Key: MNG-6371
> URL: https://issues.apache.org/jira/browse/MNG-6371
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading, Plugins and Lifecycle
>Affects Versions: 3.5.2
>Reporter: John Poth
>Priority: Major
>
> It'd be nice to be able to use the ServiceLoader mechanism in maven plugins
> when using JDK9:
>
> {code:java}
> import org.apache.maven.plugin.AbstractMojo;
> public class MyMojo extends AbstractMojo {
> public void execute() throws MojoExecutionException {
> // this is empty
> Iterator iterator =
> ServiceLoader.load(javax.tools.Tool.class).iterator();
> }
> }
> {code}
>
> Work around is to use a different classloader.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6371) Use ServiceLoader mechanism in JDK9 in maven plugins
John Poth created MNG-6371:
--
Summary: Use ServiceLoader mechanism in JDK9 in maven plugins
Key: MNG-6371
URL: https://issues.apache.org/jira/browse/MNG-6371
Project: Maven
Issue Type: Improvement
Components: Class Loading, Plugins and Lifecycle
Affects Versions: 3.5.2
Reporter: John Poth
It'd be nice to be able to use the ServiceLoader mechanism in maven plugins
when using JDK9:
{code:java}
import org.apache.maven.plugin.AbstractMojo;
public class MyMojo extends AbstractMojo {
public void execute() throws MojoExecutionException {
// this is empty
Iterator iterator =
ServiceLoader.load(javax.tools.Tool.class).iterator();
}
}
{code}
Work around is to use a different classloader.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-132) Drop parameter 'medium'
[
https://issues.apache.org/jira/browse/MPH-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387749#comment-16387749
]
Hudson commented on MPH-132:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #14
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/14/
> Drop parameter 'medium'
> ---
>
> Key: MPH-132
> URL: https://issues.apache.org/jira/browse/MPH-132
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Based on MPH-31, this parameter adds no real value given that we have
> {{minimal}} and {{detail}}. Drop it to reduce complexity.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-134) Drop deprecated alias 'mojo'
[
https://issues.apache.org/jira/browse/MPH-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387747#comment-16387747
]
Hudson commented on MPH-134:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #14
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/14/
> Drop deprecated alias 'mojo'
>
>
> Key: MPH-134
> URL: https://issues.apache.org/jira/browse/MPH-134
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{goal}} ago. Time to remove the alias along
> with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-133) Drop deprecated alias 'full'
[
https://issues.apache.org/jira/browse/MPH-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387748#comment-16387748
]
Hudson commented on MPH-133:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #14
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/14/
> Drop deprecated alias 'full'
>
>
> Key: MPH-133
> URL: https://issues.apache.org/jira/browse/MPH-133
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{detail}} ago. Time to remove the alias
> along with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPH-134) Drop deprecated alias 'mojo'
[
https://issues.apache.org/jira/browse/MPH-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPH-134.
--
Resolution: Fixed
Fixed with
[e6a088c25f18588411c572e26c8e74f84786905e|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commit;h=e6a088c25f18588411c572e26c8e74f84786905e].
> Drop deprecated alias 'mojo'
>
>
> Key: MPH-134
> URL: https://issues.apache.org/jira/browse/MPH-134
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{goal}} ago. Time to remove the alias along
> with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPH-133) Drop deprecated alias 'full'
[
https://issues.apache.org/jira/browse/MPH-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPH-133.
--
Resolution: Fixed
Fixed with
[acf04d512752798938dc824ef51bb4d1e3cd587f|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commit;h=acf04d512752798938dc824ef51bb4d1e3cd587f].
> Drop deprecated alias 'full'
>
>
> Key: MPH-133
> URL: https://issues.apache.org/jira/browse/MPH-133
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{detail}} ago. Time to remove the alias
> along with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPH-132) Drop parameter 'medium'
[
https://issues.apache.org/jira/browse/MPH-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPH-132.
--
Resolution: Fixed
Fixed with
[cf84fc3c8b5927a29c3931b3382afe30ccacaaa9|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commit;h=cf84fc3c8b5927a29c3931b3382afe30ccacaaa9].
> Drop parameter 'medium'
> ---
>
> Key: MPH-132
> URL: https://issues.apache.org/jira/browse/MPH-132
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Based on MPH-31, this parameter adds no real value given that we have
> {{minimal}} and {{detail}}. Drop it to reduce complexity.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6370) ConcurrencyDependencyGraph#getNumberOfBuilds() does not remove finished projects from unfinished ones
[
https://issues.apache.org/jira/browse/MNG-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387544#comment-16387544
]
ASF GitHub Bot commented on MNG-6370:
-
Github user michael-o commented on the issue:
https://github.com/apache/maven/pull/161
@slachiewicz I am ready to merge, @rfscholte [requested a unit
test](https://www.mail-archive.com/dev@maven.apache.org/msg116360.html). Can
you add one and I will merge it with a smile=
> ConcurrencyDependencyGraph#getNumberOfBuilds() does not remove finished
> projects from unfinished ones
> -
>
> Key: MNG-6370
> URL: https://issues.apache.org/jira/browse/MNG-6370
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.2, 3.5.3
>Reporter: Sylwester Lachiewicz
>Assignee: Michael Osipov
>Priority: Trivial
> Fix For: 3.5.4-candidate
>
>
> Fix _ConcurrencyDependencyGraph.getUnfinishedProjects_
> {code:java}
> private final HashSet finishedProjects = new HashSet<>();
> /**
> * @return set of projects that have yet to be processed successfully by the
> build.
> */
> public Set getUnfinishedProjects()
> {
> Set unfinished = new HashSet<>( projectBuilds.getProjects() );
> unfinished.remove( finishedProjects );
> return unfinished;
> }{code}
> replace _remove()_ with _removeAll()_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
