[jira] Commented: (SCM-630) Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers
[ https://jira.codehaus.org/browse/SCM-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277200#comment-277200 ] Olivier Lamy commented on SCM-630: -- yup I'm working on integrate it. Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers Key: SCM-630 URL: https://jira.codehaus.org/browse/SCM-630 Project: Maven SCM Issue Type: New Feature Components: maven-scm-api Affects Versions: 1.5 Environment: Unix and Windows Reporter: Cletus D'Souza Assignee: Olivier Lamy Priority: Minor Attachments: javadocs.zip, javadocs.zip, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, source.zip, source.zip I've developed an SCM Provider for MKS Integrity. I would like to contribute this code to the Apache community for inclusion on the Maven SCM Provider list -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-49) If maven.compiler.failOnError is used errors are not logged as errors
[ https://jira.codehaus.org/browse/MCOMPILER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCOMPILER-49. --- Resolution: Duplicate Already fixed by MCOMPILER-118 If maven.compiler.failOnError is used errors are not logged as errors - Key: MCOMPILER-49 URL: https://jira.codehaus.org/browse/MCOMPILER-49 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Stepan Roh Attachments: maven-compiler-plugin-errors-as-errors.patch If maven.compiler.failOnError is used, all errors are logged as warnings, but I think they should still be logged as errors even though they do not cause build failure. Patch attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-54) Cannot include non .java file via includes configuration
[
https://jira.codehaus.org/browse/MCOMPILER-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MCOMPILER-54.
---
Resolution: Not A Bug
Non-java sources should be placed under {{src/main/resources}} or a custom
location specified in de {{pom.xml}} in the
{{projectbuildresources}}-section as described
[here|http://maven.apache.org/pom.html#Resources].
These (re)sources don't need to be compiled, but belong on the classpath. The
[maven-resources-plugin|http://maven.apache.org/plugins/maven-resources-plugin/]
is responsible for this action.
Cannot include non .java file via includes configuration
Key: MCOMPILER-54
URL: https://jira.codehaus.org/browse/MCOMPILER-54
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.0, 2.0.1, 2.0.2
Environment: WinXP, Win2003K, JDK 5.11 (Java(TM) 2 Runtime
Environment, Standard Edition (build 1.5.0_11-b03))
Reporter: Dave Ousey
Priority: Minor
Attachments: quicktest.zip
Could not get mvn clean compile to move a .properties file in source
directory structure even though appropriate includes configuration is
specified in the POM. Attached is simple archetype project to demonstrate.
app.properties is not moved to target directory.
Our use of MyEclipse places .properties resource bundle files in source
directory. I will pursue moving properties files to resources directory
but expected this to work.
I dug into the source code and problem manifests in StateSourceScanner -
getIncludedSources method. The scanForSources private method correctly
applies the included files but then the subsequent for loop does not catch
the properties file because the compiler plugin only every adds a
SourceMapping with a .java suffix. Could not find any clear documentation
to configure this differently to get this working.
Got similar results with earlier versions of the plugin and with target = 1.5
and not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-89) Duplicate compiler errors
[
https://jira.codehaus.org/browse/MCOMPILER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MCOMPILER-89.
---
Resolution: Cannot Reproduce
The affected version is missing so I've tried several versions of the plugin. I
wasn't able to reproduce it.
I don't think the bug will occur again since with MCOMPILER-118 the logging of
these messages has changed.
Duplicate compiler errors
-
Key: MCOMPILER-89
URL: https://jira.codehaus.org/browse/MCOMPILER-89
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Reporter: Trevor Harmon
Priority: Minor
I often get duplicate Java compiler errors when building with Maven. Here's
how to reproduce:
mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes
-DgroupId=com.mycompany.app -DartifactId=my-app
Then change App.java to this:
package com.mycompany.app;
interface Foo {
void bar();
}
public class App implements Foo {}
Running mvn compile at this point produces:
...
[INFO] Compilation failure
/Users/trevor/Desktop/test/maven/my-app/src/main/java/com/mycompany/app/App.java:[7,7]
com.mycompany.app.App is not abstract and does not override abstract method
bar() in com.mycompany.app.Foo
/Users/trevor/Desktop/test/maven/my-app/src/main/java/com/mycompany/app/App.java:[7,7]
com.mycompany.app.App is not abstract and does not override abstract method
bar() in com.mycompany.app.Foo
...
Compiling the same code with javac gives only one.
Seems like a bug in Maven itself. It is logging both the exception and the
nested compile exception (shown by running with -e). It should just show the
actual failure.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-630) Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers
[ https://jira.codehaus.org/browse/SCM-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277217#comment-277217 ] Olivier Lamy commented on SCM-630: -- all committed. I wonder if you could provide some unit tests ??? Thanks ! Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers Key: SCM-630 URL: https://jira.codehaus.org/browse/SCM-630 Project: Maven SCM Issue Type: New Feature Components: maven-scm-api Affects Versions: 1.5 Environment: Unix and Windows Reporter: Cletus D'Souza Assignee: Olivier Lamy Priority: Minor Attachments: javadocs.zip, javadocs.zip, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, source.zip, source.zip I've developed an SCM Provider for MKS Integrity. I would like to contribute this code to the Apache community for inclusion on the Maven SCM Provider list -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-630) Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers
[ https://jira.codehaus.org/browse/SCM-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-630: - Fix Version/s: 1.6 Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers Key: SCM-630 URL: https://jira.codehaus.org/browse/SCM-630 Project: Maven SCM Issue Type: New Feature Components: maven-scm-api Affects Versions: 1.5 Environment: Unix and Windows Reporter: Cletus D'Souza Assignee: Olivier Lamy Priority: Minor Fix For: 1.6 Attachments: javadocs.zip, javadocs.zip, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, source.zip, source.zip I've developed an SCM Provider for MKS Integrity. I would like to contribute this code to the Apache community for inclusion on the Maven SCM Provider list -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-708) upgrade to last scm 1.6 to integrate new scm provider mks integrity
[ https://jira.codehaus.org/browse/MRELEASE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-708. - Resolution: Fixed Fix Version/s: 2.3 Assignee: Olivier Lamy fixed rev 1162351 upgrade to last scm 1.6 to integrate new scm provider mks integrity --- Key: MRELEASE-708 URL: https://jira.codehaus.org/browse/MRELEASE-708 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-708) upgrade to last scm 1.6 to integrate new scm provider mks integrity
upgrade to last scm 1.6 to integrate new scm provider mks integrity --- Key: MRELEASE-708 URL: https://jira.codehaus.org/browse/MRELEASE-708 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Reporter: Olivier Lamy -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-630) Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers
[ https://jira.codehaus.org/browse/SCM-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277226#comment-277226 ] Cletus D'Souza commented on SCM-630: Sure, I can work on creating the unit tests. Any idea when maven scm 1.6 is scheduled to be released? Request to include MKS Integrity SCM Provider along with the rest of the Maven SCM Providers Key: SCM-630 URL: https://jira.codehaus.org/browse/SCM-630 Project: Maven SCM Issue Type: New Feature Components: maven-scm-api Affects Versions: 1.5 Environment: Unix and Windows Reporter: Cletus D'Souza Assignee: Olivier Lamy Priority: Minor Fix For: 1.6 Attachments: javadocs.zip, javadocs.zip, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, maven-scm-provider-integrity-1.0-SNAPSHOT.jar, source.zip, source.zip I've developed an SCM Provider for MKS Integrity. I would like to contribute this code to the Apache community for inclusion on the Maven SCM Provider list -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5168) warning on build.directory does not identify source of problem
warning on build.directory does not identify source of problem
--
Key: MNG-5168
URL: https://jira.codehaus.org/browse/MNG-5168
Project: Maven 2 3
Issue Type: Bug
Components: General
Affects Versions: 3.0.3
Reporter: Benson Margulies
Note the lack of a file name or line number below. You can repro this with:
https://svn.apache.org/repos/asf/maven/sandbox/branches/doxia-ide-eclipse-with-tycho/org.apache.maven.doxia.eclipse.dependencies
at svn rev 1162378.
I can't find the thing it's complaining about in the POM so far.
[WARNING] Some problems were encountered while building the effective model for
org.apache.maven.doxia.ide:dependencies:bundle:1.0-SNAPSHOT
[WARNING] The expression ${build.directory} is deprecated. Please use
${project.build.directory} instead.
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-94) compiler sets artifact file to target/classes, even if nothing is compiled
[
https://jira.codehaus.org/browse/MCOMPILER-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MCOMPILER-94.
---
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Robert Scholte
Fixed in [rev. 1162398|http://svn.apache.org/viewvc?rev=1162398view=rev]
compiler sets artifact file to target/classes, even if nothing is compiled
--
Key: MCOMPILER-94
URL: https://jira.codehaus.org/browse/MCOMPILER-94
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Brett Porter
Assignee: Robert Scholte
Fix For: 2.4
consider the following parent project:
{code:xml}
project
...
packagingpom/packaging
build
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
/plugin
...
{code}
This is technically incorrect, you're asking to compile a project with no
sources, but it is needed for inheritence. The compiler should gracefully
skip all functions, however it sets the artifact from the POM to the
target/classes directory, which is incorrect if nothing was compiled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-99) Spaces in for external executable are not accepted
[ https://jira.codehaus.org/browse/MCOMPILER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277231#comment-277231 ] Robert Scholte commented on MCOMPILER-99: - Could someone verify if this is still a problem? With Windows7 I'm not able to reproduce this issue. The problem should be caused by the [plexus-compiler|http://plexus.codehaus.org/plexus-components/plexus-compiler/]. Meanwhile we've already updated its version from 1.6 (used by maven-compiler-plugin-2.1) to 1.8.2. Strange enough [Plexus' Jira|http://jira.codehaus.org/browse/PLXCOMP/component/12541] doesn't refer to such an issue. Spaces in for external executable are not accepted -- Key: MCOMPILER-99 URL: https://jira.codehaus.org/browse/MCOMPILER-99 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Windows XP Reporter: Jean-Marc Borer When the path to the external executable in executable contains space(s), the build will fail: the command is misunderstood because it stops at the first space encountered. Example: executableC:\Program Files\java\jdk1.6.0_11\bin\javac.exe/executable The plugin will try to execute C:\Program instead. On windows the only workaround I know of is: executableC:\PROGRA~1\java\jdk1.6.0_11\bin\javac.exe/executable -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-129) unable to pass in javac -J option
[
https://jira.codehaus.org/browse/MCOMPILER-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277234#comment-277234
]
Robert Scholte commented on MCOMPILER-129:
--
One way to solve this is by using {{compilerArguments}} like this:
{code:xml}
compiletArguments
J-Duser.languageen_us/J-Duser.language
/compiletArguments
{code}
This works because the plugin will prefix the key with a '{{-}}' if it's not
there.
There real problem is caused by this piece of code:
{code}
if ( !StringUtils.isEmpty( effectiveCompilerArgument ) )
{
cplrArgsCopy.put( effectiveCompilerArgument, null );
}
{code}
Here the whole line is set as the key without a specific value.
To solve this the line should be split into key-value pairs.
I´ve assigned this already issue to myself.
unable to pass in javac -J option
-
Key: MCOMPILER-129
URL: https://jira.codehaus.org/browse/MCOMPILER-129
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Environment: jdk 1.6
maven 3.0-beta-1
Reporter: Juven Xu
Assignee: Robert Scholte
because of MCOMPILER-109, l10n-ed javac warning messages will be regarded as
error, so I want to pass user language configuration to javac, like this:
javac ... -J-Duser.language=en_us
this works well on pure javac command line, but when I configure this for
maven-compiler-plugin:
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.3.1/version
configuration
forktrue/fork
source1.5/source
target1.5/target
compilerArgument-J-Duser.language=en_us/compilerArgument
/configuration
/plugin
I got#65306;
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile' with basic
configurator --
[DEBUG] (f) basedir = D:\workspace\test
[DEBUG] (f) buildDirectory = D:\workspace\test\target
[DEBUG] (f) classpathElements = [D:\workspace\test\target\classes]
[DEBUG] (f) compileSourceRoots = [D:\workspace\test\src\main\java]
[DEBUG] (f) compilerArgument = -J-Duser.language=en_us
[DEBUG] (f) compilerId = javac
[DEBUG] (f) debug = true
[DEBUG] (f) failOnError = true
[DEBUG] (f) fork = true
[DEBUG] (f) generatedSourcesDirectory =
D:\workspace\test\target\generated-sources\annotations
[DEBUG] (f) optimize = false
[DEBUG] (f) outputDirectory = D:\workspace\test\target\classes
[DEBUG] (f) outputFileName = test-0.0.1-SNAPSHOT
[DEBUG] (f) projectArtifact = com.juvenxu:test:jar:0.0.1-SNAPSHOT
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@11d2572
[DEBUG] (f) showDeprecation = false
[DEBUG] (f) showWarnings = false
[DEBUG] (f) source = 1.5
[DEBUG] (f) staleMillis = 0
[DEBUG] (f) target = 1.5
[DEBUG] (f) verbose = false
[DEBUG] -- end configuration --
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories: [D:\workspace\test\src\main\java]
[DEBUG] Classpath: [D:\workspace\test\target\classes]
[DEBUG] Output directory: D:\workspace\test\target\classes
[DEBUG] Classpath:
[DEBUG] D:\workspace\test\target\classes
[DEBUG] Source roots:
[DEBUG] D:\workspace\test\src\main\java
[DEBUG] Command line options:
[DEBUG] -d D:\workspace\test\target\classes -classpath
D:\workspace\test\target\classes; -sourcepath
D:\workspace\test\src\main\java;
D:\workspace\test\src\main\java\com\juvenxu\test\Test.java -g -nowarn -target
1.5 -source 1.5 -J-Duser.language=en_us
[WARNING] File encoding has not been set, using platform encoding GBK, i.e.
build is platform dependent!
[INFO] Compiling 1 source file to D:\workspace\test\target\classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] Failure executing javac, but could not parse the error:
javac: #26080;#25928;#30340;#26631;#24535;#65306;
-J-Duser.language=en_us
#29992;#27861;: javac options source files
-help #29992;#20110;#21015;#20986;#21487;#33021;#30340;#36873;#39033;
[INFO] 1error
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.451s
[INFO] Finished at: Wed May 26 17:29:06 CST 2010
[INFO] Final Memory: 2M/5M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project test: Compilation failure
Failure executing javac, but could not parse the error:
javac: #26080;#25928;#30340;#26631;#24535;#65306;
-J-Duser.language=en_us
#29992;#27861;: javac options source files
[jira] Issue Comment Edited: (MCOMPILER-129) unable to pass in javac -J option
[
https://jira.codehaus.org/browse/MCOMPILER-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277234#comment-277234
]
Robert Scholte edited comment on MCOMPILER-129 at 8/27/11 5:19 PM:
---
One way to solve this is by using {{compilerArguments}} like this:
{code:xml}
compilerArguments
J-Duser.languageen_us/J-Duser.language
/compilerArguments
{code}
This works because the plugin will prefix the key with a '{{-}}' if it's not
there.
There real problem is caused by this piece of code:
{code}
if ( !StringUtils.isEmpty( effectiveCompilerArgument ) )
{
cplrArgsCopy.put( effectiveCompilerArgument, null );
}
{code}
Here the whole line is set as the key without a specific value.
To solve this the line should be split into key-value pairs.
I´ve assigned this already issue to myself.
was (Author: rfscholte):
One way to solve this is by using {{compilerArguments}} like this:
{code:xml}
compiletArguments
J-Duser.languageen_us/J-Duser.language
/compiletArguments
{code}
This works because the plugin will prefix the key with a '{{-}}' if it's not
there.
There real problem is caused by this piece of code:
{code}
if ( !StringUtils.isEmpty( effectiveCompilerArgument ) )
{
cplrArgsCopy.put( effectiveCompilerArgument, null );
}
{code}
Here the whole line is set as the key without a specific value.
To solve this the line should be split into key-value pairs.
I´ve assigned this already issue to myself.
unable to pass in javac -J option
-
Key: MCOMPILER-129
URL: https://jira.codehaus.org/browse/MCOMPILER-129
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Environment: jdk 1.6
maven 3.0-beta-1
Reporter: Juven Xu
Assignee: Robert Scholte
because of MCOMPILER-109, l10n-ed javac warning messages will be regarded as
error, so I want to pass user language configuration to javac, like this:
javac ... -J-Duser.language=en_us
this works well on pure javac command line, but when I configure this for
maven-compiler-plugin:
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.3.1/version
configuration
forktrue/fork
source1.5/source
target1.5/target
compilerArgument-J-Duser.language=en_us/compilerArgument
/configuration
/plugin
I got#65306;
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile' with basic
configurator --
[DEBUG] (f) basedir = D:\workspace\test
[DEBUG] (f) buildDirectory = D:\workspace\test\target
[DEBUG] (f) classpathElements = [D:\workspace\test\target\classes]
[DEBUG] (f) compileSourceRoots = [D:\workspace\test\src\main\java]
[DEBUG] (f) compilerArgument = -J-Duser.language=en_us
[DEBUG] (f) compilerId = javac
[DEBUG] (f) debug = true
[DEBUG] (f) failOnError = true
[DEBUG] (f) fork = true
[DEBUG] (f) generatedSourcesDirectory =
D:\workspace\test\target\generated-sources\annotations
[DEBUG] (f) optimize = false
[DEBUG] (f) outputDirectory = D:\workspace\test\target\classes
[DEBUG] (f) outputFileName = test-0.0.1-SNAPSHOT
[DEBUG] (f) projectArtifact = com.juvenxu:test:jar:0.0.1-SNAPSHOT
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@11d2572
[DEBUG] (f) showDeprecation = false
[DEBUG] (f) showWarnings = false
[DEBUG] (f) source = 1.5
[DEBUG] (f) staleMillis = 0
[DEBUG] (f) target = 1.5
[DEBUG] (f) verbose = false
[DEBUG] -- end configuration --
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories: [D:\workspace\test\src\main\java]
[DEBUG] Classpath: [D:\workspace\test\target\classes]
[DEBUG] Output directory: D:\workspace\test\target\classes
[DEBUG] Classpath:
[DEBUG] D:\workspace\test\target\classes
[DEBUG] Source roots:
[DEBUG] D:\workspace\test\src\main\java
[DEBUG] Command line options:
[DEBUG] -d D:\workspace\test\target\classes -classpath
D:\workspace\test\target\classes; -sourcepath
D:\workspace\test\src\main\java;
D:\workspace\test\src\main\java\com\juvenxu\test\Test.java -g -nowarn -target
1.5 -source 1.5 -J-Duser.language=en_us
[WARNING] File encoding has not been set, using platform encoding GBK, i.e.
build is platform dependent!
[INFO] Compiling 1 source file to D:\workspace\test\target\classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] Failure executing javac, but could not parse the error:
javac: #26080;#25928;#30340;#26631;#24535;#65306;
-J-Duser.language=en_us
#29992;#27861;: javac options source files
-help #29992;#20110;#21015;#20986;#21487;#33021;#30340;#36873;#39033;
[INFO] 1error
[INFO] -
[INFO]
[jira] Commented: (MCOMPILER-129) unable to pass in javac -J option
[
https://jira.codehaus.org/browse/MCOMPILER-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277235#comment-277235
]
Robert Scholte commented on MCOMPILER-129:
--
I had to edit previous comment, because I made a typo in the configuration. Due
to this it seemed to work, but it didn't.
The {{cplrArgsCopy}} which is passed to the Plexus Compiler separates the key
and value with a space instead of a '='.
I've looked at its sourcecode and right now there's no way to specify which
separator should be used.
So that brings us back to the original issue.
unable to pass in javac -J option
-
Key: MCOMPILER-129
URL: https://jira.codehaus.org/browse/MCOMPILER-129
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Environment: jdk 1.6
maven 3.0-beta-1
Reporter: Juven Xu
Assignee: Robert Scholte
because of MCOMPILER-109, l10n-ed javac warning messages will be regarded as
error, so I want to pass user language configuration to javac, like this:
javac ... -J-Duser.language=en_us
this works well on pure javac command line, but when I configure this for
maven-compiler-plugin:
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.3.1/version
configuration
forktrue/fork
source1.5/source
target1.5/target
compilerArgument-J-Duser.language=en_us/compilerArgument
/configuration
/plugin
I got#65306;
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile' with basic
configurator --
[DEBUG] (f) basedir = D:\workspace\test
[DEBUG] (f) buildDirectory = D:\workspace\test\target
[DEBUG] (f) classpathElements = [D:\workspace\test\target\classes]
[DEBUG] (f) compileSourceRoots = [D:\workspace\test\src\main\java]
[DEBUG] (f) compilerArgument = -J-Duser.language=en_us
[DEBUG] (f) compilerId = javac
[DEBUG] (f) debug = true
[DEBUG] (f) failOnError = true
[DEBUG] (f) fork = true
[DEBUG] (f) generatedSourcesDirectory =
D:\workspace\test\target\generated-sources\annotations
[DEBUG] (f) optimize = false
[DEBUG] (f) outputDirectory = D:\workspace\test\target\classes
[DEBUG] (f) outputFileName = test-0.0.1-SNAPSHOT
[DEBUG] (f) projectArtifact = com.juvenxu:test:jar:0.0.1-SNAPSHOT
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@11d2572
[DEBUG] (f) showDeprecation = false
[DEBUG] (f) showWarnings = false
[DEBUG] (f) source = 1.5
[DEBUG] (f) staleMillis = 0
[DEBUG] (f) target = 1.5
[DEBUG] (f) verbose = false
[DEBUG] -- end configuration --
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories: [D:\workspace\test\src\main\java]
[DEBUG] Classpath: [D:\workspace\test\target\classes]
[DEBUG] Output directory: D:\workspace\test\target\classes
[DEBUG] Classpath:
[DEBUG] D:\workspace\test\target\classes
[DEBUG] Source roots:
[DEBUG] D:\workspace\test\src\main\java
[DEBUG] Command line options:
[DEBUG] -d D:\workspace\test\target\classes -classpath
D:\workspace\test\target\classes; -sourcepath
D:\workspace\test\src\main\java;
D:\workspace\test\src\main\java\com\juvenxu\test\Test.java -g -nowarn -target
1.5 -source 1.5 -J-Duser.language=en_us
[WARNING] File encoding has not been set, using platform encoding GBK, i.e.
build is platform dependent!
[INFO] Compiling 1 source file to D:\workspace\test\target\classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] Failure executing javac, but could not parse the error:
javac: #26080;#25928;#30340;#26631;#24535;#65306;
-J-Duser.language=en_us
#29992;#27861;: javac options source files
-help #29992;#20110;#21015;#20986;#21487;#33021;#30340;#36873;#39033;
[INFO] 1error
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.451s
[INFO] Finished at: Wed May 26 17:29:06 CST 2010
[INFO] Final Memory: 2M/5M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project test: Compilation failure
Failure executing javac, but could not parse the error:
javac: #26080;#25928;#30340;#26631;#24535;#65306;
-J-Duser.language=en_us
#29992;#27861;: javac options source files
-help #29992;#20110;#21015;#20986;#21487;#33021;#30340;#36873;#39033;
- [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal
