[jira] (SUREFIRE-1077) NPE problem will happen if you set testng status to fail at afterInvocation method

[ https://jira.codehaus.org/browse/SUREFIRE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1077: - Description: In our test program, we have some soft assert, which require us set the test

[jira] (SUREFIRE-1096) ClassCastException: Fork test for TestNG with xmlsuite

[ https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1096: - Description: When i setup surefire for forking tests via: {code} 3 true false {code} And i

[jira] (SUREFIRE-1024) "verify" goal ignores "dependenciesToScan" parameter when checking tests existence

[ https://jira.codehaus.org/browse/SUREFIRE-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1024: - Fix Version/s: (was: 2.18) 3.0 > "verify" goal ignores "dependencies

[jira] (SUREFIRE-1034) dependencesToScan versus classifiers: what's the scoop?

[ https://jira.codehaus.org/browse/SUREFIRE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1034: - Fix Version/s: (was: 2.18) 3.0 > dependencesToScan versus classifier

[jira] (SUREFIRE-749) Parallel methods should run in separate classloaders

[ https://jira.codehaus.org/browse/SUREFIRE-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353311#comment-353311 ] Andreas Gudian commented on SUREFIRE-749: - > You didn't explain how one would implement t

[jira] (SUREFIRE-1099) Invalid link ids in surefire-report

Andreas Gudian created SUREFIRE-1099: Summary: Invalid link ids in surefire-report Key: SUREFIRE-1099 URL: https://jira.codehaus.org/browse/SUREFIRE-1099 Project: Maven Surefire Issue Typ

[jira] (SUREFIRE-1099) Invalid link ids in surefire-report

[ https://jira.codehaus.org/browse/SUREFIRE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1099: - Fix Version/s: 2.18 > Invalid link ids in surefire-report > ---

[jira] (SUREFIRE-1099) Invalid link ids in surefire-report

[ https://jira.codehaus.org/browse/SUREFIRE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-1099: Assignee: Andreas Gudian > Invalid link ids in surefire-report >

[jira] (SUREFIRE-1099) Invalid link ids in surefire-report

[ https://jira.codehaus.org/browse/SUREFIRE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1099. Resolution: Fixed PR merged and pushed to master. Thanks, kermit-the-frog! > Invalid link id

[jira] (SUREFIRE-1084) Surefire-report stack traces appear on a single line.

[ https://jira.codehaus.org/browse/SUREFIRE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353316#comment-353316 ] Andreas Gudian commented on SUREFIRE-1084: -- I'm unsure about merging the PR, as I think

[jira] (SUREFIRE-1072) Duplicate example of commandline in run single test documentation

[ https://jira.codehaus.org/browse/SUREFIRE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-1072: Assignee: Andreas Gudian > Duplicate example of commandline in run single test docume

[jira] (SUREFIRE-1072) Duplicate example of commandline in run single test documentation

[ https://jira.codehaus.org/browse/SUREFIRE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1072. Resolution: Fixed Fixed the documentation. Thanks for the report! > Duplicate example of com

[jira] (SUREFIRE-1077) NPE problem will happen if you set testng status to fail at afterInvocation method

[ https://jira.codehaus.org/browse/SUREFIRE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1077. Resolution: Fixed Fixed. I re-used your example in a new integration test. If you feel like

[jira] (SUREFIRE-1088) When test fail during initialization the test execution time can result in a large negative number.

[ https://jira.codehaus.org/browse/SUREFIRE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35#comment-35 ] Andreas Gudian commented on SUREFIRE-1088: -- I'm having trouble reproducing it. You fill

[jira] (SUREFIRE-1096) ClassCastException: Fork test for TestNG with xmlsuite

[ https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1096. Resolution: Fixed For now, I committed a fix that lets surefire not crash when using forkCoun

[jira] (SUREFIRE-1100) Support suiteXmlFiles and forkCount>1 with reuseForks=true

Andreas Gudian created SUREFIRE-1100: Summary: Support suiteXmlFiles and forkCount>1 with reuseForks=true Key: SUREFIRE-1100 URL: https://jira.codehaus.org/browse/SUREFIRE-1100 Project: Maven Suref

[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized

[ https://jira.codehaus.org/browse/SUREFIRE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353508#comment-353508 ] Andreas Gudian commented on SUREFIRE-1082: -- @Tibor: when closing as Not A Bug, please r

[jira] (SUREFIRE-1088) When test fail during initialization the test execution time can result in a large negative number.

[ https://jira.codehaus.org/browse/SUREFIRE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353732#comment-353732 ] Andreas Gudian commented on SUREFIRE-1088: -- @Daniel: your surefire configuration would

[jira] (SUREFIRE-1104) Internal Maven Surefire IT tests fail with Maven 3.2.x

[ https://jira.codehaus.org/browse/SUREFIRE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353920#comment-353920 ] Andreas Gudian commented on SUREFIRE-1104: -- I'll take a look tonight. > Internal Mave

[jira] (SUREFIRE-1104) Internal Maven Surefire IT tests fail with Maven 3.2.x

[ https://jira.codehaus.org/browse/SUREFIRE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-1104: Assignee: Andreas Gudian > Internal Maven Surefire IT tests fail with Maven 3.2.x > -

[jira] (SUREFIRE-1104) Internal Maven Surefire IT tests fail with Maven 3.2.x

[ https://jira.codehaus.org/browse/SUREFIRE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1104: - Fix Version/s: 2.18 > Internal Maven Surefire IT tests fail with Maven 3.2.x >

[jira] (SUREFIRE-1104) Internal Maven Surefire IT tests fail with Maven 3.2.x

[ https://jira.codehaus.org/browse/SUREFIRE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1104. Resolution: Fixed OK, wasn't exactly "tonight", but I just fixed it... the test passed {{-T 2

[jira] (SUREFIRE-1088) When test fail during initialization the test execution time can result in a large negative number.

[ https://jira.codehaus.org/browse/SUREFIRE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-1088: Assignee: Andreas Gudian > When test fail during initialization the test execution ti

[jira] (SUREFIRE-1104) Internal Maven Surefire IT tests fail with Maven 3.2.x

[ https://jira.codehaus.org/browse/SUREFIRE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354227#comment-354227 ] Andreas Gudian commented on SUREFIRE-1104: -- You're right. I guess my problem was that I

[jira] (SUREFIRE-1104) Internal Maven Surefire IT tests fail with Maven 3.2.x

[ https://jira.codehaus.org/browse/SUREFIRE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354227#comment-354227 ] Andreas Gudian edited comment on SUREFIRE-1104 at 10/11/14 2:41 PM: --

[jira] (SUREFIRE-859) Exception in thread "TreadedStreamConsumer" java.lang.RuntimeException during GC

[ https://jira.codehaus.org/browse/SUREFIRE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354229#comment-354229 ] Andreas Gudian commented on SUREFIRE-859: - This may look more like an issue of the JRE th

[jira] (SUREFIRE-1088) When test fail during initialization the test execution time can result in a large negative number.

[ https://jira.codehaus.org/browse/SUREFIRE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1088. Resolution: Fixed That description was enough for me to be able to finally reporduce it. It'

[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354688#comment-354688 ] Andreas Gudian commented on SUREFIRE-654: - I'll take a closer look on the PR soon-ish.

[jira] (MCHECKSTYLE-255) First checkstyle error is not printed in the console ouput

Andreas Gudian created MCHECKSTYLE-255: -- Summary: First checkstyle error is not printed in the console ouput Key: MCHECKSTYLE-255 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-255 Project: Mav

[jira] (SUREFIRE-1090) NPE in SmartStacktraceParser if Thread.contextCassLoader is null

[ https://jira.codehaus.org/browse/SUREFIRE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-1090: Assignee: Andreas Gudian > NPE in SmartStacktraceParser if Thread.contextCassLoader i

[jira] (SUREFIRE-1090) NPE in SmartStacktraceParser if Thread.contextCassLoader is null

[ https://jira.codehaus.org/browse/SUREFIRE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1090. Resolution: Fixed Rebased and committed the fix. https://git-wip-us.apache.org/repos/asf?p=m

[jira] (SUREFIRE-1078) Failure running forked mode with TestNG test suites defined via XML files

[ https://jira.codehaus.org/browse/SUREFIRE-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-1078. Resolution: Duplicate Fix Version/s: 2.18 Assignee: Andreas Gudian I didn't s

[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-654: --- Assignee: Andreas Gudian > Surefire does not recognize successful tests using TestNG wit

[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354979#comment-354979 ] Andreas Gudian edited comment on SUREFIRE-654 at 10/26/14 7:47 AM:

[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-654: Fix Version/s: 2.18 > Surefire does not recognize successful tests using TestNG with the > in

[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354979#comment-354979 ] Andreas Gudian commented on SUREFIRE-654: - I'll do the review and check why the fix is no

[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354999#comment-354999 ] Andreas Gudian commented on SUREFIRE-654: - I'm afraid I found what's wrong. The test run

[jira] (SUREFIRE-654) Surefire does not recognize successful tests using TestNG with the invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355004#comment-355004 ] Andreas Gudian commented on SUREFIRE-654: - Not perfect, but it looks good to me. The comm

[jira] (SUREFIRE-654) TestNG: Recognize successful tests when using invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-654: Summary: TestNG: Recognize successful tests when using invocationCount and successPercentage p

[jira] (SUREFIRE-654) TestNG: Recognize successful tests when using invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-654: Issue Type: New Feature (was: Bug) > TestNG: Recognize successful tests when using invocation

[jira] (SUREFIRE-1017) Failures do not show test-package since 2.13

[ https://jira.codehaus.org/browse/SUREFIRE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1017: - Fix Version/s: (was: 2.18) 2.19 > Failures do not show test-package

[jira] (SUREFIRE-654) TestNG: Recognize successful tests when using invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-654. --- Resolution: Fixed Closing as fixed for now. A better interaction with the new "Flaky" tests fea

[jira] (SUREFIRE-1053) Suppress warning message if file.encoding is set using argLine

[ https://jira.codehaus.org/browse/SUREFIRE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355143#comment-355143 ] Andreas Gudian edited comment on SUREFIRE-1053 at 10/29/14 4:09 AM: --

[jira] (SUREFIRE-1053) Suppress warning message if file.encoding is set using argLine

[ https://jira.codehaus.org/browse/SUREFIRE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355143#comment-355143 ] Andreas Gudian commented on SUREFIRE-1053: -- > Can you elaborate on that last part? "ano

[jira] (SUREFIRE-1053) Suppress warning message if file.encoding is set using argLine

[ https://jira.codehaus.org/browse/SUREFIRE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355167#comment-355167 ] Andreas Gudian commented on SUREFIRE-1053: -- Tibor would have to say for sure, but as I

[jira] (SUREFIRE-654) TestNG: Recognize successful tests when using invocationCount and successPercentage parameters on the @Test annotation

[ https://jira.codehaus.org/browse/SUREFIRE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355183#comment-355183 ] Andreas Gudian commented on SUREFIRE-654: - Very soon. I'd like to start the release proce

[jira] (SUREFIRE-1053) Suppress warning message if file.encoding is set using argLine

[ https://jira.codehaus.org/browse/SUREFIRE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355189#comment-355189 ] Andreas Gudian commented on SUREFIRE-1053: -- OK, looking at the code more closely, it se

[jira] (SUREFIRE-1053) Suppress warning message if file.encoding is set using argLine

[ https://jira.codehaus.org/browse/SUREFIRE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355192#comment-355192 ] Andreas Gudian commented on SUREFIRE-1053: -- I usually don't make any fuzz about the dis

[jira] (SUREFIRE-779) Surefire reports wrong number of failed tests when using JUnit's ErrorCollector rule

[ https://jira.codehaus.org/browse/SUREFIRE-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355203#comment-355203 ] Andreas Gudian commented on SUREFIRE-779: - JUnit and likewise TestNG do ensure that diffe

[jira] (SUREFIRE-1053) Suppress warning message if file.encoding is set using argLine

[ https://jira.codehaus.org/browse/SUREFIRE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355218#comment-355218 ] Andreas Gudian commented on SUREFIRE-1053: -- That bild above pushes the snapshots to htt

[jira] (SUREFIRE-1112) Remove uneccessary newlines in console output for test results with no error

[ https://jira.codehaus.org/browse/SUREFIRE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned SUREFIRE-1112: Assignee: Andreas Gudian > Remove uneccessary newlines in console output for test res

[jira] (SUREFIRE-1112) Remove uneccessary newlines in console output for test results with no error

Andreas Gudian created SUREFIRE-1112: Summary: Remove uneccessary newlines in console output for test results with no error Key: SUREFIRE-1112 URL: https://jira.codehaus.org/browse/SUREFIRE-1112 P

[jira] (SUREFIRE-1113) Build does not fail when successPercentage for @org.testng.annotations.Test() is not met

[ https://jira.codehaus.org/browse/SUREFIRE-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355588#comment-355588 ] Andreas Gudian commented on SUREFIRE-1113: -- I am pretty sure this is a duplicate of SUR

[jira] [Commented] (MCOMPILER-203) Allow compiler-plugin to specify annotation processor dependencies

[ https://issues.apache.org/jira/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094924#comment-15094924 ] Andreas Gudian commented on MCOMPILER-203: -- [~dmlloyd]: my advice would be mak

[jira] [Closed] (MCOMPILER-203) Allow compiler-plugin to specify annotation processor dependencies

[ https://issues.apache.org/jira/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed MCOMPILER-203. Resolution: Fixed > Allow compiler-plugin to specify annotation processor dependencies >

[jira] [Resolved] (MCOMPILER-261) Require Maven 3 for maven-compiler-plugin

[ https://issues.apache.org/jira/browse/MCOMPILER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian resolved MCOMPILER-261. -- Resolution: Fixed > Require Maven 3 for maven-compiler-plugin > -

[jira] [Created] (MCOMPILER-261) Require Maven 3 for maven-compiler-plugin

Andreas Gudian created MCOMPILER-261: Summary: Require Maven 3 for maven-compiler-plugin Key: MCOMPILER-261 URL: https://issues.apache.org/jira/browse/MCOMPILER-261 Project: Maven Compiler Plugin

[jira] [Updated] (MCOMPILER-261) Require Maven 3 for maven-compiler-plugin

[ https://issues.apache.org/jira/browse/MCOMPILER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated MCOMPILER-261: - Fix Version/s: (was: 3.5) > Require Maven 3 for maven-compiler-plugin > ---

[jira] [Reopened] (MCOMPILER-261) Require Maven 3 for maven-compiler-plugin

[ https://issues.apache.org/jira/browse/MCOMPILER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reopened MCOMPILER-261: -- > Require Maven 3 for maven-compiler-plugin > - >

[jira] [Closed] (MCOMPILER-261) Require Maven 3 for maven-compiler-plugin

[ https://issues.apache.org/jira/browse/MCOMPILER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed MCOMPILER-261. Resolution: Duplicate Damn, we had an issue for it already... ;) > Require Maven 3 for m

[jira] [Assigned] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more

[ https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned MCOMPILER-235: Assignee: Andreas Gudian > duplicate classes due to MCOMPILER-157 when compiler

[jira] [Commented] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more

[ https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1594#comment-1594 ] Andreas Gudian commented on MCOMPILER-235: -- I've just committed a possible fix

[jira] [Commented] (MCOMPILER-203) Allow compiler-plugin to specify annotation processor dependencies

[ https://issues.apache.org/jira/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111204#comment-15111204 ] Andreas Gudian commented on MCOMPILER-203: -- [~natros], please don't hijack thi

[jira] [Updated] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more

[ https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated MCOMPILER-235: - Fix Version/s: 2.5.1 > duplicate classes due to MCOMPILER-157 when compiler is called t

[jira] [Closed] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more

[ https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed MCOMPILER-235. Resolution: Fixed > duplicate classes due to MCOMPILER-157 when compiler is called twice

[jira] [Commented] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more

[ https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120092#comment-15120092 ] Andreas Gudian commented on MCOMPILER-235: -- Thanks for trying it out! I've ex

[jira] [Created] (MCOMPILER-262) When using annotationProcessorPaths, the project dependencies must not be added as well

Andreas Gudian created MCOMPILER-262: Summary: When using annotationProcessorPaths, the project dependencies must not be added as well Key: MCOMPILER-262 URL: https://issues.apache.org/jira/browse/MCOMPILER-26

[jira] [Closed] (MCOMPILER-262) When using annotationProcessorPaths, the project dependencies must not be added as well

[ https://issues.apache.org/jira/browse/MCOMPILER-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed MCOMPILER-262. Resolution: Fixed > When using annotationProcessorPaths, the project dependencies must no

[jira] [Commented] (SUREFIRE-1137) Problem with Umlauts in stdout

[ https://issues.apache.org/jira/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126899#comment-15126899 ] Andreas Gudian commented on SUREFIRE-1137: -- [~michael-o], well, that's too lon

[jira] [Commented] (SUREFIRE-1220) Surefire never outputs UTF-8 under Windows

[ https://issues.apache.org/jira/browse/SUREFIRE-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126922#comment-15126922 ] Andreas Gudian commented on SUREFIRE-1220: -- > 3. if redirectTestOutputToFile i

[jira] [Commented] (MCOMPILER-240) Generated sources directory should not be added to compiler's source roots

[ https://issues.apache.org/jira/browse/MCOMPILER-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134090#comment-15134090 ] Andreas Gudian commented on MCOMPILER-240: -- Please check my last comment in MC

[jira] [Updated] (MCOMPILER-240) Generated sources directory should not be added to compiler's source roots

[ https://issues.apache.org/jira/browse/MCOMPILER-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated MCOMPILER-240: - Fix Version/s: 3.5.1 > Generated sources directory should not be added to compiler's so

[jira] [Assigned] (MCOMPILER-240) Generated sources directory should not be added to compiler's source roots

[ https://issues.apache.org/jira/browse/MCOMPILER-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned MCOMPILER-240: Assignee: Andreas Gudian > Generated sources directory should not be added to co

[jira] [Resolved] (MCOMPILER-240) Generated sources directory should not be added to compiler's source roots

[ https://issues.apache.org/jira/browse/MCOMPILER-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian resolved MCOMPILER-240. -- Resolution: Duplicate > Generated sources directory should not be added to compiler's

[jira] [Assigned] (MCOMPILER-236) Compilation error due to MCOMPILER-157 in deploy phase

[ https://issues.apache.org/jira/browse/MCOMPILER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian reassigned MCOMPILER-236: Assignee: Andreas Gudian > Compilation error due to MCOMPILER-157 in deploy phas

[jira] [Commented] (MCOMPILER-240) Generated sources directory should not be added to compiler's source roots

[ https://issues.apache.org/jira/browse/MCOMPILER-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134553#comment-15134553 ] Andreas Gudian commented on MCOMPILER-240: -- Great, thanks for checking! I'll p

[jira] [Updated] (MCOMPILER-236) Compilation error due to MCOMPILER-157 in deploy phase

[ https://issues.apache.org/jira/browse/MCOMPILER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated MCOMPILER-236: - Fix Version/s: 3.5.1 > Compilation error due to MCOMPILER-157 in deploy phase > ---

[jira] [Resolved] (MCOMPILER-236) Compilation error due to MCOMPILER-157 in deploy phase

[ https://issues.apache.org/jira/browse/MCOMPILER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian resolved MCOMPILER-236. -- Resolution: Duplicate Underlying cause of the issue is the same as in MCOMPILER-235.

[jira] [Resolved] (MCOMPILER-227) Ability to reset the annotation processing to "not specified"

[ https://issues.apache.org/jira/browse/MCOMPILER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian resolved MCOMPILER-227. -- Resolution: Not A Problem Just use {{}}, as documented in https://maven.apache.org/p

[jira] [Resolved] (MCOMPILER-97) META-INF/services/javax.annotation.processing.Processor copied before compilation and causes error

[ https://issues.apache.org/jira/browse/MCOMPILER-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian resolved MCOMPILER-97. - Resolution: Not A Problem I'm closing this as "Not A Problem", as it's just how a) the d

[jira] [Commented] (MCOMPILER-226) Annotation Precompiler causes javac compiler not to compile

[ https://issues.apache.org/jira/browse/MCOMPILER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134591#comment-15134591 ] Andreas Gudian commented on MCOMPILER-226: -- I don't understand the problem. Is

[jira] [Resolved] (MCOMPILER-202) Plugin dependencies not added to compiler classpath with javax.tools.Compiler

[ https://issues.apache.org/jira/browse/MCOMPILER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian resolved MCOMPILER-202. -- Resolution: Duplicate > Plugin dependencies not added to compiler classpath with java

[jira] [Commented] (MCOMPILER-197) dependencies no more at classpath

[ https://issues.apache.org/jira/browse/MCOMPILER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134602#comment-15134602 ] Andreas Gudian commented on MCOMPILER-197: -- I would argue that the current beh

[jira] [Resolved] (MCOMPILER-197) dependencies no more at classpath

[ https://issues.apache.org/jira/browse/MCOMPILER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian resolved MCOMPILER-197. -- Resolution: Won't Fix > dependencies no more at classpath > -

[jira] [Updated] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more

[ https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated MCOMPILER-235: - Fix Version/s: (was: 2.5.1) 3.5.1 > duplicate classes due to MCO

[jira] [Commented] (MCOMPILER-235) duplicate classes due to MCOMPILER-157 when compiler is called twice or more

[ https://issues.apache.org/jira/browse/MCOMPILER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185162#comment-15185162 ] Andreas Gudian commented on MCOMPILER-235: -- Oops, indeed. Thanks! > duplicate

[jira] [Commented] (MCOMPILER-266) generatedSourcesDirectory added to compileSourceRoots

[ https://issues.apache.org/jira/browse/MCOMPILER-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229755#comment-15229755 ] Andreas Gudian commented on MCOMPILER-266: -- Did you try using the latest versi

[jira] [Commented] (MCOMPILER-265) IllegalAccessError trying to access package-private method through public subclass (for same package) from another package

[ https://issues.apache.org/jira/browse/MCOMPILER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229776#comment-15229776 ] Andreas Gudian commented on MCOMPILER-265: -- If I understand the comments on SO

[jira] (SUREFIRE-839) If no tests are found that would match a given JUnit category, mvn test should not fail in multi-module project

[ https://jira.codehaus.org/browse/SUREFIRE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315257#comment-315257 ] Andreas Gudian commented on SUREFIRE-839: - Kristian, this fix breaks SUREFIRE-751: using

[jira] (SUREFIRE-839) If no tests are found that would match a given JUnit category, mvn test should not fail in multi-module project

[ https://jira.codehaus.org/browse/SUREFIRE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315266#comment-315266 ] Andreas Gudian commented on SUREFIRE-839: - @Kristian, that is actually the part that you

[jira] (SUREFIRE-839) If no tests are found that would match a given JUnit category, mvn test should not fail in multi-module project

[ https://jira.codehaus.org/browse/SUREFIRE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315271#comment-315271 ] Andreas Gudian commented on SUREFIRE-839: - @Kristian: the pull-request extends your IT wi

[jira] (SUREFIRE-933) forkMode onceperthread broken after fix for JUnit category filter with empty result

Andreas Gudian created SUREFIRE-933: --- Summary: forkMode onceperthread broken after fix for JUnit category filter with empty result Key: SUREFIRE-933 URL: https://jira.codehaus.org/browse/SUREFIRE-933

[jira] (SUREFIRE-933) forkMode onceperthread broken after fix for JUnit category filter with empty result

[ https://jira.codehaus.org/browse/SUREFIRE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315283#comment-315283 ] Andreas Gudian commented on SUREFIRE-933: - Opened/Updated pull request https://github.com

[jira] (SUREFIRE-934) Remove getLocatedClasses() and size() from TestsToRun

Andreas Gudian created SUREFIRE-934: --- Summary: Remove getLocatedClasses() and size() from TestsToRun Key: SUREFIRE-934 URL: https://jira.codehaus.org/browse/SUREFIRE-934 Project: Maven Surefire

[jira] (SUREFIRE-934) Remove getLocatedClasses() and size() from TestsToRun

[ https://jira.codehaus.org/browse/SUREFIRE-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315299#comment-315299 ] Andreas Gudian commented on SUREFIRE-934: - Could you push the changes from SUREFIRE-933 t

[jira] (SUREFIRE-934) Remove getLocatedClasses() and size() from TestsToRun

[ https://jira.codehaus.org/browse/SUREFIRE-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315312#comment-315312 ] Andreas Gudian commented on SUREFIRE-934: - OK, I pulled from apache.org and created the p

[jira] (SUREFIRE-933) forkMode onceperthread broken after fix for JUnit category filter with empty result

[ https://jira.codehaus.org/browse/SUREFIRE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315767#comment-315767 ] Andreas Gudian commented on SUREFIRE-933: - Totally. Please try https://github.com/apache/

[jira] (SUREFIRE-933) forkMode onceperthread broken after fix for JUnit category filter with empty result

[ https://jira.codehaus.org/browse/SUREFIRE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315790#comment-315790 ] Andreas Gudian commented on SUREFIRE-933: - Thank you for applying it. :)

[jira] (SUREFIRE-933) forkMode onceperthread broken after fix for JUnit category filter with empty result

[ https://jira.codehaus.org/browse/SUREFIRE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-933: Attachment: SUREFIRE-933-part2.patch SUREFIRE-933-part1.patch For the record:

[jira] (SUREFIRE-934) Remove getLocatedClasses() and size() from TestsToRun

[ https://jira.codehaus.org/browse/SUREFIRE-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-934: Attachment: SUREFIRE-934.patch For the record: attached the patch contained in pull-request 14

<    1   2   3   4   5   6   >