[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[
https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362272#comment-362272
]
Jürgen Zeller commented on SUREFIRE-1137:
-
@Tibor: Yes, we have a bug in surefire.
@Michael: removing the
-Dfile.encoding=${project.build.sourceEncoding} is obviously
fixing the encoding issues but not the problem:
I need that encoding for running the tests, because the test file data is in
Cp1252, not in UTF-8
But when i change file.encoding, it also changes the encoding for stdout/stdin
in the forked JVM, and so the problems starts.
> Problem with Umlauts in stdout
> --
>
> Key: SUREFIRE-1137
> URL: https://jira.codehaus.org/browse/SUREFIRE-1137
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.18
> Environment: Linux
>Reporter: Jürgen Zeller
>Assignee: Andreas Gudian
> Attachments: surefire-test.zip
>
>
> When using Cp1252 as file encoding, the generated Surefire stdout report
> contains invalid characters when run on Linux. When running the same test on
> Windows, everything is fine.
> A simular Problem was reported in SUREFIRE-998
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[
https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362273#comment-362273
]
Andreas Gudian commented on SUREFIRE-1137:
--
I should have answered yesterday night already: I was able to reproduce the
problem on my local Windows machine by encoding the test java file as UTF-8 and
using UTF-8 in the pom. Stacktraces and error messages are correctly encoded in
the output XML, but the sysout doesn't survive the journey, just as Jürgen
describes.
My main maven process has {{Charset.defaultCharset()}} being my windows-1252,
whereas the forked VM has {{Charset.defaultCharset()}} UTF-8. The current
implementation relies on the default charset being the same on both the main
process and the forked process, hence the encoding garbage.
* if I don't pass file.encoding to the forked VM, then the forked VM also uses
windows-1252
* If I pass -Dfile.encoding=UTF-8 in the MAVEN_OPTS to the main process, then
System.getProperty("file.encoding") is "UTF-8", but
{{Charset.defaultCharset()}} _remains being windows-1252_ - I was not able to
manipulate the defaultCharset of the main process with a system property.
But the documentation is quite clear on that: you're not supposed to change the
defaultCharset by using file.encoding, but instead change the system's locale /
language settings. Meh.
I'm not really sure yet what to make of this. I could pass the fork's
defaultCharset back to the main process to properly recode the stream into
UTF-8. I could pass the main's defaultCharset to the fork to use that one for
encoding the String in PrintSteam's print(String) method (although that may
cause strange side-effects with other ways how to use that print stream). Or I
could convert any print stream activity in the fork to UTF-16 (although not
every charset can transform all its characters to UTF-16 and then again back
from UTF-16, which is why I tried to rely on the defaultEncoding in the first
place)...
So I might go with the first option, but I still need to think about it (to see
if it really is the right thing to do).
If you guys have an idea here, let me know.
> Problem with Umlauts in stdout
> --
>
> Key: SUREFIRE-1137
> URL: https://jira.codehaus.org/browse/SUREFIRE-1137
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.18
> Environment: Linux
>Reporter: Jürgen Zeller
>Assignee: Andreas Gudian
> Attachments: surefire-test.zip
>
>
> When using Cp1252 as file encoding, the generated Surefire stdout report
> contains invalid characters when run on Linux. When running the same test on
> Windows, everything is fine.
> A simular Problem was reported in SUREFIRE-998
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[
https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362274#comment-362274
]
Michael Osipov commented on SUREFIRE-1137:
--
[~zet],
there is no bug (yet). First, {{javac}} reads your Java source with ISO-8859-15
and the std out is correct. There is no connection to {{file.encoding}}.
Second, you test sample does not contain any resources but Java files only. I
see no problem. Third, if your test resources are not in the encoding as
{{file.encoding}} and surefire did ignore {{project.build.sourceEncoding}} then
this is a bug but you haven't provided a valid sample project Even though, I
would be confused because surefire does not read any test resources but your
testcases do.
> Problem with Umlauts in stdout
> --
>
> Key: SUREFIRE-1137
> URL: https://jira.codehaus.org/browse/SUREFIRE-1137
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.18
> Environment: Linux
>Reporter: Jürgen Zeller
>Assignee: Andreas Gudian
> Attachments: surefire-test.zip
>
>
> When using Cp1252 as file encoding, the generated Surefire stdout report
> contains invalid characters when run on Linux. When running the same test on
> Windows, everything is fine.
> A simular Problem was reported in SUREFIRE-998
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[ https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362275#comment-362275 ] Michael Osipov commented on SUREFIRE-1137: -- After reading Andreas' post: if anyone expects Maven/Surefire/Java to spit out UTF-8 encoded chars on Windows' command line. Forget about it, don't even try. This has been crap ever since. There are numerous questions on SO about that. This is something only Microsoft can fix. > Problem with Umlauts in stdout > -- > > Key: SUREFIRE-1137 > URL: https://jira.codehaus.org/browse/SUREFIRE-1137 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.18 > Environment: Linux >Reporter: Jürgen Zeller >Assignee: Andreas Gudian > Attachments: surefire-test.zip > > > When using Cp1252 as file encoding, the generated Surefire stdout report > contains invalid characters when run on Linux. When running the same test on > Windows, everything is fine. > A simular Problem was reported in SUREFIRE-998 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[ https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362276#comment-362276 ] Andreas Gudian commented on SUREFIRE-1137: -- Michael, it's not the output on the cmd-line, but what we write to the stdout-section in the report xml. What we have here is a bug on our side and we're going to fix it. > Problem with Umlauts in stdout > -- > > Key: SUREFIRE-1137 > URL: https://jira.codehaus.org/browse/SUREFIRE-1137 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.18 > Environment: Linux >Reporter: Jürgen Zeller >Assignee: Andreas Gudian > Attachments: surefire-test.zip > > > When using Cp1252 as file encoding, the generated Surefire stdout report > contains invalid characters when run on Linux. When running the same test on > Windows, everything is fine. > A simular Problem was reported in SUREFIRE-998 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[
https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362277#comment-362277
]
Michael Osipov commented on SUREFIRE-1137:
--
[~agudian], that wasn't clear up front. Thanks for the clarification.
How's surefire capturing std out? By chaning the output stream to a tee stream
of a file stream? That if course needs to be read with {{file.encoding}}.
> Problem with Umlauts in stdout
> --
>
> Key: SUREFIRE-1137
> URL: https://jira.codehaus.org/browse/SUREFIRE-1137
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.18
> Environment: Linux
>Reporter: Jürgen Zeller
>Assignee: Andreas Gudian
> Attachments: surefire-test.zip
>
>
> When using Cp1252 as file encoding, the generated Surefire stdout report
> contains invalid characters when run on Linux. When running the same test on
> Windows, everything is fine.
> A simular Problem was reported in SUREFIRE-998
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-780) Duplicate connection url's properties
[
https://jira.codehaus.org/browse/SCM-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed SCM-780.
---
Resolution: Fixed
Assignee: Karl-Heinz Marbaise (was: Dan Tran)
Fixed in
[ab163ea9a3f902adc482f42ad20aafa491412827|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commitdiff;h=ab163ea9a3f902adc482f42ad20aafa491412827].
> Duplicate connection url's properties
> -
>
> Key: SCM-780
> URL: https://jira.codehaus.org/browse/SCM-780
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-plugin
>Affects Versions: 1.9.1
>Reporter: Dan Tran
>Assignee: Karl-Heinz Marbaise
> Fix For: 1.9.3
>
>
> at AbstractScmMojo
> /**
> * The SCM connection URL.
> */
> @Parameter( property = "connectionUrl", defaultValue =
> "${project.scm.connection}" )
> private String connectionUrl;
> /**
> * The SCM connection URL for developers.
> */
> @Parameter( property = "connectionUrl", defaultValue =
> "${project.scm.developerConnection}" )
> private String developerConnectionUrl;
> the property "connectionUrl" is used by both connectionUrl and
> developerConnectionUrl
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[ https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362280#comment-362280 ] Tibor Digana commented on SUREFIRE-1137: ok, very good. We are all on the same line. @Andreas, do you want to take this job? For one month I am working on patterns related to -Dtest=... and testing it like a hell. Additionally, I have to handle SUREFIRE-1138. > Problem with Umlauts in stdout > -- > > Key: SUREFIRE-1137 > URL: https://jira.codehaus.org/browse/SUREFIRE-1137 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.18 > Environment: Linux >Reporter: Jürgen Zeller >Assignee: Andreas Gudian > Attachments: surefire-test.zip > > > When using Cp1252 as file encoding, the generated Surefire stdout report > contains invalid characters when run on Linux. When running the same test on > Windows, everything is fine. > A simular Problem was reported in SUREFIRE-998 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MEAR-213) WARNING Output is not correct in case of classifiers
[
https://jira.codehaus.org/browse/MEAR-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MEAR-213:
-
Description:
In relationship with classifier this does not work correctly.
{noformat}
[INFO] --- maven-ear-plugin:2.10:ear (default-ear) @ middletier-ear ---
[WARNING] The artifactId component-base:6.33.10-SNAPSHOT exists more than once
in the modules list.
[WARNING] --> com.company:component-base:jar:6.33.10-SNAPSHOT (jar)
[WARNING] --> com.company:component-base:jar:qclasses:6.33.10-SNAPSHOT (jar)
[WARNING] The artifactId component-func:6.33.10-SNAPSHOT exists more than once
in the modules list.
[WARNING] --> com.company:component-func:jar:6.33.10-SNAPSHOT (jar)
[WARNING] --> com.company:component-func:jar:qclasses:6.33.10-SNAPSHOT (jar)
[WARNING] HINT: This can be simply solved by using the
full
{noformat}
was:
In relationship with classifier this does not work correctly.
{code}
[INFO] --- maven-ear-plugin:2.10:ear (default-ear) @ middletier-ear ---
[WARNING] The artifactId component-base:6.33.10-SNAPSHOT exists more than once
in the modules list.
[WARNING] --> com.company:component-base:jar:6.33.10-SNAPSHOT (jar)
[WARNING] --> com.company:component-base:jar:qclasses:6.33.10-SNAPSHOT (jar)
[WARNING] The artifactId component-func:6.33.10-SNAPSHOT exists more than once
in the modules list.
[WARNING] --> com.company:component-func:jar:6.33.10-SNAPSHOT (jar)
[WARNING] --> com.company:component-func:jar:qclasses:6.33.10-SNAPSHOT (jar)
[WARNING] HINT: This can be simply solved by using the
full
[code}
> WARNING Output is not correct in case of classifiers
>
>
> Key: MEAR-213
> URL: https://jira.codehaus.org/browse/MEAR-213
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Karl-Heinz Marbaise
> Fix For: 2.10.1
>
>
> In relationship with classifier this does not work correctly.
> {noformat}
> [INFO] --- maven-ear-plugin:2.10:ear (default-ear) @ middletier-ear ---
> [WARNING] The artifactId component-base:6.33.10-SNAPSHOT exists more than
> once in the modules list.
> [WARNING] --> com.company:component-base:jar:6.33.10-SNAPSHOT (jar)
> [WARNING] --> com.company:component-base:jar:qclasses:6.33.10-SNAPSHOT (jar)
> [WARNING] The artifactId component-func:6.33.10-SNAPSHOT exists more than
> once in the modules list.
> [WARNING] --> com.company:component-func:jar:6.33.10-SNAPSHOT (jar)
> [WARNING] --> com.company:component-func:jar:qclasses:6.33.10-SNAPSHOT (jar)
> [WARNING] HINT: This can be simply solved by using the
> full
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[ https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362282#comment-362282 ] Andreas Gudian commented on SUREFIRE-1137: -- Sure, I'm on it. I'm busy tonight, but it'll come... ;-) > Problem with Umlauts in stdout > -- > > Key: SUREFIRE-1137 > URL: https://jira.codehaus.org/browse/SUREFIRE-1137 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.18 > Environment: Linux >Reporter: Jürgen Zeller >Assignee: Andreas Gudian > Attachments: surefire-test.zip > > > When using Cp1252 as file encoding, the generated Surefire stdout report > contains invalid characters when run on Linux. When running the same test on > Windows, everything is fine. > A simular Problem was reported in SUREFIRE-998 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1137) Problem with Umlauts in stdout
[ https://jira.codehaus.org/browse/SUREFIRE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362283#comment-362283 ] Tibor Digana commented on SUREFIRE-1137: @Andreas You have asked us for our opinion: I vote for the first option, but without testing it I would be 100% sure either. > Problem with Umlauts in stdout > -- > > Key: SUREFIRE-1137 > URL: https://jira.codehaus.org/browse/SUREFIRE-1137 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.18 > Environment: Linux >Reporter: Jürgen Zeller >Assignee: Andreas Gudian > Attachments: surefire-test.zip > > > When using Cp1252 as file encoding, the generated Surefire stdout report > contains invalid characters when run on Linux. When running the same test on > Windows, everything is fine. > A simular Problem was reported in SUREFIRE-998 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1138) Enabling reuseForks runs all tests in series on just one fork
[
https://jira.codehaus.org/browse/SUREFIRE-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1138:
--
Assignee: Tibor Digana (was: Andreas Gudian)
> Enabling reuseForks runs all tests in series on just one fork
> -
>
> Key: SUREFIRE-1138
> URL: https://jira.codehaus.org/browse/SUREFIRE-1138
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.18, 2.18.1
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 19:44:56+1100)
> Java version: 1.7.0_17, vendor: Oracle Corporation
> Ubuntu 12.04 LTS
>Reporter: Matthew Provis
>Assignee: Tibor Digana
> Attachments: test.zip
>
>
> When using Surefire >= 2.18, I've encountered a problem when setting
> {{forkCount > 1}} and {{reuseForks = true}}.
> Expected behaviour:
> Tests should run simultaneously, each on a separate fork.
> Actual behaviour:
> All tests run on just one fork, sequentially.
> Setting {{reuseForks = false}} gives the expected behaviour.
> Reverting to Surefire 2.17 also gives the expected behaviour.
> I've attached a project that demonstrates the issue. Here I've created two
> tests, each of which prints the fork number and sleeps for 5 seconds. The
> total run time is 10 seconds with Surefire 2.18 and 2.18.1, but 5 seconds
> with version 2.17.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1138) Enabling reuseForks runs all tests in series on just one fork
[
https://jira.codehaus.org/browse/SUREFIRE-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1138:
---
Fix Version/s: 2.19
> Enabling reuseForks runs all tests in series on just one fork
> -
>
> Key: SUREFIRE-1138
> URL: https://jira.codehaus.org/browse/SUREFIRE-1138
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.18, 2.18.1
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 19:44:56+1100)
> Java version: 1.7.0_17, vendor: Oracle Corporation
> Ubuntu 12.04 LTS
>Reporter: Matthew Provis
>Assignee: Tibor Digana
> Fix For: 2.19
>
> Attachments: test.zip
>
>
> When using Surefire >= 2.18, I've encountered a problem when setting
> {{forkCount > 1}} and {{reuseForks = true}}.
> Expected behaviour:
> Tests should run simultaneously, each on a separate fork.
> Actual behaviour:
> All tests run on just one fork, sequentially.
> Setting {{reuseForks = false}} gives the expected behaviour.
> Reverting to Surefire 2.17 also gives the expected behaviour.
> I've attached a project that demonstrates the issue. Here I've created two
> tests, each of which prints the fork number and sleeps for 5 seconds. The
> total run time is 10 seconds with Surefire 2.18 and 2.18.1, but 5 seconds
> with version 2.17.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-273) remove Turbine configuration since it is not used any more
[ https://jira.codehaus.org/browse/MCHECKSTYLE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHECKSTYLE-273: Fix Version/s: 2.16 > remove Turbine configuration since it is not used any more > -- > > Key: MCHECKSTYLE-273 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-273 > Project: Maven Checkstyle Plugin > Issue Type: Task >Affects Versions: 2.13 >Reporter: Herve Boutemy >Priority: Trivial > Fix For: 2.16 > > > Chesktyle doesn't seem to be used any more > http://turbine.apache.org/turbine/turbine-4.0-M1/plugins.html > Maintaining Turbine specific configuration as part of maven-checkstyle-plugin > does not seem to have any meaning now -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-285) Remove config/maven_checks.xml by removing the dependency on maven-shared-resources:2
[ https://jira.codehaus.org/browse/MCHECKSTYLE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHECKSTYLE-285: Fix Version/s: 2.16 > Remove config/maven_checks.xml by removing the dependency on > maven-shared-resources:2 > - > > Key: MCHECKSTYLE-285 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-285 > Project: Maven Checkstyle Plugin > Issue Type: Task >Reporter: Dennis Lundberg > Fix For: 2.16 > > > The plugin should not include configurations for specific projects, by > default. Let the users pick their own configuration. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-285) Remove config/maven_checks.xml by removing the dependency on maven-shared-resources:2
Dennis Lundberg created MCHECKSTYLE-285: --- Summary: Remove config/maven_checks.xml by removing the dependency on maven-shared-resources:2 Key: MCHECKSTYLE-285 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-285 Project: Maven Checkstyle Plugin Issue Type: Task Reporter: Dennis Lundberg The plugin should not include configurations for specific projects, by default. Let the users pick their own configuration. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-898) release:branch fails in a multi-project git project with each project in its own repository.
Ralph Goers created MRELEASE-898: Summary: release:branch fails in a multi-project git project with each project in its own repository. Key: MRELEASE-898 URL: https://jira.codehaus.org/browse/MRELEASE-898 Project: Maven Release Plugin Issue Type: Bug Affects Versions: 2.5.1 Reporter: Ralph Goers Attachments: maven.log, releasetest.zip I have a sample project that illustrates how our project is organized - every project is in its own git repo. When trying to perform a release:branch on this project it fails to add the modified poms because it tries to perform a git add on all of them at once. This fails with a message saying a pom is outside the repository. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-120) Javac compiler plugin doesn't support -Werror
[
https://jira.codehaus.org/browse/MCOMPILER-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCOMPILER-120.
--
Resolution: Fixed
Here's the story.
If you are compiling down with -source / -target, and not supplying
-Xbootclasspath, you get a warning at the outset. That stops the process with
-Werror _unless_ you then also use -Xlint:-options to turn this off. I can't
explain the apparent influence of deprecation/warning control.
> Javac compiler plugin doesn't support -Werror
> -
>
> Key: MCOMPILER-120
> URL: https://jira.codehaus.org/browse/MCOMPILER-120
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Christopher Webster
>Assignee: Kristian Rosenvold
> Fix For: 2.4
>
> Attachments: JavacCompiler.java, JavacCompiler.patch,
> trial-maven.zip, werror.zip
>
>
> If I write a pom file like the following:
> {code:xml}...
>
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.1
>
> javac
> 1.6
> 1.6
>
>
>
>
>
> true
>
> {code}
> and if there are only warnings, then the build will not fail as intended by
> the compiler Argument. The reason is that in compileInProcess the exit code
> from javac is only considered if there are no messages. In the case of
> treating warnings as errors, there will be messages but no errors so the
> intention of the build failure is lost.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1126) Discrepancy between test exclusion docs and plugin behavior
[ https://jira.codehaus.org/browse/SUREFIRE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362332#comment-362332 ] Dima Spivak commented on SUREFIRE-1126: --- Any update on this, Tibor? We'd love this functionality for our test-running in Apache HBase. > Discrepancy between test exclusion docs and plugin behavior > --- > > Key: SUREFIRE-1126 > URL: https://jira.codehaus.org/browse/SUREFIRE-1126 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.18 >Reporter: Dima Spivak >Assignee: Tibor Digana > > According to [Surefire > documentation|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#test], > tests can be excluded on the command line by prefixing with an exclamation > mark. Is this expected behavior that's currently broken, or did someone jump > the gun with the docs? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
