[jira] (MWAR-167) Final manifest not written to exploded location

2015-01-08 Thread Karl-Heinz Marbaise (JIRA) 

[ 
https://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360974#comment-360974
 ] 

Karl-Heinz Marbaise edited comment on MWAR-167 at 1/8/15 1:23 PM:
--

Fixed in [r1650354|http://svn.apache.org/r1650354]
Patch applied with slight modifications.
Followup in [r1650356|http://svn.apache.org/r1650356]
Added missing exclusion for MANIFEST.MF file for apache-rat-plugin.


was (Author: khmarbaise):
Fixed in [r1650354|http://svn.apache.org/r1650354]
Patch applied with slight modifications.

> Final manifest not written to exploded location
> ---
>
> Key: MWAR-167
> URL: https://jira.codehaus.org/browse/MWAR-167
> Project: Maven WAR Plugin
>  Issue Type: Bug
>  Components: manifest
>Affects Versions: 2.1-alpha-1
>Reporter: Paul Benedict
>Assignee: Karl-Heinz Marbaise
> Fix For: 2.6
>
> Attachments: mvn167-with-it.diff, patch.diff
>
>
> When I open up my generated WAR file, the Manifest file contains all the 
> entries I specified. This is correct. However, when I look into the exploded 
> location, it's just the file I had in my project to begin with.
> The exploded Manifest should be updated with the final contents.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MWAR-167) Final manifest not written to exploded location

2015-01-08 Thread Karl-Heinz Marbaise (JIRA) 

 [ 
https://jira.codehaus.org/browse/MWAR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl-Heinz Marbaise closed MWAR-167.


Resolution: Fixed
  Assignee: Karl-Heinz Marbaise

Fixed in [r1650354|http://svn.apache.org/r1650354]
Patch applied with slight modifications.

> Final manifest not written to exploded location
> ---
>
> Key: MWAR-167
> URL: https://jira.codehaus.org/browse/MWAR-167
> Project: Maven WAR Plugin
>  Issue Type: Bug
>  Components: manifest
>Affects Versions: 2.1-alpha-1
>Reporter: Paul Benedict
>Assignee: Karl-Heinz Marbaise
> Fix For: 2.6
>
> Attachments: mvn167-with-it.diff, patch.diff
>
>
> When I open up my generated WAR file, the Manifest file contains all the 
> entries I specified. This is correct. However, when I look into the exploded 
> location, it's just the file I had in my project to begin with.
> The exploded Manifest should be updated with the final contents.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHECKSTYLE-252) Version 2.13 includes non-source files in checks

2015-01-08 Thread Brent Ryan (JIRA) 

[ 
https://jira.codehaus.org/browse/MCHECKSTYLE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360968#comment-360968
 ] 

Brent Ryan commented on MCHECKSTYLE-252:


I want to add that this also seems to have caused checkstyle to include 
target/generated-sources and there doesn't appear to be anyway to exclude it.

This is pretty huge because it means we can't use checkstyle at all for Java8 
projects.

> Version 2.13 includes non-source files in checks
> 
>
> Key: MCHECKSTYLE-252
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-252
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle
>Affects Versions: 2.13
>Reporter: Michael Heuer
> Fix For: 2.14
>
> Attachments: mcheckstyle-252.tar.gz
>
>
> Updating maven-checkstyle-plugin to version 2.13 and running
> $ mvn site
> now includes non-source files in its checks, e.g.
> COPYING
> COPYING.LESSER
> target/generated-classes/cobertura/cobertura.properties
> While it is rather amusing to have checkstyle complain that COPYING (the text 
> of the GNU General Public License) doesn't include a license header, it seems 
> that the default source root or one of the other properties new to version 
> 2.13 does not have an appropriate default value.  The target directory should 
> also be excluded by default.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHECKSTYLE-271) checkstyle plugin fails with default ruleset and checkstyle 6.2

2015-01-08 Thread Dennis Lundberg (JIRA) 

 [ 
https://jira.codehaus.org/browse/MCHECKSTYLE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MCHECKSTYLE-271:


Fix Version/s: (was: 2.15)
   2.16

> checkstyle plugin fails with default ruleset and checkstyle 6.2
> ---
>
> Key: MCHECKSTYLE-271
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-271
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>  Components: checkstyle:checkstyle, predefined ruleset: Sun
>Affects Versions: 2.13
>Reporter: Henning Schmiedehausen
> Fix For: 2.16
>
>
> when using the 2.13 plugin with checkstyle 6.2, it fails with
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check (default) on 
> project otj-parent: Failed during checkstyle configuration: cannot initialize 
> module TreeWalker - Unable to instantiate RedundantThrows: Unable to 
> instantiate RedundantThrowsCheck -> [Help 1]
> because the sun ruleset contains RedundantThrows 
> (https://github.com/apache/maven-plugins/blob/trunk/maven-checkstyle-plugin/src/main/resources/config/sun_checks.xml#L168)
>  which got removed in checkstyle 6.2  
> (https://github.com/checkstyle/checkstyle/issues/473)



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHECKSTYLE-272) Upgrade to Checkstyle 6.2

2015-01-08 Thread Dennis Lundberg (JIRA) 

 [ 
https://jira.codehaus.org/browse/MCHECKSTYLE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MCHECKSTYLE-272:


Fix Version/s: 2.16

> Upgrade to Checkstyle 6.2
> -
>
> Key: MCHECKSTYLE-272
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-272
> Project: Maven Checkstyle Plugin
>  Issue Type: Improvement
>Reporter: Dennis Lundberg
> Fix For: 2.16
>
>
> This version of Checkstyle requires Java 7.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHECKSTYLE-272) Upgrade to Checkstyle 6.2

2015-01-08 Thread Dennis Lundberg (JIRA) 
Dennis Lundberg created MCHECKSTYLE-272:
---

 Summary: Upgrade to Checkstyle 6.2
 Key: MCHECKSTYLE-272
 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-272
 Project: Maven Checkstyle Plugin
  Issue Type: Improvement
Reporter: Dennis Lundberg


This version of Checkstyle requires Java 7.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNGSITE-220) Wrong " test source directory" named in "Introduction to the POM"

2015-01-08 Thread Markus Bollerey (JIRA) 
Markus Bollerey created MNGSITE-220:
---

 Summary: Wrong " test source directory" named in "Introduction to 
the POM"
 Key: MNGSITE-220
 URL: https://jira.codehaus.org/browse/MNGSITE-220
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: Just about the content, not depending to any 
environmental issues.
Reporter: Markus Bollerey
Priority: Minor


Described here is an error in the Web Documentation Site of Maven "Introduction 
to the POM" as found under 
.

In the first section named "What is a POM?", some examples for default values 
of the POM are given. For the test source directory it says: "src/main/test".

This is wrong and should be corrected to "src/test/java".



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild

2015-01-08 Thread Tibor Digana (JIRA) 

 [ 
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1132.
--

Resolution: Not A Bug

Referenced by real bug https://jira.codehaus.org/browse/MNG-5750

> Surefire: regular isolated classloader failures in parallelbuild
> 
>
> Key: SUREFIRE-1132
> URL: https://jira.codehaus.org/browse/SUREFIRE-1132
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: classloading
>Affects Versions: 2.17, 2.18.1
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux
> windows server 2008 x64
> Maven 3.2.2, 3.2.3, 3.2.5
> Oracle HotSpot JDK 7u25/7u65/8u25
>Reporter: Alexander Ashitkin
>Assignee: Tibor Digana
> Attachments: consoleText-1.txt, consoleText-2.txt, consoleText-3.txt
>
>
> We have a large project of 300+ modules which regularly fails with different 
> kind of classloading issues in different places in surefire plugin. The issue 
> is reproduced only with parallel build and is not reproduced in single 
> threaded. This is a main contributor in build instability for us. All the not 
> loaded dependnecies are actually present in dependency tree. I attached 3 
> different samples of how build fails.
> Surefire config:
> {code}
> 
> 0
>  
>  false
> false
> 
> {code}
> maven cmd is like install -T 10
>  Please advise how to sort this out - ready to run any provided diagnostic 
> and evaluate any options.
> Thanks in advance, Alexander



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MPMD-200) Regression: Rule:UnusedPrivateMethod

2015-01-08 Thread Michael Osipov (JIRA) 

 [ 
https://jira.codehaus.org/browse/MPMD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MPMD-200.
---

Resolution: Fixed

Verfified as fixed with 3.4

> Regression: Rule:UnusedPrivateMethod
> 
>
> Key: MPMD-200
> URL: https://jira.codehaus.org/browse/MPMD-200
> Project: Maven PMD Plugin
>  Issue Type: Bug
>  Components: PMD
>Affects Versions: 3.3
>Reporter: Alexey Markevich
>Assignee: Michael Osipov
> Fix For: 3.4
>
> Attachments: maven-pmd-unused-private-method.zip
>
>
> After upgrade from 3.1 to 3.3 there is failure detection:
> [INFO] PMD Failure: test.Test:23 Rule:UnusedPrivateMethod Priority:3 Avoid 
> unused private methods such as 'createException(Exception)'..



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MPMD-200) Regression: Rule:UnusedPrivateMethod

2015-01-08 Thread Michael Osipov (JIRA) 

 [ 
https://jira.codehaus.org/browse/MPMD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MPMD-200:


Fix Version/s: 3.4

> Regression: Rule:UnusedPrivateMethod
> 
>
> Key: MPMD-200
> URL: https://jira.codehaus.org/browse/MPMD-200
> Project: Maven PMD Plugin
>  Issue Type: Bug
>  Components: PMD
>Affects Versions: 3.3
>Reporter: Alexey Markevich
> Fix For: 3.4
>
> Attachments: maven-pmd-unused-private-method.zip
>
>
> After upgrade from 3.1 to 3.3 there is failure detection:
> [INFO] PMD Failure: test.Test:23 Rule:UnusedPrivateMethod Priority:3 Avoid 
> unused private methods such as 'createException(Exception)'..



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MPMD-200) Regression: Rule:UnusedPrivateMethod

2015-01-08 Thread Michael Osipov (JIRA) 

 [ 
https://jira.codehaus.org/browse/MPMD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov reassigned MPMD-200:
---

Assignee: Michael Osipov

> Regression: Rule:UnusedPrivateMethod
> 
>
> Key: MPMD-200
> URL: https://jira.codehaus.org/browse/MPMD-200
> Project: Maven PMD Plugin
>  Issue Type: Bug
>  Components: PMD
>Affects Versions: 3.3
>Reporter: Alexey Markevich
>Assignee: Michael Osipov
> Fix For: 3.4
>
> Attachments: maven-pmd-unused-private-method.zip
>
>
> After upgrade from 3.1 to 3.3 there is failure detection:
> [INFO] PMD Failure: test.Test:23 Rule:UnusedPrivateMethod Priority:3 Avoid 
> unused private methods such as 'createException(Exception)'..



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MJAR-192) Sporadic NPE in maven-jar-plugin:2.5:jar

2015-01-08 Thread Michael Osipov (JIRA) 

[ 
https://jira.codehaus.org/browse/MJAR-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360941#comment-360941
 ] 

Michael Osipov commented on MJAR-192:
-

I would rather leave this open and depend upon the core issue.

> Sporadic NPE in maven-jar-plugin:2.5:jar
> 
>
> Key: MJAR-192
> URL: https://jira.codehaus.org/browse/MJAR-192
> Project: Maven JAR Plugin
>  Issue Type: Bug
>Affects Versions: 2.5
> Environment: win 2008 server x64 java 8u25 maven 3.2.5
>Reporter: Alexander Ashitkin
>
> Strange npe at jar goal:
> {code}
> 16:41:50 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) on project 
> my-model: Error assembling JAR: NullPointerException -> [Help 1]
> 16:41:50 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
> execute goal org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) 
> on project my-model: Error assembling JAR
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
> 16:41:50  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 16:41:50  at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 16:41:50  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 16:41:50  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 16:41:50  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 16:41:50  at java.lang.Thread.run(Thread.java:745)
> 16:41:50 Caused by: org.apache.maven.plugin.MojoExecutionException: Error 
> assembling JAR
> 16:41:50  at 
> org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:233)
> 16:41:50  at 
> org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:251)
> 16:41:50  at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 16:41:50  ... 11 more
> 16:41:50 Caused by: java.lang.NullPointerException
> 16:41:50  at 
> org.apache.maven.project.MavenProject.getArtifacts(MavenProject.java:715)
> 16:41:50  at 
> org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1218)
> 16:41:50  at 
> org.apache.maven.project.MavenProject.(MavenProject.java:197)
> 16:41:50  at 
> org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
> 16:41:50  at 
> org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:226)
> 16:41:50  ... 14 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MEAR-212) Failed to initialize ear modules: Unknown artifact type[mar] for addressing

2015-01-08 Thread Karl-Heinz Marbaise (JIRA) 

[ 
https://jira.codehaus.org/browse/MEAR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360940#comment-360940
 ] 

Karl-Heinz Marbaise commented on MEAR-212:
--

Could you provide a full working project which reproduces this problem. Apart 
from that {{ Unknown artifact type[mar] for addressing }} seemed to be the 
problem here. 

> Failed to initialize ear modules: Unknown artifact type[mar] for addressing
> ---
>
> Key: MEAR-212
> URL: https://jira.codehaus.org/browse/MEAR-212
> Project: Maven Ear Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: David Hoffer
>
> I'm trying to generate and ear file but I'm getting the following message:  
> Failed to initialize ear modules: Unknown artifact type[mar] for addressing  
> (full debug stack trace is below)
> However I don't have any mar artifacts in my dependencies.  What I do have is 
> a war that has 4 mar files added as resources and I'm making a ear with the 
> skinny war feature.
> Why would the ear plugin give this error when it has no nothing to do with 
> the mar resources in the war...or perhaps this error has nothing to do with 
> those resources, not sure.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
> (default-generate-application-xml) on project coreservices-ear: Failed to 
> initialize ear modules: Unknown artifact type[mar] for addressing -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
> (default-generate-application-xml) on project coreservices-ear: Failed to 
> initialize ear modules
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>   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)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to 
> initialize ear modules
>   at 
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260)
>   at 
> org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown 
> artifact type[mar] for addressing
>   at 
> org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88)
>   at 
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250)
>   ... 22 more



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MEAR-212) Failed to initialize ear modules: Unknown artifact type[mar] for addressing

2015-01-08 Thread Karl-Heinz Marbaise (JIRA) 

 [ 
https://jira.codehaus.org/browse/MEAR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl-Heinz Marbaise updated MEAR-212:
-

Description: 
I'm trying to generate and ear file but I'm getting the following message:  
Failed to initialize ear modules: Unknown artifact type[mar] for addressing  
(full debug stack trace is below)

However I don't have any mar artifacts in my dependencies.  What I do have is a 
war that has 4 mar files added as resources and I'm making a ear with the 
skinny war feature.

Why would the ear plugin give this error when it has no nothing to do with the 
mar resources in the war...or perhaps this error has nothing to do with those 
resources, not sure.

{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
(default-generate-application-xml) on project coreservices-ear: Failed to 
initialize ear modules: Unknown artifact type[mar] for addressing -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
(default-generate-application-xml) on project coreservices-ear: Failed to 
initialize ear modules
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
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)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to initialize 
ear modules
at 
org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260)
at 
org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown 
artifact type[mar] for addressing
at 
org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88)
at 
org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250)
... 22 more
{code}

  was:
I'm trying to generate and ear file but I'm getting the following message:  
Failed to initialize ear modules: Unknown artifact type[mar] for addressing  
(full debug stack trace is below)

However I don't have any mar artifacts in my dependencies.  What I do have is a 
war that has 4 mar files added as resources and I'm making a ear with the 
skinny war feature.

Why would the ear plugin give this error when it has no nothing to do with the 
mar resources in the war...or perhaps this error has nothing to do with those 
resources, not sure.

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
(default-generate-application-xml) on project coreservices-ear: Failed to 
initialize ear modules: Unknown artifact type[mar] for addressing -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml 
(default-generate-application-xml) on project coreservices-ear: Failed to 
initialize ear modules
at 
org.apache.maven.lifecycle.internal.MojoExecuto

[jira] (MPMD-200) Regression: Rule:UnusedPrivateMethod

2015-01-08 Thread Alexey Markevich (JIRA) 

[ 
https://jira.codehaus.org/browse/MPMD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360939#comment-360939
 ] 

Alexey Markevich commented on MPMD-200:
---

Its ok with 3.4-SNAPSHOT

> Regression: Rule:UnusedPrivateMethod
> 
>
> Key: MPMD-200
> URL: https://jira.codehaus.org/browse/MPMD-200
> Project: Maven PMD Plugin
>  Issue Type: Bug
>  Components: PMD
>Affects Versions: 3.3
>Reporter: Alexey Markevich
> Attachments: maven-pmd-unused-private-method.zip
>
>
> After upgrade from 3.1 to 3.3 there is failure detection:
> [INFO] PMD Failure: test.Test:23 Rule:UnusedPrivateMethod Priority:3 Avoid 
> unused private methods such as 'createException(Exception)'..



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5750) Sporadic failures in concurrent build

2015-01-08 Thread Alexander Ashitkin (JIRA) 

 [ 
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Ashitkin updated MNG-5750:


Description: 
We have a large project of 300+ modules which regularly fails with different 
kind of errors in different places. The issue is reliably reproduced with 
parallel build and is not happens in single threaded. The optimal concurrency 
level for our project ~10 threads. At this level ~%20 of builds fail. To 
workaround the issue we reduced concurrency to 4 in development builds and 
reverted production build to 1 thread.

Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to 
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# Compiler - unexpected failure because of incorrect classpath (literally all 
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package 
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import 
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import 
only from classes and interfaces
{code}
# Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly 
plusgin seems to be also affected)

At this point the issue looks like problem with MavenProject#getArtifacts in 
concurrent builds.

To help with the issue im happy to implement or evaluate any custom assembly to 
trace this down. Unfortunately i cannot submit my project - it is proprietary.

Thanks in advance, Alexander

  was:
We have a large project of 300+ modules which regularly fails with different 
kind of errors in different places. The issue is reliably reproduced with 
parallel build and is not happens in single threaded. The optimal concurrency 
level for our project ~10 threads. At this level ~%20 of builds fail. To 
workaround the issue we reduced concurrency to 4 in development builds and 
reverted production build to 1 thread.

Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to 
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# Compiler - unexpected failure because of incorrect classpath (lterally all 
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package 
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import 
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import 
only from classes and interfaces
{code}
# Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly seems 
to be also affected)

At this point the issue looks like problem with MavenProject#getArtifacts in 
concurrent builds.

To help with the issue im happy to implement or evaluate any custom assembly to 
trace this down. Unfortunately i cannot submit my project - it is proprietary.

Thanks in advance, Alexander


> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
>  Issue Type: Bug
>  Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle 
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different 
> kind of errors in different places. The issue is reliably reproduced with 
> parallel build and is not happens in single threaded. The optimal concurrency 
> level for our project ~10 threads. A

[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild

2015-01-08 Thread Alexander Ashitkin (JIRA) 

[ 
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360938#comment-360938
 ] 

Alexander Ashitkin commented on SUREFIRE-1132:
--

the issue is reported against mvn core - MNG-5750. Please feel free to close 
the issue.

Tibor, many many thanks for you help. 

Best regards

> Surefire: regular isolated classloader failures in parallelbuild
> 
>
> Key: SUREFIRE-1132
> URL: https://jira.codehaus.org/browse/SUREFIRE-1132
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: classloading
>Affects Versions: 2.17, 2.18.1
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux
> windows server 2008 x64
> Maven 3.2.2, 3.2.3, 3.2.5
> Oracle HotSpot JDK 7u25/7u65/8u25
>Reporter: Alexander Ashitkin
>Assignee: Tibor Digana
> Attachments: consoleText-1.txt, consoleText-2.txt, consoleText-3.txt
>
>
> We have a large project of 300+ modules which regularly fails with different 
> kind of classloading issues in different places in surefire plugin. The issue 
> is reproduced only with parallel build and is not reproduced in single 
> threaded. This is a main contributor in build instability for us. All the not 
> loaded dependnecies are actually present in dependency tree. I attached 3 
> different samples of how build fails.
> Surefire config:
> {code}
> 
> 0
>  
>  false
> false
> 
> {code}
> maven cmd is like install -T 10
>  Please advise how to sort this out - ready to run any provided diagnostic 
> and evaluate any options.
> Thanks in advance, Alexander



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild

2015-01-08 Thread Alexander Ashitkin (JIRA) 

[ 
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360938#comment-360938
 ] 

Alexander Ashitkin edited comment on SUREFIRE-1132 at 1/8/15 2:02 AM:
--

the issue is reported against mvn core - MNG-5750. Please feel free to close 
the issue.

Tibor, many many thanks for your help. 

Best regards


was (Author: alex_ashitkin):
the issue is reported against mvn core - MNG-5750. Please feel free to close 
the issue.

Tibor, many many thanks for you help. 

Best regards

> Surefire: regular isolated classloader failures in parallelbuild
> 
>
> Key: SUREFIRE-1132
> URL: https://jira.codehaus.org/browse/SUREFIRE-1132
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: classloading
>Affects Versions: 2.17, 2.18.1
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux
> windows server 2008 x64
> Maven 3.2.2, 3.2.3, 3.2.5
> Oracle HotSpot JDK 7u25/7u65/8u25
>Reporter: Alexander Ashitkin
>Assignee: Tibor Digana
> Attachments: consoleText-1.txt, consoleText-2.txt, consoleText-3.txt
>
>
> We have a large project of 300+ modules which regularly fails with different 
> kind of classloading issues in different places in surefire plugin. The issue 
> is reproduced only with parallel build and is not reproduced in single 
> threaded. This is a main contributor in build instability for us. All the not 
> loaded dependnecies are actually present in dependency tree. I attached 3 
> different samples of how build fails.
> Surefire config:
> {code}
> 
> 0
>  
>  false
> false
> 
> {code}
> maven cmd is like install -T 10
>  Please advise how to sort this out - ready to run any provided diagnostic 
> and evaluate any options.
> Thanks in advance, Alexander



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MJAR-192) Sporadic NPE in maven-jar-plugin:2.5:jar

2015-01-08 Thread Alexander Ashitkin (JIRA) 

[ 
https://jira.codehaus.org/browse/MJAR-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360937#comment-360937
 ] 

Alexander Ashitkin commented on MJAR-192:
-

The issue is reported against mvn core -  MNG-5750.

Please feel free to close the issue.

Thank you

> Sporadic NPE in maven-jar-plugin:2.5:jar
> 
>
> Key: MJAR-192
> URL: https://jira.codehaus.org/browse/MJAR-192
> Project: Maven JAR Plugin
>  Issue Type: Bug
>Affects Versions: 2.5
> Environment: win 2008 server x64 java 8u25 maven 3.2.5
>Reporter: Alexander Ashitkin
>
> Strange npe at jar goal:
> {code}
> 16:41:50 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) on project 
> my-model: Error assembling JAR: NullPointerException -> [Help 1]
> 16:41:50 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
> execute goal org.apache.maven.plugins:maven-jar-plugin:2.5:jar (default-jar) 
> on project my-model: Error assembling JAR
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
> 16:41:50  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 16:41:50  at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 16:41:50  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 16:41:50  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 16:41:50  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 16:41:50  at java.lang.Thread.run(Thread.java:745)
> 16:41:50 Caused by: org.apache.maven.plugin.MojoExecutionException: Error 
> assembling JAR
> 16:41:50  at 
> org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:233)
> 16:41:50  at 
> org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:251)
> 16:41:50  at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 16:41:50  at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 16:41:50  ... 11 more
> 16:41:50 Caused by: java.lang.NullPointerException
> 16:41:50  at 
> org.apache.maven.project.MavenProject.getArtifacts(MavenProject.java:715)
> 16:41:50  at 
> org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1218)
> 16:41:50  at 
> org.apache.maven.project.MavenProject.(MavenProject.java:197)
> 16:41:50  at 
> org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
> 16:41:50  at 
> org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:226)
> 16:41:50  ... 14 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5750) Sporadic failures in concurrent build

2015-01-08 Thread Alexander Ashitkin (JIRA) 

 [ 
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Ashitkin updated MNG-5750:


Description: 
We have a large project of 300+ modules which regularly fails with different 
kind of errors in different places. The issue is reliably reproduced with 
parallel build and is not happens in single threaded. The optimal concurrency 
level for our project ~10 threads. At this level ~%20 of builds fail. To 
workaround the issue we reduced concurrency to 4 in development builds and 
reverted production build to 1 thread.

Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to 
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# Compiler - unexpected failure because of incorrect classpath (lterally all 
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package 
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import 
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import 
only from classes and interfaces
{code}
# Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly seems 
to be also affected)

At this point the issue looks like problem with MavenProject#getArtifacts in 
concurrent builds.

To help with the issue im happy to implement or evaluate any custom assembly to 
trace this down. Unfortunately i cannot submit my project - it is proprietary.

Thanks in advance, Alexander

  was:
We have a large project of 300+ modules which regularly fails with different 
kind of errors in different places. The issue is reliably reproduced with 
parallel build and is not happens in single threaded. The optimal concurrency 
level for our project ~10 threads. At this level ~%20 of builds fail. To 
workaround the issue we reduced concurrency to 4 in development builds and 
reverted production build to 1 thread.

Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to 
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all 
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ... 
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package 
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import 
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package 
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import 
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack 
traces in MJAR-192

At this point the issue looks like problem with MavenProject#getArtifacts in 
concurrent builds.

To help with the issue im happy to implement or evaluate any custom assembly to 
trace this down. Unfortunately i cannot submit my project - it is proprietary.

Thanks in advance, Alexander


> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
>  Issue Type: Bug
>  Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle 
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different 
> kind of errors in different places. The issue is reliably reproduced with 
> parallel build and is not happens in single threaded. The optimal concurrency 
> level for our project ~10 threads. At this level