[jira] (MANTRUN-98) multiple input tasks leads to exception
[
https://jira.codehaus.org/browse/MANTRUN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353466#comment-353466
]
Christophe DENEUX commented on MANTRUN-98:
--
I have just encountered this issue with Maven version 3.1.1:
> multiple input tasks leads to exception
> ---
>
> Key: MANTRUN-98
> URL: https://jira.codehaus.org/browse/MANTRUN-98
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.3
> Environment: 32-bit Linux, Sun JDK 1.6.0_07, Maven 2.0.9
>Reporter: Andy Schlaikjer
>
> Running more than one task within Antrun plugin causes exception:
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> Please enter test-value-01 [123]
> Please enter test-value-02 [456]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An Ant BuildException has occured: Failed to read input from Console.
> Stream closed
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException
> has occured: Failed to read input from Console.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant
> BuildException has occured: Failed to read input from Console.
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: Failed to read input from Console.
> at
> org.apache.tools.ant.input.DefaultInputHandler.handleInput(DefaultInputHandler.java:59)
> at org.apache.tools.ant.taskdefs.Input.execute(Input.java:231)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:118)
> ... 19 more
> Caused by: java.io.IOException: Stream closed
> at
> java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:308)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
> at
[jira] (MANTRUN-98) multiple input tasks leads to exception
[
https://jira.codehaus.org/browse/MANTRUN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353466#comment-353466
]
Christophe DENEUX edited comment on MANTRUN-98 at 9/30/14 3:33 AM:
---
I have just encountered this issue with Maven version 3.1.1:
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
17:22:22+0200)
Java version: 1.7.0_65, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-i386/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux" (Ubuntu 14.04 uptodate), version: "3.13.0-36-generic", arch:
"i386", family: "unix"
was (Author: cdeneux):
I have just encountered this issue with Maven version 3.1.1:
> multiple input tasks leads to exception
> ---
>
> Key: MANTRUN-98
> URL: https://jira.codehaus.org/browse/MANTRUN-98
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.3
> Environment: 32-bit Linux, Sun JDK 1.6.0_07, Maven 2.0.9
>Reporter: Andy Schlaikjer
>
> Running more than one task within Antrun plugin causes exception:
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> Please enter test-value-01 [123]
> Please enter test-value-02 [456]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An Ant BuildException has occured: Failed to read input from Console.
> Stream closed
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException
> has occured: Failed to read input from Console.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant
> BuildException has occured: Failed to read input from Console.
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: Failed to read input from Console.
> at
> org.apache.tools.ant.input.DefaultInputHandler.handleInput(DefaultInputHandler.java:59)
> at org.apache.tools.ant.taskdefs.Input.execute(Input.java:231)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(Abstra
[jira] (MANTRUN-98) multiple input tasks leads to exception
[
https://jira.codehaus.org/browse/MANTRUN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353466#comment-353466
]
Christophe DENEUX edited comment on MANTRUN-98 at 9/30/14 3:33 AM:
---
I have just encountered this issue with Maven version 3.1.1:
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
17:22:22+0200)
Java version: 1.7.0_65, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-i386/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux" (Ubuntu 14.04 uptodate), version: "3.13.0-36-generic", arch:
"i386", family: "unix"
Running with antrun:
maven-antrun-plugin
1.7
was (Author: cdeneux):
I have just encountered this issue with Maven version 3.1.1:
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
17:22:22+0200)
Java version: 1.7.0_65, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-i386/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux" (Ubuntu 14.04 uptodate), version: "3.13.0-36-generic", arch:
"i386", family: "unix"
> multiple input tasks leads to exception
> ---
>
> Key: MANTRUN-98
> URL: https://jira.codehaus.org/browse/MANTRUN-98
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.3
> Environment: 32-bit Linux, Sun JDK 1.6.0_07, Maven 2.0.9
>Reporter: Andy Schlaikjer
>
> Running more than one task within Antrun plugin causes exception:
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> Please enter test-value-01 [123]
> Please enter test-value-02 [456]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An Ant BuildException has occured: Failed to read input from Console.
> Stream closed
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException
> has occured: Failed to read input from Console.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant
> BuildException has occured: Failed to read input from Console.
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: Failed to read input from Console.
> at
> org.apache.tools.ant.input.DefaultInputHandler.handleInput(DefaultInputHandler.java:59)
> at org.apache.tools.ant.taskdefs.Input.execute(Input.java:231)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA
[jira] (MANTRUN-98) multiple input tasks leads to exception
[
https://jira.codehaus.org/browse/MANTRUN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353470#comment-353470
]
Christophe DENEUX commented on MANTRUN-98:
--
As mentioned here (https://issues.apache.org/bugzilla/show_bug.cgi?id=51161),
the problem (in my case) was solved upgrading Ant to the version 1.8.3:
{code}
org.apache.maven.plugins
maven-antrun-plugin
...
org.apache.ant
ant
1.8.3
{code}
Perhaps, can you create a version 1.7.1 of the Maven AntRun plugin providing
the Ant runtime in version 1.8.4
> multiple input tasks leads to exception
> ---
>
> Key: MANTRUN-98
> URL: https://jira.codehaus.org/browse/MANTRUN-98
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.3
> Environment: 32-bit Linux, Sun JDK 1.6.0_07, Maven 2.0.9
>Reporter: Andy Schlaikjer
>
> Running more than one task within Antrun plugin causes exception:
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> Please enter test-value-01 [123]
> Please enter test-value-02 [456]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An Ant BuildException has occured: Failed to read input from Console.
> Stream closed
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException
> has occured: Failed to read input from Console.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant
> BuildException has occured: Failed to read input from Console.
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: Failed to read input from Console.
> at
> org.apache.tools.ant.input.DefaultInputHandler.handleInput(DefaultInputHandler.java:59)
> at org.apache.tools.ant.taskdefs.Input.execute(Input.java:231)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:118
[jira] (MANTRUN-98) multiple input tasks leads to exception
[
https://jira.codehaus.org/browse/MANTRUN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353470#comment-353470
]
Christophe DENEUX edited comment on MANTRUN-98 at 9/30/14 4:00 AM:
---
As mentioned here (https://issues.apache.org/bugzilla/show_bug.cgi?id=51161),
the problem (in my case) was solved upgrading Ant to the version 1.8.3:
{code}
org.apache.maven.plugins
maven-antrun-plugin
...
org.apache.ant
ant
1.8.3
{code}
Perhaps, can you create a version 1.7.1 of the Maven AntRun plugin providing
the Ant runtime in version 1.8.4 ?
was (Author: cdeneux):
As mentioned here (https://issues.apache.org/bugzilla/show_bug.cgi?id=51161),
the problem (in my case) was solved upgrading Ant to the version 1.8.3:
{code}
org.apache.maven.plugins
maven-antrun-plugin
...
org.apache.ant
ant
1.8.3
{code}
Perhaps, can you create a version 1.7.1 of the Maven AntRun plugin providing
the Ant runtime in version 1.8.4
> multiple input tasks leads to exception
> ---
>
> Key: MANTRUN-98
> URL: https://jira.codehaus.org/browse/MANTRUN-98
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.3
> Environment: 32-bit Linux, Sun JDK 1.6.0_07, Maven 2.0.9
>Reporter: Andy Schlaikjer
>
> Running more than one task within Antrun plugin causes exception:
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> Please enter test-value-01 [123]
> Please enter test-value-02 [456]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An Ant BuildException has occured: Failed to read input from Console.
> Stream closed
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException
> has occured: Failed to read input from Console.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant
> BuildException has occured: Failed to read input from Console.
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:131)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: Failed to read input from Console.
> at
> org.apache.tools.ant.input.DefaultInputHandler.handleInput(DefaultInputHandler.java:59)
> at org.apache.tools.ant.taskdefs.Input.execute(Input.java:231)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke
[jira] (MSITE-730) Add retryFailedDeploymentCount to site:deploy
James Nord created MSITE-730: Summary: Add retryFailedDeploymentCount to site:deploy Key: MSITE-730 URL: https://jira.codehaus.org/browse/MSITE-730 Project: Maven Site Plugin Issue Type: Improvement Reporter: James Nord When working remotely it is not uncommon to have transient network issues that cause the site:deploy goal to fail. When the site is being uploaded as part of a time consuming multi-module release these failures are very annoying - and it means the whole release process needs to be started again. It would be great if the site:deploy mojo added support to retry a configurable number of times in the face of an error - like the deploy:deploy mojos does with retryFailedDeploymentCount -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353490#comment-353490 ] Bayley Gaillard commented on SUREFIRE-1082: --- Sorry it took so long to get back to you, work has been crazy! I've created a very simple Remote Webdriver project to demonstrate the issue. I ran it first without the parallel feature enabled, then with it set to Classes. I created two test classes that inherit from a base class, similar to my actual project setup, running with parameterization, but I am seeing no evidence of parallel execution. I have zipped and attached the project. This is the log first without, then with parallel turned on: --- T E S T S --- Running sample.classATest 10:25:57: Launched instance of IE 10:25:57: Test A passed 10:26:01: Launched instance of Chrome 10:26:01: Test A passed 10:26:05: Launched instance of Firefox 10:26:05: Test A passed Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.273 sec Running sample.classBTest 10:26:09: Launched instance of IE 10:26:09: Test B passed 10:26:13: Launched instance of Chrome 10:26:13: Test B passed 10:26:17: Launched instance of Firefox 10:26:17: Test B passed Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.02 sec Results : Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ sample --- [INFO] Surefire report directory: C:\Users\bgreen\workspace\sample\target\surefire-reports --- T E S T S --- Running sample.classATest 10:30:57: Launched instance of IE 10:30:57: Test A passed 10:31:01: Launched instance of Chrome 10:31:01: Test A passed 10:31:05: Launched instance of Firefox 10:31:05: Test A passed Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.368 sec - in sample.classATest Running sample.classBTest 10:31:09: Launched instance of IE 10:31:09: Test B passed 10:31:13: Launched instance of Chrome 10:31:13: Test B passed 10:31:17: Launched instance of Firefox 10:31:17: Test B passed Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.903 sec - in sample.classBTest Results : Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESS [INFO] > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Fix For: 2.18 > > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bayley Gaillard updated SUREFIRE-1082: -- Attachment: sample.zip Sample that reproduces the project > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Fix For: 2.18 > > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353489#comment-353489 ] Bayley Gaillard edited comment on SUREFIRE-1082 at 9/30/14 9:33 AM: Sample that reproduces the problem was (Author: yamikuronue): Sample that reproduces the project > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Fix For: 2.18 > > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353491#comment-353491 ] Bayley Gaillard commented on SUREFIRE-1082: --- To run the project I attached, change the IP address to one of either a local VM (I used a VM on my network) or localhost, then start Selenium Server on that machine so it can receive requests. > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Fix For: 2.18 > > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-179) Adding empty files to jar failed with a ZipException : bad CRC checksum
[ https://jira.codehaus.org/browse/MJAR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353497#comment-353497 ] Kristian Rosenvold commented on MJAR-179: - The test case has been added to archiver > Adding empty files to jar failed with a ZipException : bad CRC checksum > --- > > Key: MJAR-179 > URL: https://jira.codehaus.org/browse/MJAR-179 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Benoit Guerin >Priority: Blocker > Fix For: more-investigation > > Attachments: mjar-179.zip > > > Here is the trace : > [INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ project --- > [INFO] Building jar: workspace/project/project-1.0.0-SNAPSHOT.jar > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) on > project project: Error assembling JAR > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling > JAR > at > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:233) > at > org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:251) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: IOException when > zipping Test.class: bad CRC checksum for entry empty_file: 2144df1c instead > of 0 > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:602) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.addResources(AbstractZipArchiver.java:401) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:326) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:223) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:910) > at > org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:582) > at > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:226) > ... 22 more > Caused by: java.util.zip.ZipException: bad CRC checksum for entry empty_file: > 2144df1c instead of 0 > at > org.codehaus.plexus.archiver.zip.ZipOutputStream.closeEntry(ZipOutputStream.java:372) > at > org.codehaus.plexus.archiver.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:422) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:563) > at > org.codehaus.plexus.archiver.jar.JarArchiver.zipFile(JarArchiver.java:480) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:598) > ... 28 more -- This message was sent by
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353500#comment-353500 ] Tibor Digana commented on SUREFIRE-1082: Would you please check the version of JUnit in your POM ? Read the maven-surefire documentation properly. It's written that parallel execution works with JUnit 4.7+. Not a bug. One way or another I will keep this issue open till you get back saying that everything is fine on your side, and I will provide IT tests in Surefire project to prove this scenario. Thx, Tibor > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Fix For: 2.18 > > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-422) HTTP wagon AuthScope is not definable from settings
leon franzen created WAGON-422:
--
Summary: HTTP wagon AuthScope is not definable from settings
Key: WAGON-422
URL: https://jira.codehaus.org/browse/WAGON-422
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http
Affects Versions: 2.7, 2.8
Environment: All
Reporter: leon franzen
Attachments: wagon.patch
Based on our needs as described in this post to the mailing list:
{quote}
We are trying to stand up a highly-available Maven repository that is protected
by an SSO solution using Basic Auth over SSL. The architecture is as follows:
1.)Maven clients connect over the internet to the repository using
maven.example.com
2.)maven.example.com is a hardware load balancer DNS alias that uses HTTP
301 to redirect to repo.example.com
3.)repo.example.com uses HTTP 302 to redirect the request to
login.example.com
4.)login.example.com sends back HTTP 401 to require authentication
5.)The client returns the request with the Authorization header and
login.example.com uses HTTP 302 to redirect the request back to
repo.example.com with the proper Authorization header and retrieve the artifact.
We define the repository in settings.xml with a url of
https://maven.example.com. The problem we are running into is that the Maven
HTTP Wagon code is setting the AuthScope based on the Repository URLâs host
(and port, if supplied).
Credentials creds = new UsernamePasswordCredentials( username,
password );
String host = getRepository().getHost();
int port = getRepository().getPort() > -1 ?
getRepository().getPort() : AuthScope.ANY_PORT;
credentialsProvider.setCredentials( new AuthScope( host, port
), creds );
As such, the AuthScope is created with âmaven.example.comâ and â-1â
(i.e., AuthScope.ANY_PORT). This causes the Authorization header to not be
returned in response to the HTTP 401 challenge and Maven simply moves on to try
to retrieve the artifact from Maven Central (but the artifact isnât thereâ¦).
>From reading the code, there doesnât appear to be any way of telling Maven
>to set the AuthScope realm to a value that we specify (and the AuthScope host
>to AuthScope.ANY_HOST). Are we missing something obvious or, as we believe,
>do we need to enhance Maven to support this type of configuration?
{quote}
We are submitting a patch that provides customization of AuthScope fields via
wagon settings. Allows AuthScope host and port to differ from the associated
repository host and port if needed. Value of "ANY" permits more flexible
AuthScope.
An example configuration snippet, providing AuthScope of any host, any port and
specific realm would look like:
{code:borderStyle=solid}
server-id
user
password
ANY
ANY
My Realm
http.protocol.max-redirects
%i,20
http.protocol.allow-circular-redirects
%b,true
{code}
The feature also allows for the same AuthScope overrides for proxy Basic auth
using the element..
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1098) runOrder=balanced is not working
[
https://jira.codehaus.org/browse/SUREFIRE-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1098.
--
Resolution: Fixed
Commit: http://git-wip-us.apache.org/repos/asf/maven-surefire/commit/5cb02c37
> runOrder=balanced is not working
>
>
> Key: SUREFIRE-1098
> URL: https://jira.codehaus.org/browse/SUREFIRE-1098
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.12.2, 2.12.3, 2.12.4, 2.13, 2.14, 2.14.1, 2.15, 2.16,
> 2.17
> Environment: JDK 7 on Linux
> JUnit 4.11
>Reporter: Miyata Jumpei
>Assignee: Tibor Digana
> Fix For: 2.18
>
>
> It seems that the runOrder parameter with balanced value is not working.
> For example, I created a project with the following setting.
> {code}
>
> maven-surefire-plugin
> 2.17
>
> classes
> balanced
> 2
> false
>
>
> {code}
> Then, execute the following tests.
> TestA: 1 second
> TestB: 2 seconds
> TestC: 3 seconds
> TestD: 4 seconds
> The expected order is the following from the second time.
> Thread 1: TestD → TestA
> Thread 2: TestC → TestB
> However, the actual order is the following.
> Thread 1: TestB → TestD
> Thread 2: TestC → TestA
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353503#comment-353503 ] Tibor Digana commented on SUREFIRE-1082: @Andreas or Kristian, What should be Fix Version if not a bug, e.g. backlog? > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Fix For: 2.18 > > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MECLIPSE-755) Classpath includes dependencies with scope 'runtime'
[ https://jira.codehaus.org/browse/MECLIPSE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353504#comment-353504 ] Roland Asmann commented on MECLIPSE-755: Update: Fix works for workspace-projects as well. > Classpath includes dependencies with scope 'runtime' > > > Key: MECLIPSE-755 > URL: https://jira.codehaus.org/browse/MECLIPSE-755 > Project: Maven Eclipse Plugin > Issue Type: Bug >Reporter: Roland Asmann >Priority: Minor > Attachments: runtime-scope.patch > > > When generating the classpath for a project, the plugin adds *all* > dependencies in the classpath. This is actually incorrect, since the > dependencies with scope 'runtime' should not be added in the classpath. > Here's a quick fix I threw together... It works for JARs, I haven't tested it > for workspace-projects though... -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MECLIPSE-755) Classpath includes dependencies with scope 'runtime'
[ https://jira.codehaus.org/browse/MECLIPSE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353505#comment-353505 ] Dan Tran commented on MECLIPSE-755: --- without runtime jars, test will fail, IMO > Classpath includes dependencies with scope 'runtime' > > > Key: MECLIPSE-755 > URL: https://jira.codehaus.org/browse/MECLIPSE-755 > Project: Maven Eclipse Plugin > Issue Type: Bug >Reporter: Roland Asmann >Priority: Minor > Attachments: runtime-scope.patch > > > When generating the classpath for a project, the plugin adds *all* > dependencies in the classpath. This is actually incorrect, since the > dependencies with scope 'runtime' should not be added in the classpath. > Here's a quick fix I threw together... It works for JARs, I haven't tested it > for workspace-projects though... -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MECLIPSE-755) Classpath includes dependencies with scope 'runtime'
[ https://jira.codehaus.org/browse/MECLIPSE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353506#comment-353506 ] Dan Tran commented on MECLIPSE-755: --- This plugin is not maintained for quite sometime, not sure why you are not using m2e by now > Classpath includes dependencies with scope 'runtime' > > > Key: MECLIPSE-755 > URL: https://jira.codehaus.org/browse/MECLIPSE-755 > Project: Maven Eclipse Plugin > Issue Type: Bug >Reporter: Roland Asmann >Priority: Minor > Attachments: runtime-scope.patch > > > When generating the classpath for a project, the plugin adds *all* > dependencies in the classpath. This is actually incorrect, since the > dependencies with scope 'runtime' should not be added in the classpath. > Here's a quick fix I threw together... It works for JARs, I haven't tested it > for workspace-projects though... -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353508#comment-353508 ] Andreas Gudian commented on SUREFIRE-1082: -- @Tibor: when closing as Not A Bug, please remove any versions in the Fix Version field (so that it is empty again). > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Fix For: 2.18 > > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MECLIPSE-755) Classpath includes dependencies with scope 'runtime'
[ https://jira.codehaus.org/browse/MECLIPSE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roland Asmann closed MECLIPSE-755. -- Resolution: Not A Bug > Classpath includes dependencies with scope 'runtime' > > > Key: MECLIPSE-755 > URL: https://jira.codehaus.org/browse/MECLIPSE-755 > Project: Maven Eclipse Plugin > Issue Type: Bug >Reporter: Roland Asmann >Priority: Minor > Attachments: runtime-scope.patch > > > When generating the classpath for a project, the plugin adds *all* > dependencies in the classpath. This is actually incorrect, since the > dependencies with scope 'runtime' should not be added in the classpath. > Here's a quick fix I threw together... It works for JARs, I haven't tested it > for workspace-projects though... -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MECLIPSE-755) Classpath includes dependencies with scope 'runtime'
[ https://jira.codehaus.org/browse/MECLIPSE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353510#comment-353510 ] Roland Asmann commented on MECLIPSE-755: Ah... Indeed, you might be right about tests failing... I thought I had all use-cases figured out... OK, bug can be closed. > Classpath includes dependencies with scope 'runtime' > > > Key: MECLIPSE-755 > URL: https://jira.codehaus.org/browse/MECLIPSE-755 > Project: Maven Eclipse Plugin > Issue Type: Bug >Reporter: Roland Asmann >Priority: Minor > Attachments: runtime-scope.patch > > > When generating the classpath for a project, the plugin adds *all* > dependencies in the classpath. This is actually incorrect, since the > dependencies with scope 'runtime' should not be added in the classpath. > Here's a quick fix I threw together... It works for JARs, I haven't tested it > for workspace-projects though... -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1082: --- Fix Version/s: (was: 2.18) > Parallelization does not work as expected when using jUnit Parameterized > > > Key: SUREFIRE-1082 > URL: https://jira.codehaus.org/browse/SUREFIRE-1082 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Bayley Gaillard >Assignee: Tibor Digana > Attachments: sample.zip > > > I am using jUnit's Parameterized annotation on some Selenium tests to specify > the browsers they should run with. I am also using SureFire's new parallel > parameter (set to "classes") to try and run them in parallel. However, this > is nerfing the parallelization. > Let's say I have my parameter list set to Firefox and Chrome, and I have 10 > test classes. When I execute the tests with Maven, I'm seeing one Firefox > window and one Chrome window appear on my remote server at a time. I expected > to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with > each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-179) Adding empty files to jar failed with a ZipException : bad CRC checksum
[ https://jira.codehaus.org/browse/MJAR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MJAR-179. Resolution: Fixed Fix Version/s: (was: more-investigation) 2.5.1 Assignee: Karl-Heinz Marbaise Fixed in [r1628550|http://svn.apache.org/r1628550] > Adding empty files to jar failed with a ZipException : bad CRC checksum > --- > > Key: MJAR-179 > URL: https://jira.codehaus.org/browse/MJAR-179 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Benoit Guerin >Assignee: Karl-Heinz Marbaise >Priority: Blocker > Fix For: 2.5.1 > > Attachments: mjar-179.zip > > > Here is the trace : > [INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ project --- > [INFO] Building jar: workspace/project/project-1.0.0-SNAPSHOT.jar > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) on > project project: Error assembling JAR > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling > JAR > at > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:233) > at > org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:251) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: IOException when > zipping Test.class: bad CRC checksum for entry empty_file: 2144df1c instead > of 0 > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:602) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.addResources(AbstractZipArchiver.java:401) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:326) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:223) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:910) > at > org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:582) > at > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:226) > ... 22 more > Caused by: java.util.zip.ZipException: bad CRC checksum for entry empty_file: > 2144df1c instead of 0 > at > org.codehaus.plexus.archiver.zip.ZipOutputStream.closeEntry(ZipOutputStream.java:372) > at > org.codehaus.plexus.archiver.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:422) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:563) > at > org.codehaus.plexus.archiver.jar.JarArchiver.zipFile(JarArchiver.java:480) > at > org.codehaus.ple
[jira] (MJAR-179) Adding empty files to jar failed with a ZipException : bad CRC checksum
[ https://jira.codehaus.org/browse/MJAR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353511#comment-353511 ] Karl-Heinz Marbaise edited comment on MJAR-179 at 9/30/14 4:23 PM: --- Upgrade to plexus-archiver 2.6.2 has fixed the issue. This has been done [r1628550|http://svn.apache.org/r1628550] was (Author: khmarbaise): Fixed in [r1628550|http://svn.apache.org/r1628550] > Adding empty files to jar failed with a ZipException : bad CRC checksum > --- > > Key: MJAR-179 > URL: https://jira.codehaus.org/browse/MJAR-179 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Benoit Guerin >Assignee: Karl-Heinz Marbaise >Priority: Blocker > Fix For: 2.5.1 > > Attachments: mjar-179.zip > > > Here is the trace : > [INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ project --- > [INFO] Building jar: workspace/project/project-1.0.0-SNAPSHOT.jar > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) on > project project: Error assembling JAR > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling > JAR > at > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:233) > at > org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:251) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: IOException when > zipping Test.class: bad CRC checksum for entry empty_file: 2144df1c instead > of 0 > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:602) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.addResources(AbstractZipArchiver.java:401) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:326) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:223) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:910) > at > org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:582) > at > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:226) > ... 22 more > Caused by: java.util.zip.ZipException: bad CRC checksum for entry empty_file: > 2144df1c instead of 0 > at > org.codehaus.plexus.archiver.zip.ZipOutputStream.closeEntry(ZipOutputStream.java:372) > at > org.codehaus.plexus.archiver.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:422) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:563) > at
[jira] (MREPOSITORY-31) Update version of plexus-archiver to 2.6.2
[ https://jira.codehaus.org/browse/MREPOSITORY-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MREPOSITORY-31: --- Fix Version/s: 2.4 > Update version of plexus-archiver to 2.6.2 > -- > > Key: MREPOSITORY-31 > URL: https://jira.codehaus.org/browse/MREPOSITORY-31 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > [Release Notes plexus-archiver > 2.6.1]|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] > * Bug > ** [PLXCOMP-243] - Restore JDK1.5 compatibility > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MREPOSITORY-31) Update version of plexus-archiver to 2.6.2
Karl-Heinz Marbaise created MREPOSITORY-31: -- Summary: Update version of plexus-archiver to 2.6.2 Key: MREPOSITORY-31 URL: https://jira.codehaus.org/browse/MREPOSITORY-31 Project: Maven Repository Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Karl-Heinz Marbaise Priority: Minor [Release Notes plexus-archiver 2.6.1]|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] * Bug ** [PLXCOMP-243] - Restore JDK1.5 compatibility [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MREPOSITORY-31) Update version of plexus-archiver to 2.6.2
[ https://jira.codehaus.org/browse/MREPOSITORY-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MREPOSITORY-31: --- Description: [Release Notes plexus-archiver 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] * Bug ** [PLXCOMP-243] - Restore JDK1.5 compatibility [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux was: [Release Notes plexus-archiver 2.6.1]|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] * Bug ** [PLXCOMP-243] - Restore JDK1.5 compatibility [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux > Update version of plexus-archiver to 2.6.2 > -- > > Key: MREPOSITORY-31 > URL: https://jira.codehaus.org/browse/MREPOSITORY-31 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > [Release Notes plexus-archiver > 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] > * Bug > ** [PLXCOMP-243] - Restore JDK1.5 compatibility > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MREPOSITORY-31) Update version of plexus-archiver to 2.6.2
[ https://jira.codehaus.org/browse/MREPOSITORY-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MREPOSITORY-31. -- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1628552|http://svn.apache.org/r1628552]. > Update version of plexus-archiver to 2.6.2 > -- > > Key: MREPOSITORY-31 > URL: https://jira.codehaus.org/browse/MREPOSITORY-31 > Project: Maven Repository Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > [Release Notes plexus-archiver > 2.6.1]|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] > * Bug > ** [PLXCOMP-243] - Restore JDK1.5 compatibility > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-714) Update version of plexus-archiver to 2.6.1
[ https://jira.codehaus.org/browse/MASSEMBLY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-714: -- Description: [Release Notes plexus-archiver 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] * Bug: ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to fix) * Improvements: ** [PLXCOMP-64] - add symlink support to tar unarchiver ** [PLXCOMP-117] - add symbolic links managment [Release Notes plexus-archiver 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] * Bug ** [PLXCOMP-243] - Restore JDK1.5 compatibility [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux was: [Release Notes plexus-archiver 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] * Bug: ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to fix) * Improvements: ** [PLXCOMP-64] - add symlink support to tar unarchiver ** [PLXCOMP-117] - add symbolic links managment [Release Notes plexus-archiver 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] * Bug ** [PLXCOMP-243] - Restore JDK1.5 compatibility > Update version of plexus-archiver to 2.6.1 > -- > > Key: MASSEMBLY-714 > URL: https://jira.codehaus.org/browse/MASSEMBLY-714 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > [Release Notes plexus-archiver > 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] > * Bug: > ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to > fix) > * Improvements: > ** [PLXCOMP-64] - add symlink support to tar unarchiver > ** [PLXCOMP-117] - add symbolic links managment > [Release Notes plexus-archiver > 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] > * Bug > ** [PLXCOMP-243] - Restore JDK1.5 compatibility > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-714) Update version of plexus-archiver to 2.6.1
[ https://jira.codehaus.org/browse/MASSEMBLY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-714: -- Description: [Release Notes plexus-archiver 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] * Bug: ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to fix) * Improvements: ** [PLXCOMP-64] - add symlink support to tar unarchiver ** [PLXCOMP-117] - add symbolic links managment [Release Notes plexus-archiver 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] * Bug ** [PLXCOMP-243] - Restore JDK1.5 compatibility was: [Release Notes plexus-archiver 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] * Bug: ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to fix) * Improvements: ** [PLXCOMP-64] - add symlink support to tar unarchiver ** [PLXCOMP-117] - add symbolic links managment > Update version of plexus-archiver to 2.6.1 > -- > > Key: MASSEMBLY-714 > URL: https://jira.codehaus.org/browse/MASSEMBLY-714 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > [Release Notes plexus-archiver > 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] > * Bug: > ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to > fix) > * Improvements: > ** [PLXCOMP-64] - add symlink support to tar unarchiver > ** [PLXCOMP-117] - add symbolic links managment > [Release Notes plexus-archiver > 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] > * Bug > ** [PLXCOMP-243] - Restore JDK1.5 compatibility -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-714) Update version of plexus-archiver to 2.6.1
[ https://jira.codehaus.org/browse/MASSEMBLY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MASSEMBLY-714. - Resolution: Fixed Fix in [r1628092|http://svn.apache.org/r1628092]. Fix in [r1628553|http://svn.apache.org/r1628553]. > Update version of plexus-archiver to 2.6.1 > -- > > Key: MASSEMBLY-714 > URL: https://jira.codehaus.org/browse/MASSEMBLY-714 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > [Release Notes plexus-archiver > 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] > * Bug: > ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to > fix) > * Improvements: > ** [PLXCOMP-64] - add symlink support to tar unarchiver > ** [PLXCOMP-117] - add symbolic links managment > [Release Notes plexus-archiver > 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] > * Bug > ** [PLXCOMP-243] - Restore JDK1.5 compatibility > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPLUGIN-274) generated HelpMojo source contains tabs and other errors reported by Checkstyle
Herve Boutemy created MPLUGIN-274:
-
Summary: generated HelpMojo source contains tabs and other errors
reported by Checkstyle
Key: MPLUGIN-274
URL: https://jira.codehaus.org/browse/MPLUGIN-274
Project: Maven Plugin Tools
Issue Type: Bug
Affects Versions: 3.3
Reporter: Herve Boutemy
Priority: Minor
{noformat}[INFO] --- maven-checkstyle-plugin:2.13:check (checkstyle-check) @
dist-tool-plugin ---
[INFO]
[INFO] There are 6 checkstyle errors.
[ERROR] HelpMojo.java[3] (header) RegexpHeader: Line does not match expected
header line of '^/\*\s*$'.
[ERROR] HelpMojo.java[61] (sizes) LineLength: Line is longer than 120
characters (found 130).
[ERROR] HelpMojo.java[112:26] (coding) MagicNumber: '80' is a magic number.
[ERROR] HelpMojo.java[233:1] (whitespace) FileTabCharacter: Line contains a tab
character.
[ERROR] HelpMojo.java[274:54] (whitespace) WhitespaceAfter: 'cast' is not
followed by whitespace.
[ERROR] HelpMojo.java[295:9] (whitespace) FileTabCharacter: Line contains a tab
character.{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-714) Update version of plexus-archiver to 2.6.2
[ https://jira.codehaus.org/browse/MASSEMBLY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-714: -- Summary: Update version of plexus-archiver to 2.6.2 (was: Update version of plexus-archiver to 2.6.1) > Update version of plexus-archiver to 2.6.2 > -- > > Key: MASSEMBLY-714 > URL: https://jira.codehaus.org/browse/MASSEMBLY-714 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > [Release Notes plexus-archiver > 2.6|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20639] > * Bug: > ** [PLXCOMP-113] - zip unarchiver doesn't support symlinks (and trivial to > fix) > * Improvements: > ** [PLXCOMP-64] - add symlink support to tar unarchiver > ** [PLXCOMP-117] - add symbolic links managment > [Release Notes plexus-archiver > 2.6.1|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20656] > * Bug > ** [PLXCOMP-243] - Restore JDK1.5 compatibility > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEAR-197) Update version of plexus-archiver to 2.6.2
[ https://jira.codehaus.org/browse/MEAR-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEAR-197. Resolution: Fixed Fix Version/s: 2.10 Assignee: Karl-Heinz Marbaise Fixed in [r1628554|http://svn.apache.org/r1628554]. > Update version of plexus-archiver to 2.6.2 > -- > > Key: MEAR-197 > URL: https://jira.codehaus.org/browse/MEAR-197 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.10 > > > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEAR-197) Update version of plexus-archiver to 2.6.2
Karl-Heinz Marbaise created MEAR-197: Summary: Update version of plexus-archiver to 2.6.2 Key: MEAR-197 URL: https://jira.codehaus.org/browse/MEAR-197 Project: Maven Ear Plugin Issue Type: Improvement Affects Versions: 2.10 Reporter: Karl-Heinz Marbaise Priority: Minor [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-71) Update version of plexus-archiver to 2.6.2
[ https://jira.codehaus.org/browse/MEJB-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MEJB-71: Fix Version/s: 3.0 > Update version of plexus-archiver to 2.6.2 > -- > > Key: MEJB-71 > URL: https://jira.codehaus.org/browse/MEJB-71 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 3.0 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEJB-71) Update version of plexus-archiver to 2.6.2
Karl-Heinz Marbaise created MEJB-71: --- Summary: Update version of plexus-archiver to 2.6.2 Key: MEJB-71 URL: https://jira.codehaus.org/browse/MEJB-71 Project: Maven EJB Plugin Issue Type: Improvement Affects Versions: 3.0 Reporter: Karl-Heinz Marbaise Priority: Minor [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPLUGIN-274) generated HelpMojo source contains tabs and other errors reported by Checkstyle
[
https://jira.codehaus.org/browse/MPLUGIN-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPLUGIN-274.
-
Resolution: Fixed
Fix Version/s: 3.4
Assignee: Herve Boutemy
fixed in [r1628556|http://svn.apache.org/r1628556]
only license header is intentionnally left missing
> generated HelpMojo source contains tabs and other errors reported by
> Checkstyle
> ---
>
> Key: MPLUGIN-274
> URL: https://jira.codehaus.org/browse/MPLUGIN-274
> Project: Maven Plugin Tools
> Issue Type: Bug
>Affects Versions: 3.3
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Minor
> Fix For: 3.4
>
>
> {noformat}[INFO] --- maven-checkstyle-plugin:2.13:check (checkstyle-check) @
> dist-tool-plugin ---
> [INFO]
> [INFO] There are 6 checkstyle errors.
> [ERROR] HelpMojo.java[3] (header) RegexpHeader: Line does not match expected
> header line of '^/\*\s*$'.
> [ERROR] HelpMojo.java[61] (sizes) LineLength: Line is longer than 120
> characters (found 130).
> [ERROR] HelpMojo.java[112:26] (coding) MagicNumber: '80' is a magic number.
> [ERROR] HelpMojo.java[233:1] (whitespace) FileTabCharacter: Line contains a
> tab character.
> [ERROR] HelpMojo.java[274:54] (whitespace) WhitespaceAfter: 'cast' is not
> followed by whitespace.
> [ERROR] HelpMojo.java[295:9] (whitespace) FileTabCharacter: Line contains a
> tab character.{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MEJB-71) Update version of plexus-archiver to 2.6.2
[ https://jira.codehaus.org/browse/MEJB-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MEJB-71. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1628559|http://svn.apache.org/r1628559]. > Update version of plexus-archiver to 2.6.2 > -- > > Key: MEJB-71 > URL: https://jira.codehaus.org/browse/MEJB-71 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 3.0 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 3.0 > > > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-321) Upgrade plexus archiver to 2.6.2
[ https://jira.codehaus.org/browse/MWAR-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MWAR-321: - Fix Version/s: 2.5 > Upgrade plexus archiver to 2.6.2 > > > Key: MWAR-321 > URL: https://jira.codehaus.org/browse/MWAR-321 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-321) Upgrade plexus archiver to 2.6.2
Karl-Heinz Marbaise created MWAR-321: Summary: Upgrade plexus archiver to 2.6.2 Key: MWAR-321 URL: https://jira.codehaus.org/browse/MWAR-321 Project: Maven WAR Plugin Issue Type: Improvement Affects Versions: 2.5 Reporter: Karl-Heinz Marbaise Priority: Minor [Release Notes plexus-archiver 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] * Bugs: ** [PLXCOMP-238] - CRC Failure if compress=false ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-321) Upgrade plexus archiver to 2.6.2
[ https://jira.codehaus.org/browse/MWAR-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MWAR-321. Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed [r1628561|http://svn.apache.org/r1628561] > Upgrade plexus archiver to 2.6.2 > > > Key: MWAR-321 > URL: https://jira.codehaus.org/browse/MWAR-321 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > [Release Notes plexus-archiver > 2.6.2|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20664] > * Bugs: > ** [PLXCOMP-238] - CRC Failure if compress=false > ** [PLXCOMP-245] - Archives created on windows get zero permissions, creates > malformed permissions on linux -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSOURCES-73) Update version of plexus-archiver to 2.6.1
[ https://jira.codehaus.org/browse/MSOURCES-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MSOURCES-73: Description: [Release Notes plexus-archiver 2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress was: [Release Notes plexus-archiver 2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress > Update version of plexus-archiver to 2.6.1 > -- > > Key: MSOURCES-73 > URL: https://jira.codehaus.org/browse/MSOURCES-73 > Project: Maven Source Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.4 > > > [Release Notes plexus-archiver > 2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSOURCES-74) Upgrade to plexus-archiver 2.6.2
Karl-Heinz Marbaise created MSOURCES-74: --- Summary: Upgrade to plexus-archiver 2.6.2 Key: MSOURCES-74 URL: https://jira.codehaus.org/browse/MSOURCES-74 Project: Maven Source Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Karl-Heinz Marbaise Priority: Minor First step in [r1628561|http://svn.apache.org/r1628561]. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSOURCES-74) Upgrade to plexus-archiver 2.6.2
[ https://jira.codehaus.org/browse/MSOURCES-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MSOURCES-74: Fix Version/s: 2.4 > Upgrade to plexus-archiver 2.6.2 > > > Key: MSOURCES-74 > URL: https://jira.codehaus.org/browse/MSOURCES-74 > Project: Maven Source Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > First step in [r1628561|http://svn.apache.org/r1628561]. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSOURCES-74) Upgrade to plexus-archiver 2.6.2
[ https://jira.codehaus.org/browse/MSOURCES-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MSOURCES-74. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1628564|http://svn.apache.org/r1628564]. > Upgrade to plexus-archiver 2.6.2 > > > Key: MSOURCES-74 > URL: https://jira.codehaus.org/browse/MSOURCES-74 > Project: Maven Source Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.4 > > > First step in [r1628561|http://svn.apache.org/r1628561]. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1088) When test fail during initialization the test execution time can result in a large negative number.
[ https://jira.codehaus.org/browse/SUREFIRE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353525#comment-353525 ] Daniel Cruver commented on SUREFIRE-1088: - I believe this issue still effects 2.17. We get a case where we have a failing test that causes this to happen atleast once a week. Unfortunately I am unable to produce an example that reproduces it. I will let you know if I have better luck tomorrow. Thank You. > When test fail during initialization the test execution time can result in a > large negative number. > --- > > Key: SUREFIRE-1088 > URL: https://jira.codehaus.org/browse/SUREFIRE-1088 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.16 >Reporter: Daniel Cruver >Priority: Minor > Fix For: 2.18 > > > For example it will print out this: > Time elapsed: -1,317,678.69 sec <<< ERROR! > This happened in a call to @BeforeClass method and was specifically when a > class was not found when loading in a spring context. The later is not that > important because we have seen it happen in other cases. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-422) HTTP wagon AuthScope is not definable from settings
[
https://jira.codehaus.org/browse/WAGON-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated WAGON-422:
---
Fix Version/s: 2.8
> HTTP wagon AuthScope is not definable from settings
> ---
>
> Key: WAGON-422
> URL: https://jira.codehaus.org/browse/WAGON-422
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.7, 2.8
> Environment: All
>Reporter: leon franzen
>Assignee: Olivier Lamy
> Fix For: 2.8
>
> Attachments: wagon.patch
>
>
> Based on our needs as described in this post to the mailing list:
> {quote}
> We are trying to stand up a highly-available Maven repository that is
> protected by an SSO solution using Basic Auth over SSL. The architecture is
> as follows:
> 1.)Maven clients connect over the internet to the repository using
> maven.example.com
> 2.)maven.example.com is a hardware load balancer DNS alias that uses HTTP
> 301 to redirect to repo.example.com
> 3.)repo.example.com uses HTTP 302 to redirect the request to
> login.example.com
> 4.)login.example.com sends back HTTP 401 to require authentication
> 5.)The client returns the request with the Authorization header and
> login.example.com uses HTTP 302 to redirect the request back to
> repo.example.com with the proper Authorization header and retrieve the
> artifact.
>
> We define the repository in settings.xml with a url of
> https://maven.example.com. The problem we are running into is that the Maven
> HTTP Wagon code is setting the AuthScope based on the Repository URLâs host
> (and port, if supplied).
> Credentials creds = new UsernamePasswordCredentials(
> username, password );
> String host = getRepository().getHost();
> int port = getRepository().getPort() > -1 ?
> getRepository().getPort() : AuthScope.ANY_PORT;
>
> credentialsProvider.setCredentials( new AuthScope( host, port
> ), creds );
> As such, the AuthScope is created with âmaven.example.comâ and â-1â
> (i.e., AuthScope.ANY_PORT). This causes the Authorization header to not be
> returned in response to the HTTP 401 challenge and Maven simply moves on to
> try to retrieve the artifact from Maven Central (but the artifact isnât
> thereâ¦).
> From reading the code, there doesnât appear to be any way of telling Maven
> to set the AuthScope realm to a value that we specify (and the AuthScope host
> to AuthScope.ANY_HOST). Are we missing something obvious or, as we believe,
> do we need to enhance Maven to support this type of configuration?
> {quote}
> We are submitting a patch that provides customization of AuthScope fields via
> wagon settings. Allows AuthScope host and port to differ from the associated
> repository host and port if needed. Value of "ANY" permits more flexible
> AuthScope.
> An example configuration snippet, providing AuthScope of any host, any port
> and specific realm would look like:
> {code:borderStyle=solid}
>
> server-id
> user
> password
>
>
> ANY
> ANY
> My Realm
>
>
>
>
>
> http.protocol.max-redirects
> %i,20
>
>
>
> http.protocol.allow-circular-redirects
> %b,true
>
>
>
>
>
>
> {code}
> The feature also allows for the same AuthScope overrides for proxy Basic auth
> using the element..
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-422) HTTP wagon AuthScope is not definable from settings
[
https://jira.codehaus.org/browse/WAGON-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reassigned WAGON-422:
--
Assignee: Olivier Lamy
> HTTP wagon AuthScope is not definable from settings
> ---
>
> Key: WAGON-422
> URL: https://jira.codehaus.org/browse/WAGON-422
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.7, 2.8
> Environment: All
>Reporter: leon franzen
>Assignee: Olivier Lamy
> Fix For: 2.8
>
> Attachments: wagon.patch
>
>
> Based on our needs as described in this post to the mailing list:
> {quote}
> We are trying to stand up a highly-available Maven repository that is
> protected by an SSO solution using Basic Auth over SSL. The architecture is
> as follows:
> 1.)Maven clients connect over the internet to the repository using
> maven.example.com
> 2.)maven.example.com is a hardware load balancer DNS alias that uses HTTP
> 301 to redirect to repo.example.com
> 3.)repo.example.com uses HTTP 302 to redirect the request to
> login.example.com
> 4.)login.example.com sends back HTTP 401 to require authentication
> 5.)The client returns the request with the Authorization header and
> login.example.com uses HTTP 302 to redirect the request back to
> repo.example.com with the proper Authorization header and retrieve the
> artifact.
>
> We define the repository in settings.xml with a url of
> https://maven.example.com. The problem we are running into is that the Maven
> HTTP Wagon code is setting the AuthScope based on the Repository URLâs host
> (and port, if supplied).
> Credentials creds = new UsernamePasswordCredentials(
> username, password );
> String host = getRepository().getHost();
> int port = getRepository().getPort() > -1 ?
> getRepository().getPort() : AuthScope.ANY_PORT;
>
> credentialsProvider.setCredentials( new AuthScope( host, port
> ), creds );
> As such, the AuthScope is created with âmaven.example.comâ and â-1â
> (i.e., AuthScope.ANY_PORT). This causes the Authorization header to not be
> returned in response to the HTTP 401 challenge and Maven simply moves on to
> try to retrieve the artifact from Maven Central (but the artifact isnât
> thereâ¦).
> From reading the code, there doesnât appear to be any way of telling Maven
> to set the AuthScope realm to a value that we specify (and the AuthScope host
> to AuthScope.ANY_HOST). Are we missing something obvious or, as we believe,
> do we need to enhance Maven to support this type of configuration?
> {quote}
> We are submitting a patch that provides customization of AuthScope fields via
> wagon settings. Allows AuthScope host and port to differ from the associated
> repository host and port if needed. Value of "ANY" permits more flexible
> AuthScope.
> An example configuration snippet, providing AuthScope of any host, any port
> and specific realm would look like:
> {code:borderStyle=solid}
>
> server-id
> user
> password
>
>
> ANY
> ANY
> My Realm
>
>
>
>
>
> http.protocol.max-redirects
> %i,20
>
>
>
> http.protocol.allow-circular-redirects
> %b,true
>
>
>
>
>
>
> {code}
> The feature also allows for the same AuthScope overrides for proxy Basic auth
> using the element..
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-422) HTTP wagon AuthScope is not definable from settings
[
https://jira.codehaus.org/browse/WAGON-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed WAGON-422.
--
Resolution: Fixed
patch merged.
Thanks!
> HTTP wagon AuthScope is not definable from settings
> ---
>
> Key: WAGON-422
> URL: https://jira.codehaus.org/browse/WAGON-422
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.7, 2.8
> Environment: All
>Reporter: leon franzen
>Assignee: Olivier Lamy
> Fix For: 2.8
>
> Attachments: wagon.patch
>
>
> Based on our needs as described in this post to the mailing list:
> {quote}
> We are trying to stand up a highly-available Maven repository that is
> protected by an SSO solution using Basic Auth over SSL. The architecture is
> as follows:
> 1.)Maven clients connect over the internet to the repository using
> maven.example.com
> 2.)maven.example.com is a hardware load balancer DNS alias that uses HTTP
> 301 to redirect to repo.example.com
> 3.)repo.example.com uses HTTP 302 to redirect the request to
> login.example.com
> 4.)login.example.com sends back HTTP 401 to require authentication
> 5.)The client returns the request with the Authorization header and
> login.example.com uses HTTP 302 to redirect the request back to
> repo.example.com with the proper Authorization header and retrieve the
> artifact.
>
> We define the repository in settings.xml with a url of
> https://maven.example.com. The problem we are running into is that the Maven
> HTTP Wagon code is setting the AuthScope based on the Repository URLâs host
> (and port, if supplied).
> Credentials creds = new UsernamePasswordCredentials(
> username, password );
> String host = getRepository().getHost();
> int port = getRepository().getPort() > -1 ?
> getRepository().getPort() : AuthScope.ANY_PORT;
>
> credentialsProvider.setCredentials( new AuthScope( host, port
> ), creds );
> As such, the AuthScope is created with âmaven.example.comâ and â-1â
> (i.e., AuthScope.ANY_PORT). This causes the Authorization header to not be
> returned in response to the HTTP 401 challenge and Maven simply moves on to
> try to retrieve the artifact from Maven Central (but the artifact isnât
> thereâ¦).
> From reading the code, there doesnât appear to be any way of telling Maven
> to set the AuthScope realm to a value that we specify (and the AuthScope host
> to AuthScope.ANY_HOST). Are we missing something obvious or, as we believe,
> do we need to enhance Maven to support this type of configuration?
> {quote}
> We are submitting a patch that provides customization of AuthScope fields via
> wagon settings. Allows AuthScope host and port to differ from the associated
> repository host and port if needed. Value of "ANY" permits more flexible
> AuthScope.
> An example configuration snippet, providing AuthScope of any host, any port
> and specific realm would look like:
> {code:borderStyle=solid}
>
> server-id
> user
> password
>
>
> ANY
> ANY
> My Realm
>
>
>
>
>
> http.protocol.max-redirects
> %i,20
>
>
>
> http.protocol.allow-circular-redirects
> %b,true
>
>
>
>
>
>
> {code}
> The feature also allows for the same AuthScope overrides for proxy Basic auth
> using the element..
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1103) The total amount of threads are not used with test classes nested by Enclosed.class.
Miyata Jumpei created SUREFIRE-1103:
---
Summary: The total amount of threads are not used with test
classes nested by Enclosed.class.
Key: SUREFIRE-1103
URL: https://jira.codehaus.org/browse/SUREFIRE-1103
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.7+ (parallel) support
Affects Versions: 2.17, 2.16
Environment: JDK 7 on Linux
JUnit 4.11
Reporter: Miyata Jumpei
It seems that the total amount of threads are not used with test classes nested
by Enclosed.class.
For example, I created a project with the following setting.
{code}
maven-surefire-plugin
2.17
classes
4
false
{code}
And, create 4 test classes like the following.
{code}
@RunWith(Enclosed.class)
public class Test {
public static class InnerTest {
@Test
public void test1() throws InterruptedException {
Thread.sleep(1000l);
}
}
}
{code}
It takes 4 seconds to execute the 4 tests.
I hope 1 second.
It seems that the outer tests are not parallelly-processed until all inner
tests are processed.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
