[jira] [Commented] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116043#comment-16116043 ] Arvind commented on SUREFIRE-1402: -- Hi Dan Tran i dont have any tag of jmockit. i just have following tags for junit and jmockit 4.8.2 4.4 2.5.1 2.6.0-RC2 0.999.19 1.3.1 > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116041#comment-16116041 ] Arvind commented on SUREFIRE-1402: -- Tibor, i got the build as success using mvn org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom > log.txt. I got the the version of maven-surefire-plugin as 2.8. So anything else i can do? > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DOXIATOOLS-57) Figure not displayed in doxia-editor if relative path used
[
https://issues.apache.org/jira/browse/DOXIATOOLS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alix Lourme updated DOXIATOOLS-57:
--
Description:
When a relative path is used for a
[Figure|https://maven.apache.org/doxia/references/apt-format.html#Figure], the
view tab doesn't display it.
+Scenario+: In a project consider:
# A _test.jpg_ picture
# A _test.apt_ file with:
{code}
Test
This is a test of figure:
[test.jpg] test
{code}
The result of display is a black cross.
If the path is absolute, the picture is displayed.
In addition of managing the relative path, it could be nice to manage the
classic Maven site directories (apt &
[resources|https://maven.apache.org/guides/mini/guide-site.html#Adding_Extra_Resources]).
was:
When a relative path is used for a
[Figure|https://maven.apache.org/doxia/references/apt-format.html#Figure], the
view tab doesn't display it.
+Scenario+: In a project consider:
# A _test.jpg_ picture
# A _test.apt_ file with:
{code}
Test
This is a test of figure:
[test.jpg] test
{code}
The result of display is a black cross.
If the path is complete, the picture is displayed.
In addition of managing the relative path, it could be nice to manage the
classic Maven site directories (apt &
[resources|https://maven.apache.org/guides/mini/guide-site.html#Adding_Extra_Resources]).
> Figure not displayed in doxia-editor if relative path used
> --
>
> Key: DOXIATOOLS-57
> URL: https://issues.apache.org/jira/browse/DOXIATOOLS-57
> Project: Maven Doxia Tools
> Issue Type: Bug
> Components: Doxia Eclipse Editor
>Affects Versions: doxia-eclipse-editor-1.0
>Reporter: Alix Lourme
>
> When a relative path is used for a
> [Figure|https://maven.apache.org/doxia/references/apt-format.html#Figure],
> the view tab doesn't display it.
> +Scenario+: In a project consider:
> # A _test.jpg_ picture
> # A _test.apt_ file with:
> {code}
> Test
> This is a test of figure:
>
> [test.jpg] test
> {code}
> The result of display is a black cross.
> If the path is absolute, the picture is displayed.
> In addition of managing the relative path, it could be nice to manage the
> classic Maven site directories (apt &
> [resources|https://maven.apache.org/guides/mini/guide-site.html#Adding_Extra_Resources]).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (DOXIATOOLS-57) Figure not displayed in doxia-editor if relative path used
Alix Lourme created DOXIATOOLS-57:
-
Summary: Figure not displayed in doxia-editor if relative path used
Key: DOXIATOOLS-57
URL: https://issues.apache.org/jira/browse/DOXIATOOLS-57
Project: Maven Doxia Tools
Issue Type: Bug
Components: Doxia Eclipse Editor
Affects Versions: doxia-eclipse-editor-1.0
Reporter: Alix Lourme
When a relative path is used for a
[Figure|https://maven.apache.org/doxia/references/apt-format.html#Figure], the
view tab doesn't display it.
+Scenario+: In a project consider:
# A _test.jpg_ picture
# A _test.apt_ file with:
{code}
Test
This is a test of figure:
[test.jpg] test
{code}
The result of display is a black cross.
If the path is complete, the picture is displayed.
In addition of managing the relative path, it could be nice to manage the
classic Maven site directories (apt &
[resources|https://maven.apache.org/guides/mini/guide-site.html#Adding_Extra_Resources]).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DOXIATOOLS-46) Workspace indisposed after file rename
[ https://issues.apache.org/jira/browse/DOXIATOOLS-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alix Lourme updated DOXIATOOLS-46: -- Attachment: DOXIATOOLS-46-doxia-ide.patch Please consider [^DOXIATOOLS-46-doxia-ide.patch] as patch. This is a _poor_ fix, only delete the infinite loop (not enough knowledge in SWT to fix the file change handler). > Workspace indisposed after file rename > -- > > Key: DOXIATOOLS-46 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-46 > Project: Maven Doxia Tools > Issue Type: Bug > Components: Doxia Eclipse Editor > Environment: Eclipse Kepler 4.3.2 > Doxia Editors Feature 1.0.0.201301041016 >Reporter: Alix Lourme >Priority: Blocker > Attachments: DOXIATOOLS-46-doxia-ide.patch, loop.log > > > +Synthesis+ : When a file opened by plugin is renamed, plugin is indisposed > and crash the workspace (because try to reopen it after Eclipse kill/restart). > +Use Case+ : > # Create a workspace and a project _Test_ > # Create file _index.apt_ with a title (the file is opened by plugin) > # Rename file (F2 key) : _index2.apt_ > # Error appears : _Resource '/Test/index.apt' does not exist._ > # +Informations+ : > * File is renamed (on filesystem) > * Sheet title of plugin is *index2.apt* but on mouse over shows *index.apt* > * The sheet is not closable > * Eclipse must be killed > * Error _Unhandled event loop exception_ appears in log > +Root cause hypothesis+ : Infinite loop in > _org.apache.maven.doxia.ide.eclipse.common.ui.editors.AbstractMultiPageEditorPart.isSaveAsAllowed(AbstractMultiPageEditorPart.java:231)_ > (cf. [^loop.log]) > +Workaround+ : Recreate the file ... because plugin try to open renamed file > during start => same error below. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115917#comment-16115917 ] Dan Tran edited comment on SUREFIRE-1402 at 8/6/17 8:23 PM: Not sure if this is related. jmocket 1.x reimplements org.junit.runner.Runner, so you must make sure it it loaded before junit ( define jmockit maven dependency before junit) was (Author: dantran): Not sure if this is related. jmocket 1.x reimplements org.junit.runner.Runner, so you must make sure it it loaded before junit ( define jmockit maven deppendency before junit) > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115917#comment-16115917 ] Dan Tran commented on SUREFIRE-1402: Not sure if this is related. jmocket 1.x reimplements org.junit.runner.Runner, so you must make sure it it loaded before junit ( define jmockit maven deppendency before junit) > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MSHADE-258) RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta
[
https://issues.apache.org/jira/browse/MSHADE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115888#comment-16115888
]
Robert Scholte commented on MSHADE-258:
---
MSHADE-242 is happening in case of minifying the jar, this issue happens when
relocating classes of jars with a module descriptor. This will also mean that
it'll break the intended strong encapsulation.
Java 9 will not provide a solution for that yet, so I guess we'll have to log a
warning as well.
> RemappingClassAdapter is deprecated and throws an exception with ASM 6.0 beta
> -
>
> Key: MSHADE-258
> URL: https://issues.apache.org/jira/browse/MSHADE-258
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Ismael Juma
>
> While trying to use the maven shade plugin with ASM 6.0 beta (for Java 9
> support) in the easymock project, I ran into the following exception:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project
> easymock: Error creating shaded jar: Error in ASM processing class
> module-info.class: RemappingClassAdapter is deprecated, use ClassRemapper
> instead -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on
> project easymock: Error creating shaded jar: Error in ASM processing class
> module-info.class
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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 creating
> shaded jar: Error in ASM processing class module-info.class
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error in ASM
> processing class module-info.class
> at
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:453)
> at
> org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar(DefaultShader.java:220)
> at
> org.apache.maven.plugins.shade.DefaultShader.shadeJars(DefaultShader.java:181)
> at
> org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:104)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:442)
> ... 22 more
> Caused by: java.lang.RuntimeException: RemappingClassAdapter is deprecated,
> use ClassRemapper instead
> at org.objectweb.asm.commons.RemappingClassAdapter.visitModule(Unknown
> Source)
> at org.objectweb.asm.ClassReader.a(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at
> org.apache.maven.plug
[jira] [Commented] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115864#comment-16115864 ] Tibor Digana commented on SUREFIRE-1402: mvn org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom > log.txt and see versions of all "surefire" artifacts, just search this word in log.txt. > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MNGSITE-314) Broken link to Settings reference.
[
https://issues.apache.org/jira/browse/MNGSITE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNGSITE-314:
---
Description:
When reading this Maven Guide page
https://maven.apache.org/guides/mini/guide-configuring-maven.html
the "Settings reference" link is broken.
{code}
$ wget https://maven.apache.org/guides/mini/settings.html
--2017-08-03 11:27:14-- https://maven.apache.org/guides/mini/settings.html
Resolving maven.apache.org (maven.apache.org)... 88.198.26.2, 140.211.11.105,
62.210.60.236, ...
Connecting to maven.apache.org (maven.apache.org)|88.198.26.2|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-08-03 11:27:14 ERROR 404: Not Found.
{code}
was:
When reading this Maven Guide page
https://maven.apache.org/guides/mini/guide-configuring-maven.html
the "Settings reference" link is broken.
{{$ wget https://maven.apache.org/guides/mini/settings.html
--2017-08-03 11:27:14-- https://maven.apache.org/guides/mini/settings.html
Resolving maven.apache.org (maven.apache.org)... 88.198.26.2, 140.211.11.105,
62.210.60.236, ...
Connecting to maven.apache.org (maven.apache.org)|88.198.26.2|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-08-03 11:27:14 ERROR 404: Not Found.
$}}
> Broken link to Settings reference.
> --
>
> Key: MNGSITE-314
> URL: https://issues.apache.org/jira/browse/MNGSITE-314
> Project: Maven Project Web Site
> Issue Type: Bug
> Environment: All environments.
>Reporter: Jeremy Whiting
>Priority: Minor
> Labels: documentation
>
> When reading this Maven Guide page
> https://maven.apache.org/guides/mini/guide-configuring-maven.html
> the "Settings reference" link is broken.
> {code}
> $ wget https://maven.apache.org/guides/mini/settings.html
> --2017-08-03 11:27:14-- https://maven.apache.org/guides/mini/settings.html
> Resolving maven.apache.org (maven.apache.org)... 88.198.26.2, 140.211.11.105,
> 62.210.60.236, ...
> Connecting to maven.apache.org (maven.apache.org)|88.198.26.2|:443...
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2017-08-03 11:27:14 ERROR 404: Not Found.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115773#comment-16115773 ] Arvind commented on SUREFIRE-1402: -- Tibor, i am new to these things. Can you guide me how to do it. thanks for the help. > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115764#comment-16115764 ] Tibor Digana commented on SUREFIRE-1402: You should not have exactly the same stack trace with version 2.20 because the Java class JUnit4TestSet does not exist long time. Please generate Effective POM with commandline and find out version of Surefire Provider. It should be same with version of the Surefire/Failsafe plugin. If not then this would be the issue in your POM. > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arvind reopened SUREFIRE-1402: -- I have Maven 3.3.9 (mvn -version). I do know how can i check which version from eclipse. I have tried to change to maven surefire 2.20 but still got the same error. > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115738#comment-16115738 ] Arvind commented on SUREFIRE-1402: -- Hi Tibor, thanks for your response. I am using maven 3.3.9 (i got this info in command prompt mvn -version) I have tried using maven surefire plugin 2.20, but i am getting the same error. Let me know how can i proceed. > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MRESOURCES-238) on archetype:create-from-project does not copying .gitignore file to archetype
[ https://issues.apache.org/jira/browse/MRESOURCES-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ebuzer taha kanat updated MRESOURCES-238: - Summary: on archetype:create-from-project does not copying .gitignore file to archetype (was: on archetype:create-from-project does not copy to .gitignore file to archetype) > on archetype:create-from-project does not copying .gitignore file to archetype > -- > > Key: MRESOURCES-238 > URL: https://issues.apache.org/jira/browse/MRESOURCES-238 > Project: Maven Resources Plugin > Issue Type: Bug >Affects Versions: 3.0.0, 3.0.1, 3.0.2 >Reporter: Ebuzer taha kanat > > false > or > > > > > > .*ignore > > > > > not solving the problem either -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MRESOURCES-238) on archetype:create-from-project does not copy to .gitignore file to archetype
Ebuzer taha kanat created MRESOURCES-238: Summary: on archetype:create-from-project does not copy to .gitignore file to archetype Key: MRESOURCES-238 URL: https://issues.apache.org/jira/browse/MRESOURCES-238 Project: Maven Resources Plugin Issue Type: Bug Affects Versions: 3.0.2, 3.0.1, 3.0.0 Reporter: Ebuzer taha kanat false or .*ignore not solving the problem either -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1401) If test FAILS with forks > 0 - OutOfMemory with Junit5, another Error with forks=0
[
https://issues.apache.org/jira/browse/SUREFIRE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1401.
--
Resolution: Duplicate
Fix Version/s: SUREFIRE-1382
OOM was fixed in SUREFIRE-1382
Ask JUnit team regarding
{{java.lang.ClassNotFoundException:
org.apache.maven.plugin.surefire.log.api.ConsoleLogger}}
They adapted to new version of Surefire - not sure if released.
> If test FAILS with forks > 0 - OutOfMemory with Junit5, another Error with
> forks=0
> --
>
> Key: SUREFIRE-1401
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1401
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin, process forking
>Affects Versions: 2.20
> Environment: Maven 3.5.0, Java 1.8, Junit5 (M4, M5)
>Reporter: FAGIM SADYKOV
>Assignee: Tibor Digana
> Fix For: SUREFIRE-1382
>
> Attachments: FailedTest.java, pom.xml
>
>
> In attachment where is minimal project to cause problem.
> Create project with given POM and single test, then run `mvn test` - it will
> be fail not about Test fails, but about OutOfMemory exception.
> If you change forks to Zero then it not fails with OutOfMemory, but about
> `java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger`
> There is no difference on M4 or M5 of Junit5 subversion.
> There is no problem if test not fails
> The only solution is to change 2.20 back to 2.19.1 - it will be good on any
> forking and M4 and M5
> POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> outer-issues
> surefire-plugin-bug-OutOfMemory
> 1.0-SNAPSHOT
>
>
> 1
>
> 2.20
>
> 5
>
>
>
> org.junit.jupiter
> junit-jupiter-api
> 5.0.0-M${junut5suffix}
>
>
> org.junit.jupiter
> junit-jupiter-engine
> 5.0.0-M${junut5suffix}
>
>
>
>
>
> maven-surefire-plugin
> ${surefire_version}
>
>
> org.junit.platform
>
> junit-platform-surefire-provider
> 1.0.0-M${junut5suffix}
>
>
>
> ${forks}
>
>
>
>
>
> {code}
> Test:
> {code}
> import org.junit.jupiter.api.Test;
> import static org.junit.jupiter.api.Assertions.assertNotNull;
> public class FailedTest {
> @Test
> public void fail(){
> // you can change it to assertNull - it will be not problem in
> MAVEN
> assertNotNull(null);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SUREFIRE-1401) If test FAILS with forks > 0 - OutOfMemory with Junit5, another Error with forks=0
[
https://issues.apache.org/jira/browse/SUREFIRE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1401:
--
Assignee: Tibor Digana
> If test FAILS with forks > 0 - OutOfMemory with Junit5, another Error with
> forks=0
> --
>
> Key: SUREFIRE-1401
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1401
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin, process forking
>Affects Versions: 2.20
> Environment: Maven 3.5.0, Java 1.8, Junit5 (M4, M5)
>Reporter: FAGIM SADYKOV
>Assignee: Tibor Digana
> Attachments: FailedTest.java, pom.xml
>
>
> In attachment where is minimal project to cause problem.
> Create project with given POM and single test, then run `mvn test` - it will
> be fail not about Test fails, but about OutOfMemory exception.
> If you change forks to Zero then it not fails with OutOfMemory, but about
> `java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger`
> There is no difference on M4 or M5 of Junit5 subversion.
> There is no problem if test not fails
> The only solution is to change 2.20 back to 2.19.1 - it will be good on any
> forking and M4 and M5
> POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> outer-issues
> surefire-plugin-bug-OutOfMemory
> 1.0-SNAPSHOT
>
>
> 1
>
> 2.20
>
> 5
>
>
>
> org.junit.jupiter
> junit-jupiter-api
> 5.0.0-M${junut5suffix}
>
>
> org.junit.jupiter
> junit-jupiter-engine
> 5.0.0-M${junut5suffix}
>
>
>
>
>
> maven-surefire-plugin
> ${surefire_version}
>
>
> org.junit.platform
>
> junit-platform-surefire-provider
> 1.0.0-M${junut5suffix}
>
>
>
> ${forks}
>
>
>
>
>
> {code}
> Test:
> {code}
> import org.junit.jupiter.api.Test;
> import static org.junit.jupiter.api.Assertions.assertNotNull;
> public class FailedTest {
> @Test
> public void fail(){
> // you can change it to assertNull - it will be not problem in
> MAVEN
> assertNotNull(null);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[
https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1402.
--
Resolution: Invalid
You used very old version.
The class {{org.apache.maven.surefire.junit4.JUnit4TestSet}} does not exist
anymore.
Upgrade Maven to 3.0.5 and Surefire 2.18 or higher.
> I have an issue with maven surefire which uses Junit and Jmockit
>
>
> Key: SUREFIRE-1402
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1402
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Surefire Report
> Plugin
>Affects Versions: 2.8
> Environment: Windows 7 eclipse Java 1.8
>Reporter: Arvind
>Assignee: Tibor Digana
>Priority: Critical
> Labels: build, test
>
> When i try to build the maven project i get the following error.
> ---
> Test set:
> ---
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<<
> FAILURE!
> java.lang.IllegalArgumentException
> at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SUREFIRE-1402) I have an issue with maven surefire which uses Junit and Jmockit
[ https://issues.apache.org/jira/browse/SUREFIRE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1402: -- Assignee: Tibor Digana > I have an issue with maven surefire which uses Junit and Jmockit > > > Key: SUREFIRE-1402 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1402 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support, Maven Surefire Report > Plugin >Affects Versions: 2.8 > Environment: Windows 7 eclipse Java 1.8 >Reporter: Arvind >Assignee: Tibor Digana >Priority: Critical > Labels: build, test > > When i try to build the maven project i get the following error. > --- > Test set: > --- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.469 sec <<< > FAILURE! > java.lang.IllegalArgumentException > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at > org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at > org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:74) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1400) Windows surefire boot directory should appear in system default temporary-directory
[ https://issues.apache.org/jira/browse/SUREFIRE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1400: --- Fix Version/s: 2.20.1 > Windows surefire boot directory should appear in system default > temporary-directory > --- > > Key: SUREFIRE-1400 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1400 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin > Environment: Windows >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.20.1 > > > Windows paths are limited in length. The path of surefire boot should point > to system tmp dir. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1400) Windows surefire boot directory should appear in system default temporary-directory
[ https://issues.apache.org/jira/browse/SUREFIRE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1400. -- Resolution: Fixed https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=413be0d6b7232fe6ef6255492099fb0fb4f3bf24 > Windows surefire boot directory should appear in system default > temporary-directory > --- > > Key: SUREFIRE-1400 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1400 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin > Environment: Windows >Reporter: Tibor Digana >Assignee: Tibor Digana > > Windows paths are limited in length. The path of surefire boot should point > to system tmp dir. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
