[jira] (MCOMPILER-236) Compilation error due to MCOMPILER-157 in deploy phase
Federico Gaule created MCOMPILER-236:
Summary: Compilation error due to MCOMPILER-157 in deploy phase
Key: MCOMPILER-236
URL: https://jira.codehaus.org/browse/MCOMPILER-236
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.2
Environment: Maven 3.2.3, Java 1.8.0_25
Reporter: Federico Gaule
After upgrading from 3.1 to 3.2 i'm experiencing compilation errors when
running deploy phase.
It's a mult module project where plugin is configured in master pom:
{code:xml}
org.apache.maven.plugins
maven-compiler-plugin
3.1
${compiler.version}
${compiler.version}
UTF-8
-parameters
{code}
And in one of the modules like this:
{code:xml}
org.apache.maven.plugins
maven-compiler-plugin
org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor
{code}
Common builds are all ok, but when using deploy phase i got a compiler error
{noformat}
An exception has occurred in the compiler (1.8.0_25). Please file a bug at the
Java Developer Connection (http://java.sun.com/webapps/bugreport) after
checking the Bug Parade for duplicates. Include your program and the following
diagnostic in your report. Thank you.
java.lang.IllegalStateException: endPosTable already set
at
com.sun.tools.javac.util.DiagnosticSource.setEndPosTable(DiagnosticSource.java:136)
at com.sun.tools.javac.util.Log.setEndPosTable(Log.java:350)
at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:667)
at
com.sun.tools.javac.main.JavaCompiler.parseFiles(JavaCompiler.java:950)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:892)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.next(JavacProcessingEnvironment.java:921)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1187)
at
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
at com.sun.tools.javac.main.Main.compile(Main.java:523)
at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)
at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)
at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125)
at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:823)
at
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[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: Maven Checkstyle Plugin
Issue Type: Bug
Reporter: Andreas Gudian
During fixing the checkstyle errors for surefire, I noticed that the very first
checkstyle error is not printed on the console ouput.
For example, the checkstyle-result.xml contains 111 errors for surefire-common
(in my local version) and for AbstractSurefireMojo.java, there are two errors
(file has too many lines, and @Nonnull at the wrong position)
{code}
[INFO] There are 111 checkstyle errors.
[ERROR] AbstractSurefireMojo.java[2296:16] (modifier) ModifierOrder: '@Nonnull'
Annotation-Modifier sollte vor den anderen Modifie
rn stehen.
[ERROR] BooterSerializer.java[78:114] (whitespace) ParenPad: Vor ')' befindet
sich kein Leerzeichen.
... nothing more about AbstractSurefireMojo.java
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.825s
[INFO] Finished at: Sat Oct 25 20:26:42 CEST 2014
[INFO] Final Memory: 11M/109M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check (default-cli) on
project maven-surefire
-common: You have 101 Checkstyle violations. -> [Help 1]
{code}
The summary about the failing build says something about 101 checkstyle
violations, not 111 errors as above.
I also noticed that if I fix all but one checkstyle error, the module passes
the test. The output contains just the line "[INFO] There are 1 checkstyle
errors." for that module and then continues with the next build.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1081) Doc claims parallel is TestNG only, but rest of doc implies junit works, too.
[ https://jira.codehaus.org/browse/SUREFIRE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1081: -- Assignee: Tibor Digana > Doc claims parallel is TestNG only, but rest of doc implies junit works, too. > - > > Key: SUREFIRE-1081 > URL: https://jira.codehaus.org/browse/SUREFIRE-1081 > Project: Maven Surefire > Issue Type: Bug >Reporter: Benson Margulies >Assignee: Tibor Digana > Fix For: 2.18 > > > The 'parallel' param's doc started with a statement of TestNG only-ness, but > then goes on to talk about the junit provider. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1081) Doc claims parallel is TestNG only, but rest of doc implies junit works, too.
[ https://jira.codehaus.org/browse/SUREFIRE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1081: --- Fix Version/s: 2.18 > Doc claims parallel is TestNG only, but rest of doc implies junit works, too. > - > > Key: SUREFIRE-1081 > URL: https://jira.codehaus.org/browse/SUREFIRE-1081 > Project: Maven Surefire > Issue Type: Bug >Reporter: Benson Margulies >Assignee: Tibor Digana > Fix For: 2.18 > > > The 'parallel' param's doc started with a statement of TestNG only-ness, but > then goes on to talk about the junit provider. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1097) improve documentation includes/excludes
[
https://jira.codehaus.org/browse/SUREFIRE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1097:
---
Fix Version/s: 2.18
> improve documentation includes/excludes
> ---
>
> Key: SUREFIRE-1097
> URL: https://jira.codehaus.org/browse/SUREFIRE-1097
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.17
>Reporter: Robert Scholte
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 2.18
>
>
> See
> http://maven.apache.org/surefire/maven-surefire-plugin/examples/inclusion-exclusion.html
> and
> http://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html
> For newbies it is not clear that these values are relative to
> {{src/test/java}} and possible additional test-source folders
> A full path of an include or exclude would help (I've seen some trying to do
> a mixture of path and package like {{src/test/java/com.foo.bar.Test.java}} ).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1097) improve documentation includes/excludes
[
https://jira.codehaus.org/browse/SUREFIRE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1097:
--
Assignee: Tibor Digana
> improve documentation includes/excludes
> ---
>
> Key: SUREFIRE-1097
> URL: https://jira.codehaus.org/browse/SUREFIRE-1097
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.17
>Reporter: Robert Scholte
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 2.18
>
>
> See
> http://maven.apache.org/surefire/maven-surefire-plugin/examples/inclusion-exclusion.html
> and
> http://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html
> For newbies it is not clear that these values are relative to
> {{src/test/java}} and possible additional test-source folders
> A full path of an include or exclude would help (I've seen some trying to do
> a mixture of path and package like {{src/test/java/com.foo.bar.Test.java}} ).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1083) Prefix user properties with plugin name
[
https://jira.codehaus.org/browse/SUREFIRE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1083:
---
Fix Version/s: 3.0
> Prefix user properties with plugin name
> ---
>
> Key: SUREFIRE-1083
> URL: https://jira.codehaus.org/browse/SUREFIRE-1083
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.17
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
> Fix For: 3.0
>
>
> Based on a [question on
> SO|http://stackoverflow.com/questions/24441210/maven-3-javadoc-plugin-conflicts-with-testng-groups]
> the problem is that some properties of maven-surefire-plugin /
> maven-failsafe are not being prefixed consistently by the plugn mame.
> This should be changed to prevent such problems on command line:
> {noformat}mvn install -Dgroups=somegroup{noformat} which is accidently picked
> up by maven-javadoc-plugin.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1068) forkNumber in systemPropertyVariables requires prefix
[
https://jira.codehaus.org/browse/SUREFIRE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354969#comment-354969
]
Tibor Digana commented on SUREFIRE-1068:
Meanwhile this may work as well
\${surefire.forkNumber}
> forkNumber in systemPropertyVariables requires prefix
> -
>
> Key: SUREFIRE-1068
> URL: https://jira.codehaus.org/browse/SUREFIRE-1068
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.16
>Reporter: Eric Pederson
>Priority: Minor
>
> The {{$\{surefire.forkNumber\}}} placeholder cannot be used alone in a
> {{systemPropertyVariable}}. The workaround is to prefix the value.
> For example, this doesn't work (the {{surefire.forkNumber}} system property
> does not exist when running the test).
> {code:xml}
>
> ${surefire.forkNumber}
>
> {code}
> But this does:
> {code:xml}
>
> 0${surefire.forkNumber}
>
> {code}
> (note the leading *0*)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1068) forkNumber in systemPropertyVariables requires prefix
[
https://jira.codehaus.org/browse/SUREFIRE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1068:
--
Assignee: Tibor Digana
> forkNumber in systemPropertyVariables requires prefix
> -
>
> Key: SUREFIRE-1068
> URL: https://jira.codehaus.org/browse/SUREFIRE-1068
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.16
>Reporter: Eric Pederson
>Assignee: Tibor Digana
>Priority: Minor
>
> The {{$\{surefire.forkNumber\}}} placeholder cannot be used alone in a
> {{systemPropertyVariable}}. The workaround is to prefix the value.
> For example, this doesn't work (the {{surefire.forkNumber}} system property
> does not exist when running the test).
> {code:xml}
>
> ${surefire.forkNumber}
>
> {code}
> But this does:
> {code:xml}
>
> 0${surefire.forkNumber}
>
> {code}
> (note the leading *0*)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-987) Provide user property for suiteXmlFile so that it can be passed from Maven Command line
[ https://jira.codehaus.org/browse/SUREFIRE-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354970#comment-354970 ] Tibor Digana commented on SUREFIRE-987: --- Is this working? -Dit.test=some/package/*IT.java Currently we have a bug that -Dtest works instead of -Dit.test > Provide user property for suiteXmlFile so that it can be passed from Maven > Command line > --- > > Key: SUREFIRE-987 > URL: https://jira.codehaus.org/browse/SUREFIRE-987 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin >Affects Versions: 2.12 > Environment: Mac 10.8.2 >Reporter: Manmohan Veettil >Priority: Critical > > Can we have a way to run all the tests in a package? I know we can run all > tests in a class using -Dit.test option. > OR > Can we define a user property for suiteXmlFile so that tests in a package can > be run using maven fail-safe plugin. > mvn clean install -DsuiteXmlFile=test1.xml > Thanks, > manmohanpv -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-987) Provide user property for suiteXmlFile so that it can be passed from Maven Command line
[ https://jira.codehaus.org/browse/SUREFIRE-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-987: - Assignee: Tibor Digana > Provide user property for suiteXmlFile so that it can be passed from Maven > Command line > --- > > Key: SUREFIRE-987 > URL: https://jira.codehaus.org/browse/SUREFIRE-987 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin >Affects Versions: 2.12 > Environment: Mac 10.8.2 >Reporter: Manmohan Veettil >Assignee: Tibor Digana >Priority: Critical > > Can we have a way to run all the tests in a package? I know we can run all > tests in a class using -Dit.test option. > OR > Can we define a user property for suiteXmlFile so that tests in a package can > be run using maven fail-safe plugin. > mvn clean install -DsuiteXmlFile=test1.xml > Thanks, > manmohanpv -- This message was sent by Atlassian JIRA (v6.1.6#6162)
