[jira] [Assigned] (SUREFIRE-1204) -Dtest= option is broken in 2.19
[ https://issues.apache.org/jira/browse/SUREFIRE-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1204: -- Assignee: Tibor Digana > -Dtest= option is broken in 2.19 > > > Key: SUREFIRE-1204 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1204 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Artem Koshelev >Assignee: Tibor Digana > > i tried to run specific method passing parameter > "-Dtest=my.package.myClass#myMethod" but got "no tests were executed" > it works in previous version (2.14-2.18) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1204) -Dtest= option is broken in 2.19
[ https://issues.apache.org/jira/browse/SUREFIRE-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1204. -- Resolution: Duplicate Fix Version/s: 2.19.1 > -Dtest= option is broken in 2.19 > > > Key: SUREFIRE-1204 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1204 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Reporter: Artem Koshelev >Assignee: Tibor Digana > Fix For: 2.19.1 > > > i tried to run specific method passing parameter > "-Dtest=my.package.myClass#myMethod" but got "no tests were executed" > it works in previous version (2.14-2.18) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1169) JUnit / Arquillian lifecycle friendly test execution with forkCount > 1 and reuseForks = true
[
https://issues.apache.org/jira/browse/SUREFIRE-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043779#comment-15043779
]
Tibor Digana commented on SUREFIRE-1169:
[~famod]
Did the provider surefire-junit47 help solving this issue?
Should we keep this issue open?
> JUnit / Arquillian lifecycle friendly test execution with forkCount > 1 and
> reuseForks = true
> -
>
> Key: SUREFIRE-1169
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1169
> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
>Affects Versions: 2.18.1
>Reporter: Falko Modler
>Assignee: Tibor Digana
> Attachments: SUREFIRE-1169_forksExecuteTestsOneByOne.patch,
> SUREFIRE-1169_forksExecuteTestsOneByOne_FIXED.patch
>
>
> The current approach to "stream" each test class name to a fork via
> {{TestProvidingInputStream}} yields a good "load balancing" accross the forks
> but it *triggers the entire test lifecycle for each test*.
> With {{forkCount = 1}}, all tests are executed in one set but with
> {{forkCount = n}} (n > 1) each test is a separate "set" (so to say).
> This is very problematic in case you or a test framwork you are using relies
> on a certain lifecycle.
> [Arquillian|http://arquillian.org/] for example ties various "events" to
> JUnit's lifecycle methods, like {{AfterSuite}} to
> {{RunListener.testRunFinished(...)}} which triggers the shutdown of the
> managed server etc.
> When using multiple forks, {{RunListener.testRunFinished(...)}} is called for
> *every* single test class, triggering {{AfterSuite}} for every single test,
> although the fork will receive further tests after that which should "reuse"
> the server.
> This is just an example. In fact the whole JUnit / Arquillian lifecycle is
> inconsistent when using multiple forks.
> From a user perspective I wouldn't expect this behaviour:
> As {{forkCount = 1}} (and {{reusableForks = true}}) triggers
> {{RunListener.testRunFinished(...)}} *once*, {{forkCount = n}} (and
> {{reusableForks = true}}) should trigger that method *n* times, not *x* times.
> To be fair, the
> [documentation|https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html]
> *does* contain a pointer to that problem by saying:
> {quote}
> When using reuseForks=true and a forkCount value larger than one, test
> classes are handed over to the forked process one-by-one.
> {quote}
> But the consequences remain very unclear.
> *(Possible) Solution:*
> I took a stab at this and implemented an "eager test distribution" to the
> forks in {{ForkStart.java}} and disabled streaming. Please see attached patch
> (to be applied against project root, 2.18.1).
> Patch Details:
> - New config property: {{ForkConfiguration.forksExecuteTestsOneByOne}}, set
> via Mojo (default is true for backward compatibility, name is debatable)
> - When {{forksExecuteTestsOneByOne}} ist set to false, the {{messageQueue}}
> in {{ForkStarter.runSuitesForkOnceMultiple(...)}} is *not* wrapped in fork
> specific {{TestProvidingInputStream}} instances to be consumed bit by bit
> later on.
> Instead, the queue is consumed directly and each test class name is assigned
> to the respective fork by creating a copy of the {{providerProperties}} which
> is filled individually for each fork.
> E.g. for three forks and eight tests:
> -- fork 1 executes test 1, 4 and 7
> -- fork 2 executes test 2, 5 and 8
> -- fork 3 executes test 3 and 6
> - To have a clean {{providerProperties}} template I had to move
> {{DefaultScanResult.writeTo(...)}} to the respective private methods.
> Otherwise the properties would have contained *all* tests already.
> - I refactored some methods in {{ForkStarter}} to enhance readability and to
> reduce code duplication.
> - The patch does *not* contain a test for the new behaviour but all existing
> tests passed.
> {{forksExecuteTestsOneByOne = false}} now leads to a consistent lifecycle.
> This solution has one downside: One or more forks could be overloaded while
> other forks could "underloaded" because you cannot say how long each test
> will take. runOrder=balanced could help here but has yet to be implemented
> for forks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1166) Include/Exclude regex pattern for a path is incorrectly replaced on Windows
[
https://issues.apache.org/jira/browse/SUREFIRE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1166.
--
Resolution: Not A Problem
Assignee: Tibor Digana
User error.
Wrong use of regex pattern.Do not use slash (/) (\) in regex.
> Include/Exclude regex pattern for a path is incorrectly replaced on Windows
> ---
>
> Key: SUREFIRE-1166
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1166
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.18.1
> Environment: Windows
>Reporter: Matthias Gradl
>Assignee: Tibor Digana
>
> On non-unix systems, the file scanner converts slashes ("/") into the
> file-system appropriate separator (eg. "\" on Windows) thus colliding with
> the standard escape character in regex Strings.
> For regex pattern matching a path (segment) to a test package (like:
> "%regex[.*/smoketest/.*Test\.java]" this leads to unusable patterns:
> "%regex[.*\smoketest\.*Test\.java]"
> There needs to be a more sophisticated replacement happening when the include
> string is actually a regex pattern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SUREFIRE-1135) Improve ignore message for TestNG
[ https://issues.apache.org/jira/browse/SUREFIRE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1135: -- Assignee: Tibor Digana > Improve ignore message for TestNG > - > > Key: SUREFIRE-1135 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1135 > Project: Maven Surefire > Issue Type: New Feature > Components: TestNG support >Reporter: Michal Bocek >Assignee: Tibor Digana > Attachments: TEST-testng.SkipExceptionReportTest.xml > > > Once the test is ignored/skipped in TestNG no additional informations are > reported. Surefire xml report contains only "skipped" element without any > information. It will be very useful to provide addition info like message and > stacktrace. > JUnit reporter correctly provide ignore message from "Ignore" annotation so > we can similarly provide message from SkipException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043806#comment-15043806 ] Tibor Digana edited comment on SUREFIRE-1042 at 12/6/15 10:35 AM: -- [~andy] Can you attach Maven project to reproduce it? Otherwise we will close it. was (Author: tibor17): [~andy] Can you attache Maven project to reproduce it? Otherwise we will close it. > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043806#comment-15043806 ] Tibor Digana commented on SUREFIRE-1042: [~andy] Can you attache Maven project to reproduce it? Otherwise we will close it. > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1034) dependencesToScan versus classifiers: what's the scoop?
[ https://issues.apache.org/jira/browse/SUREFIRE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043810#comment-15043810 ] Tibor Digana commented on SUREFIRE-1034: [~ben...@basistech.com] [~bimargul...@gmail.com] [~bmargulies] Pls provide a fix. You are PMC so you have rights to push a fix. Personally I do not have test which needs this feature in my job. > dependencesToScan versus classifiers: what's the scoop? > --- > > Key: SUREFIRE-1034 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1034 > Project: Maven Surefire > Issue Type: Bug >Reporter: Benson Margulies > Fix For: 3.0 > > > # The doc could really use an example of dependenciesToScan > # The doc should tell me the syntax for using classifiers > # if classifiers don't work, please make them work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1032) Running junit tests too verbose on command line when parallel execution is false
[ https://issues.apache.org/jira/browse/SUREFIRE-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1032. -- Resolution: Later Assignee: Tibor Digana Feel free to reopen it if you are still interested in this issue. > Running junit tests too verbose on command line when parallel execution is > false > > > Key: SUREFIRE-1032 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1032 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.16 >Reporter: Tom Jenkinson >Assignee: Tibor Digana > > http://jira.codehaus.org/browse/SUREFIRE-968 changed the output of the > surefire plugin such that it is easier to identify the output from parallel > executed test suites. Although this design may be appropriate for that use > case, it does have negative viewability implications and as such it would be > useful to minimize usage of that format where possible. Negatives include: If > you are developing on a small window it increases the likelihood of wrapping > of the text (if your terminal supports wrapping, or a scroll bar if not). > For example, if "parallel" execution is not set to true, it would be better > to see the old style output. > I agree it is required behaviour in the context of the use case it was > intended to solve. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MCHANGES-363) Add support for opened issues in announcement Mojo
[ https://issues.apache.org/jira/browse/MCHANGES-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MCHANGES-363. --- Resolution: Fixed Assignee: Olivier Lamy (*$^¨%`£) pr merged. Thanks! > Add support for opened issues in announcement Mojo > -- > > Key: MCHANGES-363 > URL: https://issues.apache.org/jira/browse/MCHANGES-363 > Project: Maven Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.11 >Reporter: David Pilato >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Trivial > Fix For: 2.12 > > Original Estimate: 1h > Remaining Estimate: 1h > > Would be nice to be able to generate announcement file including current > opened issues. > Really handy if you want to test your announcement chain without having to > actually commit your changes or close issues on github. > It is currently supported when you generate the github report but not > supported when you generate the github announcement. > Patch is coming... :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-363) Add support for opened issues in announcement Mojo
[ https://issues.apache.org/jira/browse/MCHANGES-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043826#comment-15043826 ] Hudson commented on MCHANGES-363: - SUCCESS: Integrated in maven-plugins #4855 (See [https://builds.apache.org/job/maven-plugins/4855/]) MCHANGES-363: Add support for opened issues in announcement Mojo Generate announcement file including current opened issues. Really handy if you want to test your announcement chain without having to actually commit your changes or close issues on github. It is currently supported when you generate the github report but not supported when you generate the github announcement. Closes MCHANGES-363 (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1718158]) * maven-changes-plugin/src/main/java/org/apache/maven/plugin/announcement/AnnouncementMojo.java > Add support for opened issues in announcement Mojo > -- > > Key: MCHANGES-363 > URL: https://issues.apache.org/jira/browse/MCHANGES-363 > Project: Maven Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.11 >Reporter: David Pilato >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Trivial > Fix For: 2.12 > > Original Estimate: 1h > Remaining Estimate: 1h > > Would be nice to be able to generate announcement file including current > opened issues. > Really handy if you want to test your announcement chain without having to > actually commit your changes or close issues on github. > It is currently supported when you generate the github report but not > supported when you generate the github announcement. > Patch is coming... :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-903) Execute tests by group as well as by class
[
https://issues.apache.org/jira/browse/SUREFIRE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-903.
-
Resolution: Not A Problem
Assignee: Tibor Digana
tested in future 2.19.1
> Execute tests by group as well as by class
> --
>
> Key: SUREFIRE-903
> URL: https://issues.apache.org/jira/browse/SUREFIRE-903
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
>Affects Versions: 2.12.2
> Environment: Maven 3, TestNG 6.7, NetBeans 7.2
>Reporter: Chris Rankin
>Assignee: Tibor Digana
>
> Similar to SUREFIRE-577, only execute methods on a class if they belong to a
> certain group or groups.
> NetBean's "Test File" action invokes a particular TestNG class via
> {{-Dtest=className}}. However, this completely ignores the TestNG groups and
> executes _every_ {{@Test}}, including {{@BeforeClass}} methods that were
> supposed to have been excluded (and mutually exclusive!).
> Using {{-Dgroups=...}} respects the grouping but also executes all classes,
> whereas I am trying to debug only one class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-860) additionalClasspathElement doesn't work for folders with jar filers
[ https://issues.apache.org/jira/browse/SUREFIRE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-860. - Resolution: Cannot Reproduce Assignee: Tibor Digana Cannot reproduce in future 2.19.1. > additionalClasspathElement doesn't work for folders with jar filers > --- > > Key: SUREFIRE-860 > URL: https://issues.apache.org/jira/browse/SUREFIRE-860 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Affects Versions: 2.12 > Environment: windows maven2 maven3 >Reporter: necromantiarian >Assignee: Tibor Digana > > used such config > 2.12 > > > > C:/mycompany/lib/*.jar > > > wanted to include a lot of *.jar files to classpath > observed: > surefire.test.class.path=D:\zf\workspace\test\target\test-classes;D:\zf\workspace\test\target\classes;C:\Users\myuser\.m2\repository\junit\junit\4.10\junit-4.10.jar;C:\Users\myuser\.m2\repository\org\hamcrest\hamcrest-core\1.1\hamcrest-core-1.1.jar;C:/mycompany/lib/*.jar > and got ClassNotFoundException > expected: > the classes to be found and all the jars in classpath, just like maven libs > note: > tried also > C:/mycompany/lib/ > tried older versions of plugin too > Am i doing smth wrong ? > please advise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-854) surefire causes "Forked Java VM exited abnormally"
[
https://issues.apache.org/jira/browse/SUREFIRE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-854.
-
Resolution: Auto Closed
Assignee: Tibor Digana
> surefire causes "Forked Java VM exited abnormally"
>
>
> Key: SUREFIRE-854
> URL: https://issues.apache.org/jira/browse/SUREFIRE-854
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
>Affects Versions: 2.12
> Environment: OS name: "windows 7", version: "6.1", arch: "amd64",
> family: "windows"
>Reporter: Martin Jozef
>Assignee: Tibor Digana
>
> The following argline will cause an error when the variable
> ${settings.localRepository} represents example C:\Users\Martin
> Jozef\.m2\repository\etc
> Tried escaping with quotes but it does not work. Moving the repository to a
> non-space location is not an option.
> -javaagent:"${settings.localRepository}/org/springframework/spring-agent/2.5.6.SEC03/spring-agent-2.5.6.SEC03.jar"
> -Xmx700m -Xms350m -XX:PermSize=80m -XX:MaxPermSize=180m
> Error:
> Error opening zip file or JAR manifest missing : C:\Users\Martin
> Error occurred during initialization of VM
> agent library failed to init: instrument
> Testsuite: com.bipt.tiva.persistence.risk.ho.HoRiskLoadTest
> Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
> Testcase: com.bipt.tiva.persistence.risk.ho.HoRiskLoadTest:null: Caused
> an ERROR
> Forked Java VM exited abnormally. Please note the time in the report does not
> reflect the time until the VM exit.
> junit.framework.AssertionFailedError: Forked Java VM exited abnormally.
> Please note the time in the report does not reflect the time until the VM
> exit.
> at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153)
> Test com.bipt.tiva.persistence.risk.ho.HoRiskLoadTest FAILED (crashed)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-833) Support for annotated JUnit @Category
[
https://issues.apache.org/jira/browse/SUREFIRE-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043834#comment-15043834
]
Tibor Digana commented on SUREFIRE-833:
---
[~jan_goyvaerts]
[~java.artisan]
There were a lot of attempts to have such feature in JUnit.
See the issue https://github.com/junit-team/junit/issues/1226
Can we close this issue in Maven group?
> Support for annotated JUnit @Category
> -
>
> Key: SUREFIRE-833
> URL: https://issues.apache.org/jira/browse/SUREFIRE-833
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.x support
>Affects Versions: 2.12
>Reporter: Jan Goyvaerts
> Attachments: SUREFIRE-833-spraguep-2.patch,
> SUREFIRE-833-spraguep.patch
>
>
> The current implementation of Surefire seems to look for explicit @Category
> annotations in the test classes. And will only consider those. Suppose I'd
> like to add a more concise annotation for this:
> @Category(IntegrationTests.class) <== JUnit @Category
> @Target({ElementType.TYPE})
> @Retention(RetentionPolicy.RUNTIME)
> @Documented
> public @interface IntegrationTest {}
> Annotating my test class with @IntegrationTest does not work. Although I
> think it looks much better than repeating everywhere in my code
> "@Category(com.foo.bar.IntegrationTests.class)". For which I add an
> additional dependency in the interface class btw.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-811) remote-testing
[ https://issues.apache.org/jira/browse/SUREFIRE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-811. - Resolution: Won't Fix Assignee: Tibor Digana Closing due to we already received a request that tests should run from socket. https://github.com/apache/maven-surefire/pull/74 The ambition of Surefire 3.x would be to run such tests. That's the reason why I introduced commands in forked-main VM communication. > remote-testing > -- > > Key: SUREFIRE-811 > URL: https://issues.apache.org/jira/browse/SUREFIRE-811 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin >Reporter: Henning Gross >Assignee: Tibor Digana > Attachments: ConsoleOutputCapture.patch > > > Add the possibility to copy the target folder to remote machine and run > integration-tests there. Copy back the results and handle them as if they > would have been ran locally. > I would volounteer to submit a patch for this feature if theres a chance it > would be accepted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SUREFIRE-790) Allow forked process to access the Maven session of parent
[ https://issues.apache.org/jira/browse/SUREFIRE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-790: - Assignee: Tibor Digana > Allow forked process to access the Maven session of parent > -- > > Key: SUREFIRE-790 > URL: https://issues.apache.org/jira/browse/SUREFIRE-790 > Project: Maven Surefire > Issue Type: New Feature > Components: process forking >Affects Versions: 2.10 >Reporter: Karel Piwko >Assignee: Tibor Digana > > Forked process should be able to get information from a "parent process", > which is a Maven build execution. > This will allow the test to access information like which pom.xml file being > processed, settings.xml and Maven Reactor plugin. > This feature is needed to any test which want to interfere with Maven > repositories with Aether, for instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHANGES-363) Add support for opened issues in announcement Mojo
[ https://issues.apache.org/jira/browse/MCHANGES-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043839#comment-15043839 ] ASF GitHub Bot commented on MCHANGES-363: - Github user dadoonet closed the pull request at: https://github.com/apache/maven-plugins/pull/67 > Add support for opened issues in announcement Mojo > -- > > Key: MCHANGES-363 > URL: https://issues.apache.org/jira/browse/MCHANGES-363 > Project: Maven Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.11 >Reporter: David Pilato >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Trivial > Fix For: 2.12 > > Original Estimate: 1h > Remaining Estimate: 1h > > Would be nice to be able to generate announcement file including current > opened issues. > Really handy if you want to test your announcement chain without having to > actually commit your changes or close issues on github. > It is currently supported when you generate the github report but not > supported when you generate the github announcement. > Patch is coming... :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-778) failIfNoTests=false should not be required when using -Dtest=MyTestClass in multi-module reactor builds
[ https://issues.apache.org/jira/browse/SUREFIRE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-778: -- Fix Version/s: 3.0 > failIfNoTests=false should not be required when using -Dtest=MyTestClass in > multi-module reactor builds > --- > > Key: SUREFIRE-778 > URL: https://issues.apache.org/jira/browse/SUREFIRE-778 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Scott Carey > Fix For: 3.0 > > > Configure a trivial multi-module build with two tests (TestA, TestB) and two > modules, one test in each module. > a multi-module aggregate build will succeed with > 'mvn test' > but fail with > 'mvn test -Dtest=TestA' > This happens with 2.10, but does not with 2.6 for http://avro.apache.org/ > (https://issues.apache.org/jira/browse/AVRO-935) > This is related to bug > http://jira.codehaus.org/browse/SUREFIRE-464 > -Dtest=Foo should not require that every module have a matching Foo, only one > needs match. Or to simplify things, don't automatically switch from > failIfNoTests=false to failIfNoTests=true when -Dtest= is set at all. > Users who are running one test by hand don't need this behavior (they will > notice if the test they are trying to run doesn't run) and automated > tools/scripts that use this parameter that want it to fail should set > -DfailIfNoTests=true. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-778) failIfNoTests=false should not be required when using -Dtest=MyTestClass in multi-module reactor builds
[ https://issues.apache.org/jira/browse/SUREFIRE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043843#comment-15043843 ] Tibor Digana commented on SUREFIRE-778: --- In 3.0 failIfNoTests may be set to false programaticaly. > failIfNoTests=false should not be required when using -Dtest=MyTestClass in > multi-module reactor builds > --- > > Key: SUREFIRE-778 > URL: https://issues.apache.org/jira/browse/SUREFIRE-778 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Scott Carey > Fix For: 3.0 > > > Configure a trivial multi-module build with two tests (TestA, TestB) and two > modules, one test in each module. > a multi-module aggregate build will succeed with > 'mvn test' > but fail with > 'mvn test -Dtest=TestA' > This happens with 2.10, but does not with 2.6 for http://avro.apache.org/ > (https://issues.apache.org/jira/browse/AVRO-935) > This is related to bug > http://jira.codehaus.org/browse/SUREFIRE-464 > -Dtest=Foo should not require that every module have a matching Foo, only one > needs match. Or to simplify things, don't automatically switch from > failIfNoTests=false to failIfNoTests=true when -Dtest= is set at all. > Users who are running one test by hand don't need this behavior (they will > notice if the test they are trying to run doesn't run) and automated > tools/scripts that use this parameter that want it to fail should set > -DfailIfNoTests=true. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-632) add a test-failed goal, to only run the tests which failed last time
[ https://issues.apache.org/jira/browse/SUREFIRE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-632. - Resolution: Won't Fix Assignee: Tibor Digana > add a test-failed goal, to only run the tests which failed last time > > > Key: SUREFIRE-632 > URL: https://issues.apache.org/jira/browse/SUREFIRE-632 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Affects Versions: 2.5 >Reporter: james strachan >Assignee: Tibor Digana > > if the test goal outputs to target/surefire-reports/failures.txt a little > text file of all the failures which occurred in the previous test run, it > would be easy to add a new goal *test-failed* which just runs all the test > cases which previously failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1194) reporter argument does not work for TestNG
[ https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043857#comment-15043857 ] ASF GitHub Bot commented on SUREFIRE-1194: -- Github user Tibor17 commented on the pull request: https://github.com/apache/maven-surefire/pull/107#issuecomment-162312898 @juherr I want to make a release during weekend. Can you please update the section (Line 228) of reporters? This is the document. `maven-surefire-plugin/src/site/apt/examples/testng.apt.vm` The user should know what TestNG Versions support List of TestNG classes and String. We should also mention versions which are buggy and therefore not recommended to use. > reporter argument does not work for TestNG > -- > > Key: SUREFIRE-1194 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1194 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.19 >Reporter: Testo Nakada >Assignee: Tibor Digana > Fix For: 2.19.1 > > > TestNG plugin seems to map -reporter command line parameter to reporterslist > which was removed in TestNG project since 2010 > (a4779524b59330e98ee596c5faa43ae1b33ff844). Therefore, this configuration has > stopped working since then. The configuration mentioned in > http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html#Using_Custom_Listeners_and_Reporters > does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1202) Allow rerunFailingTestsCount, skipAfterFailureCount together
[
https://issues.apache.org/jira/browse/SUREFIRE-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043861#comment-15043861
]
ASF GitHub Bot commented on SUREFIRE-1202:
--
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/108#issuecomment-162313183
@seanf I think your feature should be possible only in `surefire-junit4`
provider. Not in `surefire-junit47`. Did you have time to run tests with your
implementation?
> Allow rerunFailingTestsCount, skipAfterFailureCount together
>
>
> Key: SUREFIRE-1202
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1202
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin
>Affects Versions: 2.19
>Reporter: Sean Flanigan
>Assignee: Tibor Digana
>
> I couldn't find this limitation documented anywhere, but if I try to use the
> options {{rerunFailingTestsCount}} and {{skipAfterFailureCount}} together, I
> get this error message:
> {noformat}
> org.apache.maven.plugin.MojoFailureException:
> Parameters ["rerunFailingTestsCount", "skipAfterFailureCount"]
> should not be enabled together
> {noformat}
> I have a use case which requires both options: some integration tests are
> flaky, so I want to use {{rerunFailingTestsCount}} to repeat them, but if all
> tests are failing (eg due to a configuration problem or a really bad change),
> I don't want to wait for the entire test suite to fail multiple times, so I
> would like to abort if say 10 tests have failed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1194) reporter argument does not work for TestNG
[ https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043877#comment-15043877 ] ASF GitHub Bot commented on SUREFIRE-1194: -- Github user juherr commented on the pull request: https://github.com/apache/maven-surefire/pull/107#issuecomment-162313840 Ok, I will. But I'm not available today. Is tomorrow still ok for you? > reporter argument does not work for TestNG > -- > > Key: SUREFIRE-1194 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1194 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.19 >Reporter: Testo Nakada >Assignee: Tibor Digana > Fix For: 2.19.1 > > > TestNG plugin seems to map -reporter command line parameter to reporterslist > which was removed in TestNG project since 2010 > (a4779524b59330e98ee596c5faa43ae1b33ff844). Therefore, this configuration has > stopped working since then. The configuration mentioned in > http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html#Using_Custom_Listeners_and_Reporters > does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1034) dependencesToScan versus classifiers: what's the scoop?
[ https://issues.apache.org/jira/browse/SUREFIRE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043882#comment-15043882 ] Benson Margulies commented on SUREFIRE-1034: I don't have anything around either, and 1004 was created specifically to hold the fix. So I don't see why you reopened this. > dependencesToScan versus classifiers: what's the scoop? > --- > > Key: SUREFIRE-1034 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1034 > Project: Maven Surefire > Issue Type: Bug >Reporter: Benson Margulies > Fix For: 3.0 > > > # The doc could really use an example of dependenciesToScan > # The doc should tell me the syntax for using classifiers > # if classifiers don't work, please make them work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1034) dependencesToScan versus classifiers: what's the scoop?
[ https://issues.apache.org/jira/browse/SUREFIRE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1034: --- Fix Version/s: (was: 3.0) > dependencesToScan versus classifiers: what's the scoop? > --- > > Key: SUREFIRE-1034 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1034 > Project: Maven Surefire > Issue Type: Bug >Reporter: Benson Margulies > > # The doc could really use an example of dependenciesToScan > # The doc should tell me the syntax for using classifiers > # if classifiers don't work, please make them work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1034) dependencesToScan versus classifiers: what's the scoop?
[ https://issues.apache.org/jira/browse/SUREFIRE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1034. -- Resolution: Duplicate > dependencesToScan versus classifiers: what's the scoop? > --- > > Key: SUREFIRE-1034 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1034 > Project: Maven Surefire > Issue Type: Bug >Reporter: Benson Margulies > > # The doc could really use an example of dependenciesToScan > # The doc should tell me the syntax for using classifiers > # if classifiers don't work, please make them work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1194) reporter argument does not work for TestNG
[ https://issues.apache.org/jira/browse/SUREFIRE-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043906#comment-15043906 ] ASF GitHub Bot commented on SUREFIRE-1194: -- Github user Tibor17 commented on the pull request: https://github.com/apache/maven-surefire/pull/107#issuecomment-162320804 @juherr I updated the comment. I don't mean this weekend. We still have one week left. > reporter argument does not work for TestNG > -- > > Key: SUREFIRE-1194 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1194 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.19 >Reporter: Testo Nakada >Assignee: Tibor Digana > Fix For: 2.19.1 > > > TestNG plugin seems to map -reporter command line parameter to reporterslist > which was removed in TestNG project since 2010 > (a4779524b59330e98ee596c5faa43ae1b33ff844). Therefore, this configuration has > stopped working since then. The configuration mentioned in > http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html#Using_Custom_Listeners_and_Reporters > does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRESOURCES-203) Add a skip option to skip the execution of resources goal
[
https://issues.apache.org/jira/browse/MRESOURCES-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MRESOURCES-203.
--
Resolution: Fixed
Assignee: Karl Heinz Marbaise
Fixed in [r1718188|http://svn.apache.org/r1718188]
> Add a skip option to skip the execution of resources goal
> -
>
> Key: MRESOURCES-203
> URL: https://issues.apache.org/jira/browse/MRESOURCES-203
> Project: Maven Resources Plugin
> Issue Type: New Feature
>Reporter: Laurent TOURREAU
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>
> We should have the possibility to skip the execution of resources plugin by
> settings a skip tag:
> {code}true{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MRESOURCES-203) Add a skip option to skip the execution of resources goal
[
https://issues.apache.org/jira/browse/MRESOURCES-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043936#comment-15043936
]
Hudson commented on MRESOURCES-203:
---
SUCCESS: Integrated in maven-plugins #4856 (See
[https://builds.apache.org/job/maven-plugins/4856/])
[MRESOURCES-203] Add a skip option to skip the execution of resources goal
Added the skip option for resources goal as well as an integration test.
(khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1718188])
* maven-resources-plugin/src/it/skip-yes
* maven-resources-plugin/src/it/skip-yes/pom.xml
* maven-resources-plugin/src/it/skip-yes/src
* maven-resources-plugin/src/it/skip-yes/src/main
* maven-resources-plugin/src/it/skip-yes/src/main/resources
* maven-resources-plugin/src/it/skip-yes/src/main/resources/test-resource.txt
* maven-resources-plugin/src/it/skip-yes/verify.groovy
*
maven-resources-plugin/src/main/java/org/apache/maven/plugin/resources/ResourcesMojo.java
> Add a skip option to skip the execution of resources goal
> -
>
> Key: MRESOURCES-203
> URL: https://issues.apache.org/jira/browse/MRESOURCES-203
> Project: Maven Resources Plugin
> Issue Type: New Feature
>Reporter: Laurent TOURREAU
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>
> We should have the possibility to skip the execution of resources plugin by
> settings a skip tag:
> {code}true{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MCHECKSTYLE-314) checkstyle:check should invoke the execution of this plugin's goal "checkstyle" prior to executing itself
Roman Ivanov created MCHECKSTYLE-314: Summary: checkstyle:check should invoke the execution of this plugin's goal "checkstyle" prior to executing itself Key: MCHECKSTYLE-314 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-314 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.17 Reporter: Roman Ivanov I run into problem with using checkstyles goal "checkstyle:check" in sevntu.checkstyle project (https://github.com/sevntu-checkstyle/sevntu.checkstyle/blob/master/sevntu-checks/pom.xml#L75) as it always use default sun config when I run "checkstyle:check", It took me a while to figure out why that does not work. I had a habit and convenience to run in such a ways pmd and findbug, just "mvn pmd:check", "mvn findbug:check" it is human friendly. PMD and Findbugs plugins already do this: http://gleclaire.github.io/findbugs-maven-plugin/check-mojo.html https://maven.apache.org/plugins/maven-pmd-plugin/check-mojo.html search for "Invokes the execution of this plugin's goal" vs http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html Problem was also raised at : http://stackoverflow.com/questions/11106767/maven-checkstylecheck-not-working Please add support of this, most users are not professionals in Maven. I use Maven for many years and it took me too much time to find a reason why it does not work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MCHECKSTYLE-314) checkstyle:check should invoke the execution of this plugin's goal "checkstyle" prior to executing itself
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Ivanov updated MCHECKSTYLE-314: - Description: I run into problem with using checkstyles goal "checkstyle:check" in sevntu.checkstyle project (https://github.com/sevntu-checkstyle/sevntu.checkstyle/blob/master/sevntu-checks/pom.xml#L75) as it always use default Sun config when I run "checkstyle:check", It took me a while to figure out why that does not work. I had a habit and convenience to run in such a ways pmd and findbug, just "mvn pmd:check", "mvn findbug:check" it is human friendly. PMD and Findbugs plugins already do this: http://gleclaire.github.io/findbugs-maven-plugin/check-mojo.html https://maven.apache.org/plugins/maven-pmd-plugin/check-mojo.html search for "Invokes the execution of this plugin's goal" vs http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html Problem was also raised at : http://stackoverflow.com/questions/11106767/maven-checkstylecheck-not-working Please add support of this, most users are not professionals in Maven. I use Maven for many years and it took me too much time to find a reason why it does not work. was: I run into problem with using checkstyles goal "checkstyle:check" in sevntu.checkstyle project (https://github.com/sevntu-checkstyle/sevntu.checkstyle/blob/master/sevntu-checks/pom.xml#L75) as it always use default sun config when I run "checkstyle:check", It took me a while to figure out why that does not work. I had a habit and convenience to run in such a ways pmd and findbug, just "mvn pmd:check", "mvn findbug:check" it is human friendly. PMD and Findbugs plugins already do this: http://gleclaire.github.io/findbugs-maven-plugin/check-mojo.html https://maven.apache.org/plugins/maven-pmd-plugin/check-mojo.html search for "Invokes the execution of this plugin's goal" vs http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html Problem was also raised at : http://stackoverflow.com/questions/11106767/maven-checkstylecheck-not-working Please add support of this, most users are not professionals in Maven. I use Maven for many years and it took me too much time to find a reason why it does not work. > checkstyle:check should invoke the execution of this plugin's goal > "checkstyle" prior to executing itself > - > > Key: MCHECKSTYLE-314 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-314 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.17 >Reporter: Roman Ivanov > > I run into problem with using checkstyles goal "checkstyle:check" in > sevntu.checkstyle project > (https://github.com/sevntu-checkstyle/sevntu.checkstyle/blob/master/sevntu-checks/pom.xml#L75) > as it always use default Sun config when I run "checkstyle:check", It took > me a while to figure out why that does not work. > I had a habit and convenience to run in such a ways pmd and findbug, just > "mvn pmd:check", "mvn findbug:check" it is human friendly. > PMD and Findbugs plugins already do this: > http://gleclaire.github.io/findbugs-maven-plugin/check-mojo.html > https://maven.apache.org/plugins/maven-pmd-plugin/check-mojo.html > search for "Invokes the execution of this plugin's goal" > vs > http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html > Problem was also raised at : > http://stackoverflow.com/questions/11106767/maven-checkstylecheck-not-working > Please add support of this, most users are not professionals in Maven. I use > Maven for many years and it took me too much time to find a reason why it > does not work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1201) Surefire printed TestSuite instead of real name of test
[ https://issues.apache.org/jira/browse/SUREFIRE-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1201: --- Fix Version/s: (was: 2.19.1) > Surefire printed TestSuite instead of real name of test > --- > > Key: SUREFIRE-1201 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1201 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.19 >Reporter: Tibor Digana >Assignee: Tibor Digana > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1201) Surefire printed TestSuite instead of real name of test
[ https://issues.apache.org/jira/browse/SUREFIRE-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1201. -- Resolution: Not A Problem > Surefire printed TestSuite instead of real name of test > --- > > Key: SUREFIRE-1201 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1201 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.19 >Reporter: Tibor Digana >Assignee: Tibor Digana > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1179) TestNG parallel options seem to not be honored
[ https://issues.apache.org/jira/browse/SUREFIRE-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044051#comment-15044051 ] ASF GitHub Bot commented on SUREFIRE-1179: -- Github user Tibor17 commented on the pull request: https://github.com/apache/maven-surefire/pull/106#issuecomment-162337794 @juherr I guess this was already merged in Version 2.19. You can close the pull-request. Thx > TestNG parallel options seem to not be honored > -- > > Key: SUREFIRE-1179 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1179 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.18.1 > Environment: Windows 7 x64, Java 8 (1.8.0_60), TestNG v6.9.6, Maven > Surefire version 2.18.1 >Reporter: Jeff Vincent >Assignee: Tibor Digana > Fix For: 2.19 > > Attachments: testng-test.zip > > > I have some simple tests I'm trying to configure to run in parallel using > Maven 3.3.3 and the latest versions of TestNG. I've set my POM file to the > following: > > org.apache.maven.plugins > maven-surefire-plugin > 2.18.1 > > methods > 50 > > > When I run in parallel, I only get 10 threads no matter the setting and I can > not change it. I've tried adding the annotation parameter to the method as > well: > @Test(dataProvider = "dataProvider", threadPoolSize = 50) > Nothing seems to help. I have a simple project that illustrates what I'm > seeing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work
[ https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1191: --- Issue Type: Improvement (was: Wish) > Run Single Test with Package Name Doesn't work > -- > > Key: SUREFIRE-1191 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1191 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.19 >Reporter: Gunnar Schmidt >Assignee: Tibor Digana > Fix For: 2.19.1 > > > Running the following command works: > mvn test -Dtest=MyTestCaseTest#myTest > This doesn't work (package name included): > mvn test -Dtest=my.package.name.MyTestCaseTest#myTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work
[ https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044103#comment-15044103 ] Dan Tran commented on SUREFIRE-1191: Please deploy 2.19.1-SNAPSHOT for testing. I only see 2.20-SNAPSHOT > Run Single Test with Package Name Doesn't work > -- > > Key: SUREFIRE-1191 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1191 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.19 >Reporter: Gunnar Schmidt >Assignee: Tibor Digana > Fix For: 2.19.1 > > > Running the following command works: > mvn test -Dtest=MyTestCaseTest#myTest > This doesn't work (package name included): > mvn test -Dtest=my.package.name.MyTestCaseTest#myTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SUREFIRE-756) Allow ability to capture executed random runOrder for re-play purposes
[ https://issues.apache.org/jira/browse/SUREFIRE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-756: -- Comment: was deleted (was: The solution would be to use the existing "includesFile" parameter. The excludesFile should not work together with runOrder. The functionality "runOrder" creates file name which starts with ".surefire-" in base dir. We can recognize the File name in the form of + ".surefire-" or + ".surefire-*" and configurationHash will computed upon current plugin configuration. The format for files produced by runOrder and includesFile are different, we can load only the name of the test upon regognized file patter ".surefire-*" in base dir. Any objections to this concept?) > Allow ability to capture executed random runOrder for re-play purposes > -- > > Key: SUREFIRE-756 > URL: https://issues.apache.org/jira/browse/SUREFIRE-756 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.9 >Reporter: Josh Spiewak >Assignee: Tibor Digana >Priority: Minor > > As a user of the runOrder=random feature, I would like to be able to capture > a given ordering of tests and re-play that order, so that if a particular > ordering exposes hidden dependencies between tests I can reproduce in my > development environment, fix the problem, and then runs the tests again to > confirm the fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1119) Run tests without order
[ https://issues.apache.org/jira/browse/SUREFIRE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044107#comment-15044107 ] Tibor Digana commented on SUREFIRE-1119: [~malahovskys] I don't think the feature would be realistic because the pattern can be regex. The only way would be to provide a programmatic API to specify test filter by customer in Surefire 3.0. WDYT? > Run tests without order > --- > > Key: SUREFIRE-1119 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1119 > Project: Maven Surefire > Issue Type: Wish >Affects Versions: 2.18 >Reporter: Sergey Malahovsky >Assignee: Tibor Digana >Priority: Minor > > It will be great to have ability to run tests in direct order without any > sorting. > For example: > > > **/*CTestSuite* > **/*ATestSuite* > **/*BTestSuite* > >direct > > In current solution test suites will be sorted by alphabetical (or another > order): **/*ATestSuite*, **/*BTestSuite*, **/*CTestSuite*. > But sometimes it needs to run without any sorting in order as specified in > / tags: **/*CTestSuite*, **/*ATestSuite*, **/*BTestSuite*. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1191) Run Single Test with Package Name Doesn't work
[ https://issues.apache.org/jira/browse/SUREFIRE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044109#comment-15044109 ] Tibor Digana commented on SUREFIRE-1191: Just use 2.20-SNAPSHOT from Maven Central. Current snapshot version is only formal not important. We will release it as 2.19 in several days. > Run Single Test with Package Name Doesn't work > -- > > Key: SUREFIRE-1191 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1191 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.19 >Reporter: Gunnar Schmidt >Assignee: Tibor Digana > Fix For: 2.19.1 > > > Running the following command works: > mvn test -Dtest=MyTestCaseTest#myTest > This doesn't work (package name included): > mvn test -Dtest=my.package.name.MyTestCaseTest#myTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-470) Upgrade maven-shared-components parent to version 22
Karl Heinz Marbaise created MSHARED-470: --- Summary: Upgrade maven-shared-components parent to version 22 Key: MSHARED-470 URL: https://issues.apache.org/jira/browse/MSHARED-470 Project: Maven Shared Components Issue Type: Improvement Components: maven-dependency-analyzer Affects Versions: maven-dependency-analyzer-1.7 Reporter: Karl Heinz Marbaise Fix For: maven-dependency-analyzer-1.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSHARED-470) Upgrade maven-shared-components parent to version 22
[ https://issues.apache.org/jira/browse/MSHARED-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-470. --- Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1718218|http://svn.apache.org/r1718218] > Upgrade maven-shared-components parent to version 22 > > > Key: MSHARED-470 > URL: https://issues.apache.org/jira/browse/MSHARED-470 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-analyzer >Affects Versions: maven-dependency-analyzer-1.7 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise > Fix For: maven-dependency-analyzer-1.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-471) Upgrade maven-shared-components parent to version 22
Karl Heinz Marbaise created MSHARED-471: --- Summary: Upgrade maven-shared-components parent to version 22 Key: MSHARED-471 URL: https://issues.apache.org/jira/browse/MSHARED-471 Project: Maven Shared Components Issue Type: Improvement Components: maven-shared-io Reporter: Karl Heinz Marbaise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHARED-471) Upgrade maven-shared-components parent to version 22
[ https://issues.apache.org/jira/browse/MSHARED-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-471: Fix Version/s: maven-shared-io-3.0.0 > Upgrade maven-shared-components parent to version 22 > > > Key: MSHARED-471 > URL: https://issues.apache.org/jira/browse/MSHARED-471 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-io >Reporter: Karl Heinz Marbaise > Fix For: maven-shared-io-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSHARED-471) Upgrade maven-shared-components parent to version 22
[ https://issues.apache.org/jira/browse/MSHARED-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-471. --- Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1718219|http://svn.apache.org/r1718219] > Upgrade maven-shared-components parent to version 22 > > > Key: MSHARED-471 > URL: https://issues.apache.org/jira/browse/MSHARED-471 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-io >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise > Fix For: maven-shared-io-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-472) Upgrade maven-shared-utils to 3.0.0
Karl Heinz Marbaise created MSHARED-472: --- Summary: Upgrade maven-shared-utils to 3.0.0 Key: MSHARED-472 URL: https://issues.apache.org/jira/browse/MSHARED-472 Project: Maven Shared Components Issue Type: Improvement Components: maven-shared-io Affects Versions: maven-shared-io-3.0.0 Reporter: Karl Heinz Marbaise Priority: Minor Fix For: maven-shared-io-3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSHARED-472) Upgrade maven-shared-utils to 3.0.0
[ https://issues.apache.org/jira/browse/MSHARED-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-472. --- Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1718220|http://svn.apache.org/r1718220] > Upgrade maven-shared-utils to 3.0.0 > --- > > Key: MSHARED-472 > URL: https://issues.apache.org/jira/browse/MSHARED-472 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-io >Affects Versions: maven-shared-io-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-shared-io-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-473) Upgrade Maven 3.X Only JDK 1.6
Karl Heinz Marbaise created MSHARED-473: --- Summary: Upgrade Maven 3.X Only JDK 1.6 Key: MSHARED-473 URL: https://issues.apache.org/jira/browse/MSHARED-473 Project: Maven Shared Components Issue Type: Improvement Components: maven-shared-io Affects Versions: maven-shared-io-3.0.0 Reporter: Karl Heinz Marbaise Fix For: maven-shared-io-3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSHARED-473) Upgrade Maven 3.X Only JDK 1.6
[ https://issues.apache.org/jira/browse/MSHARED-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-473. --- Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1718222|http://svn.apache.org/r1718222] > Upgrade Maven 3.X Only JDK 1.6 > -- > > Key: MSHARED-473 > URL: https://issues.apache.org/jira/browse/MSHARED-473 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-io >Affects Versions: maven-shared-io-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise > Fix For: maven-shared-io-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MASSEMBLY-790) Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MASSEMBLY-790: -- Summary: Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0 (was: Upgrade maven-archiver/maven-filtering to 3.0.0) > Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0 > - > > Key: MASSEMBLY-790 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-790 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MASSEMBLY-790) Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MASSEMBLY-790. - Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1718224|http://svn.apache.org/r1718224] > Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0 > - > > Key: MASSEMBLY-790 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-790 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHARED-471) Upgrade maven-shared-components parent to version 22
[ https://issues.apache.org/jira/browse/MSHARED-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044163#comment-15044163 ] Hudson commented on MSHARED-471: SUCCESS: Integrated in maven-shared #816 (See [https://builds.apache.org/job/maven-shared/816/]) [MSHARED-471] Upgrade maven-shared-components parent to version 22 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1718219]) * maven-shared-io/pom.xml > Upgrade maven-shared-components parent to version 22 > > > Key: MSHARED-471 > URL: https://issues.apache.org/jira/browse/MSHARED-471 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-io >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise > Fix For: maven-shared-io-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHARED-472) Upgrade maven-shared-utils to 3.0.0
[ https://issues.apache.org/jira/browse/MSHARED-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044164#comment-15044164 ] Hudson commented on MSHARED-472: SUCCESS: Integrated in maven-shared #816 (See [https://builds.apache.org/job/maven-shared/816/]) [MSHARED-472] Upgrade maven-shared-utils to 3.0.0 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1718220]) * maven-shared-io/pom.xml > Upgrade maven-shared-utils to 3.0.0 > --- > > Key: MSHARED-472 > URL: https://issues.apache.org/jira/browse/MSHARED-472 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-io >Affects Versions: maven-shared-io-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-shared-io-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHARED-473) Upgrade Maven 3.X Only JDK 1.6
[ https://issues.apache.org/jira/browse/MSHARED-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044165#comment-15044165 ] Hudson commented on MSHARED-473: SUCCESS: Integrated in maven-shared #816 (See [https://builds.apache.org/job/maven-shared/816/]) [MSHARED-473] Upgrade Maven 3.X Only JDK 1.6 Upgraded to Maven 3.0 minimum Upgraded wagon-providate-api to 2.10 Upgraded plexus-utils to 3.0.22 Removed optional dependency plexus-container-default Added junit 4.11 test dependency (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1718222]) * maven-shared-io/pom.xml * maven-shared-io/src/test/java/org/apache/maven/shared/io/location/ArtifactLocatorStrategyTest.java > Upgrade Maven 3.X Only JDK 1.6 > -- > > Key: MSHARED-473 > URL: https://issues.apache.org/jira/browse/MSHARED-473 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-io >Affects Versions: maven-shared-io-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise > Fix For: maven-shared-io-3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHARED-470) Upgrade maven-shared-components parent to version 22
[ https://issues.apache.org/jira/browse/MSHARED-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044162#comment-15044162 ] Hudson commented on MSHARED-470: SUCCESS: Integrated in maven-shared #816 (See [https://builds.apache.org/job/maven-shared/816/]) [MSHARED-470] Upgrade maven-shared-components parent to version 22 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1718218]) * maven-dependency-analyzer/pom.xml > Upgrade maven-shared-components parent to version 22 > > > Key: MSHARED-470 > URL: https://issues.apache.org/jira/browse/MSHARED-470 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-analyzer >Affects Versions: maven-dependency-analyzer-1.7 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise > Fix For: maven-dependency-analyzer-1.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MJAVADOC-437) javadoc:aggregate fails on initial build
[
https://issues.apache.org/jira/browse/MJAVADOC-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044168#comment-15044168
]
Harald Wellmann commented on MJAVADOC-437:
--
The point is, the test needs at least one external dependency for the bug to
show.
javadoc will see all the _sources_ of the current reactor, even when the
dependencies can't be resolved. But if a module has an internal and an external
dependency, failure of resolving the internal one will lead to _all_
dependencies being skipped. The choice of {{commons-io}} as external dependency
is completely arbitrary.
I've cleaned up all the unnecessary dependencies and other stuff I overlooked.
Thanks for the review!
> javadoc:aggregate fails on initial build
>
>
> Key: MJAVADOC-437
> URL: https://issues.apache.org/jira/browse/MJAVADOC-437
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10.3
>Reporter: Harald Wellmann
>Assignee: Michael Osipov
>
> h3. Scenario
> Take a SNAPSHOT version of a reactor project with at least two JAR modules.
> Assume that no artifacts of the given SNAPSHOT version have been built before
> (this is usually the case just after running release:perform).
> h3. Actual Behaviour
> Now run {{mvn javadoc:aggregate}}. This build fails in the forked lifecycle.
> maven-javadoc-plugin unnecessarily tries to resolve the JAR artifacts of the
> current reactor (which are not avialable yet) and add them to the Javadoc
> classpath.
> h3. Expected Behaviour
> Aggregated Javadoc should be generated without problems. It is sufficient to
> take the sources of the current reactor and only put *external* dependencies
> on the Javadoc classpath.
> This is a duplicate of an 8 year old bug MJAVADOC-116 with 51 votes which has
> been closed without being fixed.
> A patch for this problem was submitted in MJAVADOC-362, but does not seem to
> have received attention by committers. (I admit the problem description is
> not very clear.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSHARED-474) Upgrade maven-shared-io to 3.0.0
Karl Heinz Marbaise created MSHARED-474: --- Summary: Upgrade maven-shared-io to 3.0.0 Key: MSHARED-474 URL: https://issues.apache.org/jira/browse/MSHARED-474 Project: Maven Shared Components Issue Type: Improvement Components: file-management Affects Versions: file-management-3.0.0 Reporter: Karl Heinz Marbaise Priority: Blocker Fix For: file-management-3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MASSEMBLY-790) Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044169#comment-15044169 ] Hudson commented on MASSEMBLY-790: -- FAILURE: Integrated in maven-plugins #4857 (See [https://builds.apache.org/job/maven-plugins/4857/]) [MASSEMBLY-790] Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0 Upgrade maven-archiver to 3.0.0 Upgrade maven-filtering to 3.0.0 Upgrade maven-common-artifact-filters to 3.0.0 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1718224]) * maven-assembly-plugin/pom.xml * maven-assembly-plugin/src/main/java/org/apache/maven/plugins/assembly/format/ReaderFormatter.java > Upgrade maven-archiver/maven-filtering/maven-common-artifact-filters to 3.0.0 > - > > Key: MASSEMBLY-790 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-790 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DOXIATOOLS-53) move doxia-integration-tools from Doxia Tools to Doxia Sitetools
Hervé Boutemy created DOXIATOOLS-53: --- Summary: move doxia-integration-tools from Doxia Tools to Doxia Sitetools Key: DOXIATOOLS-53 URL: https://issues.apache.org/jira/browse/DOXIATOOLS-53 Project: Maven Doxia Tools Issue Type: Task Components: Doxia Integration Tools Affects Versions: doxia-integration-tools-1.6 Reporter: Hervé Boutemy a little bit like DOXIA-TOOLS-52 but without dropping the artifact -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-5943) Build Failure due to NoClassDefFoundException: org/eclipse/aether/spi/connector/Transfer$State
Adarsh Kumar Maurya created MNG-5943:
Summary: Build Failure due to NoClassDefFoundException:
org/eclipse/aether/spi/connector/Transfer$State
Key: MNG-5943
URL: https://issues.apache.org/jira/browse/MNG-5943
Project: Maven
Issue Type: Bug
Components: Class Loading
Affects Versions: 3.3.9
Environment: Apache Maven 3.3.9
(bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30)
Maven home: D:\16.Maven\apache-maven-3.3.9\bin\..
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_51\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
Reporter: Adarsh Kumar Maurya
Priority: Minor
Fix For: 3.3.9
Mentioned below are the steps which results in Exception:
*Step 1.*
mvn -X install:install-file
-Dfile=%ANDROID_HOME%\platforms\android-21\android.jar
-DgroupId=com.google.android -DartifactId=android -Dversion=5.0.1_r2
-Dpackaging=jar -DgeneratePom=true>>log.txt
*Step 2.*
mvn -X archetype:generate -DarchetypeArtifactId=android-quickstart
-DarchetypeGroupId=de.akquinet.android.archetypes -DarchetypeVersion=1.1.0
-DgroupId=com.packt.androidMaven -DartifactId=chapter -Dversion=1.0-SNAPSHOT
-Dplatform=21 --batch-mode --quiet>>log.txt
*Step 3.* Check tag. If it is empty change to above used.
*Step 4.* D:\16.Maven\chapter>mvn -X build>log.txt
It results in below mentioned exceptions:
{
Exception in thread "pool-1-thread-1" java.lang.NoClassDefFoundError:
org/eclipse/aether/spi/connector/Transfer$State
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608)
at
org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.aether.spi.connector.Transfer$State
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
... 5 more
Exception in thread "main" java.lang.NoClassDefFoundError:
org/eclipse/aether/spi/connector/Transfer$State
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608)
at
org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.aether.spi.connector.Transfer$State
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
... 5 more
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-5943) Build Failure due to NoClassDefFoundException: org/eclipse/aether/spi/connector/Transfer$State
[
https://issues.apache.org/jira/browse/MNG-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adarsh Kumar Maurya updated MNG-5943:
-
Priority: Major (was: Minor)
> Build Failure due to NoClassDefFoundException:
> org/eclipse/aether/spi/connector/Transfer$State
> --
>
> Key: MNG-5943
> URL: https://issues.apache.org/jira/browse/MNG-5943
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30)
> Maven home: D:\16.Maven\apache-maven-3.3.9\bin\..
> Java version: 1.7.0_51, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_51\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: Adarsh Kumar Maurya
> Labels: github-import
> Fix For: 3.3.9
>
>
> Mentioned below are the steps which results in Exception:
> *Step 1.*
> mvn -X install:install-file
> -Dfile=%ANDROID_HOME%\platforms\android-21\android.jar
> -DgroupId=com.google.android -DartifactId=android -Dversion=5.0.1_r2
> -Dpackaging=jar -DgeneratePom=true>>log.txt
> *Step 2.*
> mvn -X archetype:generate -DarchetypeArtifactId=android-quickstart
> -DarchetypeGroupId=de.akquinet.android.archetypes -DarchetypeVersion=1.1.0
> -DgroupId=com.packt.androidMaven -DartifactId=chapter -Dversion=1.0-SNAPSHOT
> -Dplatform=21 --batch-mode --quiet>>log.txt
> *Step 3.* Check tag. If it is empty change to above used.
>
> *Step 4.* D:\16.Maven\chapter>mvn -X build>log.txt
> It results in below mentioned exceptions:
> {
> Exception in thread "pool-1-thread-1" java.lang.NoClassDefFoundError:
> org/eclipse/aether/spi/connector/Transfer$State
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608)
> at
> org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.aether.spi.connector.Transfer$State
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ... 5 more
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/eclipse/aether/spi/connector/Transfer$State
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608)
> at
> org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.aether.spi.connector.Transfer$State
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ... 5 more
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
