[jira] [Closed] (MNG-6243) Build fails with ArrayIndexOutOfBoundsException: 53090

2017-06-24 Thread Robert Scholte (JIRA) 

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

Robert Scholte closed MNG-6243.
---
Resolution: Duplicate
  Assignee: Robert Scholte

Duplicate of MNG-6216. It looks like one of your dependency pom-files got 
corrupt. Fastest solution is to clear your local repo, but it would help if you 
could confirm that a pom file is indeed not valid XML amymore after downloading.

> Build fails with ArrayIndexOutOfBoundsException: 53090
> --
>
> Key: MNG-6243
> URL: https://issues.apache.org/jira/browse/MNG-6243
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.5.0
> Environment: macos 10.12.6 & CENTOS 7, java 8_131, maven 3.5
>Reporter: Dave Wolf
>Assignee: Robert Scholte
> Attachments: redacted_dtos_pom.xml, redacted_pom.xml
>
>
> my team has a multi-module maven project that builds fine using Maven 3.3.9, 
> but fails when using Maven 3.5.0. In both cases (i.e. maven versions), the 
> build is using java 8_131. The failures occur both on MacOS Sierra 10.12.6 
> and CENTOS 7. A separate non-multi-module project builds fine under both 
> versions of Maven.
> I've updated the parent pom with the flatten-maven-plugin per the Maven CI 
> Friendly Versions doc. I've checked the other issues on here and else where 
> not finding an answered similar issue. There is another unanswered 
> StackOverflow 
> [question|https://stackoverflow.com/questions/44559325/maven-is-throwing-arrayoutofboundsexception]:
>  that may have it's roots in the same issue.
> Any help determining the problem would be much appreciated.
> failed build with [Maven 3.5.0|https://pastebin.com/vHTE7HGA]:
> successful build with [Maven 3.3.9|https://pastebin.com/37wc4Ybq]:
> I've attached the parent pom and one of the child pom files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MRELEASE-985) Override SNAPSHOT dependencies from command line

2017-06-24 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/MRELEASE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061830#comment-16061830
 ] 

ASF GitHub Bot commented on MRELEASE-985:
-

GitHub user ptahchiev opened a pull request:

https://github.com/apache/maven-release/pull/18

MRELEASE-985

This commit copies resolved snapshot dependencies system properties to the 
release descriptor
and then checks if the those resolved snapshot dependencies contain the 
SNAPSHOT artifact before
before adding it as a SNAPSHOT dependency.

Fixes: https://issues.apache.org/jira/browse/MRELEASE-985

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptahchiev/maven-release MRELEASE-985

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-release/pull/18.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #18


commit f2775c83af6b5347e266f74c99edbb920046824b
Author: petar.tahchiev 
Date:   2017-06-24T06:44:35Z

Override snapshot dependencies from command line.

This commit copies resolved snapshot dependencies system properties to the 
release descriptor
and then checks if the those resolved snapshot dependencies contain the 
SNAPSHOT artifact before
before adding it as a SNAPSHOT dependency.

Fixes: https://issues.apache.org/jira/browse/MRELEASE-985




> Override SNAPSHOT dependencies from command line
> 
>
> Key: MRELEASE-985
> URL: https://issues.apache.org/jira/browse/MRELEASE-985
> Project: Maven Release Plugin
>  Issue Type: New Feature
>Reporter: Petar Tahchiev
>
> As a user I would like to be able to override SNAPSHOT dependencies from the 
> command line so that the build would not be aborted if I have SNAPSHOT 
> dependencies in my {{pom.xml}}.
> For example let's consider I have a {{pom.xml}} which declares the following 
> dependency:
> {code}
> 
> com.mycompany
> test
> 1.0-SNAPSHOT
> 
> {code}
> or this parent:
> {code}
> 
> com.mycompany
> test
> 1.0-SNAPSHOT
> 
> {code}
> When I start the build it would fail, because I have unresolved SNAPSHOT 
> dependencies. However, it would be really useful if I can specify the 
> following:
> {code}
> mvn release:prepare --batch-mode 
> -DdependencyVersion.com.mycompany:test=1.1.RELEASE 
> -DdevelopmentVersion.com.mycompany:test=1.2.BUILD-SNAPSHOT
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1264) Some tests can be lost when running in parallel with parameterized tests

2017-06-24 Thread Tibor Digana (JIRA) 

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061860#comment-16061860
 ] 

Tibor Digana commented on SUREFIRE-1264:


[~tlemeur]
First I have to finish another pending issue and then I will dig into this. I 
will inform you.

> Some tests can be lost when running in parallel with parameterized tests
> 
>
> Key: SUREFIRE-1264
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1264
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
> Environment: Maven 3.3.9
> Java 1.8.0_45 (Oracle)
> System: OS X
> Reproduced on Linux too, with both OpenJDK 7 and Java 7 from Oracle.
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
>
> Hello,
> It appears some tests can be lost when using the parallel mode with 
> parameterized tests. Here is a [small 
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1] I've 
> used to try to reproduce the issue we have seen.
> This is not something that happens on every run, but it's quite frequent.
> With this loop, the problem should appear in less than 2 minutes, maybe on 
> the first run when (un)lucky:
> {code}
> time while true; do mvn clean test > last.log ; tail -25 last.log ; if [ 
> "$(grep -c 'Tests run: 12' last.log)" == "0" ]; then break; fi ; done
> {code}
> Normal run:
> {noformat}
> ---
>  T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec - 
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec - 
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> When tests have been lost (here one test lost according to the output):
> {noformat}
> ---
>  T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => start
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec - 
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec - 
> in [p2]
> Results :
> Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Note: there are 3 test classes and 18 tests on the [master 
> branch|https://github.com/jderrien/surefire-junit-tests/tree/master] and it's 
> even more frequent/easy to reproduce.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MSKINS-135) add an option to edit page with Apache CMS

2017-06-24 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/MSKINS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062011#comment-16062011
 ] 

Hervé Boutemy commented on MSKINS-135:
--

can use glyphicon edit: 
https://www.w3schools.com/icons/tryit.asp?filename=trybs_ref_glyph_edit with a 
href containing the same javascript as the bookmarklet

> add an option to edit page with Apache CMS
> --
>
> Key: MSKINS-135
> URL: https://issues.apache.org/jira/browse/MSKINS-135
> Project: Maven Skins
>  Issue Type: New Feature
>  Components: Fluido Skin
>Affects Versions: fluido-1.6
>Reporter: Hervé Boutemy
>
> it would be useful if a link to edit the current page with Apache CMS could 
> be configured: this would avoid the need to have CMS bookmarklet 
> https://cms.apache.org/#bookmark
> ideally even as anonymous user (anonymous users for sure don't know the CMS 
> and its bookmarklet)
> see Apache CMS reference: https://www.apache.org/dev/cmsref.html
> and the bookmarklet: 
> javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MSKINS-135) add an option to edit page with Apache CMS

2017-06-24 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/MSKINS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062011#comment-16062011
 ] 

Hervé Boutemy edited comment on MSKINS-135 at 6/24/17 2:30 PM:
---

can use glyphicon edit: 
https://www.w3schools.com/icons/tryit.asp?filename=trybs_ref_glyph_edit with a 
href containing the same javascript as the bookmarklet, added in the breadcrumb 
on the right


was (Author: hboutemy):
can use glyphicon edit: 
https://www.w3schools.com/icons/tryit.asp?filename=trybs_ref_glyph_edit with a 
href containing the same javascript as the bookmarklet

> add an option to edit page with Apache CMS
> --
>
> Key: MSKINS-135
> URL: https://issues.apache.org/jira/browse/MSKINS-135
> Project: Maven Skins
>  Issue Type: New Feature
>  Components: Fluido Skin
>Affects Versions: fluido-1.6
>Reporter: Hervé Boutemy
>
> it would be useful if a link to edit the current page with Apache CMS could 
> be configured: this would avoid the need to have CMS bookmarklet 
> https://cms.apache.org/#bookmark
> ideally even as anonymous user (anonymous users for sure don't know the CMS 
> and its bookmarklet)
> see Apache CMS reference: https://www.apache.org/dev/cmsref.html
> and the bookmarklet: 
> javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MNG-6216) ArrayIndexOutOfBoundsException when parsing POM

2017-06-24 Thread Robert Scholte (JIRA) 

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

Robert Scholte updated MNG-6216:

Summary: ArrayIndexOutOfBoundsException when parsing POM   (was: 
IndexArrayOutOfBounds when parsing POM )

> ArrayIndexOutOfBoundsException when parsing POM 
> 
>
> Key: MNG-6216
> URL: https://issues.apache.org/jira/browse/MNG-6216
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Marc Savy
> Fix For: 3.5.1
>
> Attachments: log
>
>
> When building apiman https://github.com/apiman/apiman.git on Maven 3.5.0 the 
> XML parser seems to have some issues parsing the apiman-test-common module. 
> If you want to reproduce, you can simply use mvn clean install, no profiles 
> needed.
> Log: https://gist.github.com/msavy/a1b4307fb238a543dfd6af426b42d446 
> Also attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MCHECKSTYLE-287) checkstyle report throws NPE

2017-06-24 Thread Michael Osipov (JIRA) 

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062066#comment-16062066
 ] 

Michael Osipov commented on MCHECKSTYLE-287:


Can someone reupload an uptodate version of the test project? I am having 
trouble to reproduce it again. [~edrandall], I'd like to test with 3.5.0 and 
then deliver a quickfix until the root cause has been found.

> checkstyle report throws NPE
> 
>
> Key: MCHECKSTYLE-287
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-287
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>Affects Versions: 2.13, 2.14
>Reporter: Thomas Scheffler
> Attachments: patch1.diff, projects.tar.gz
>
>
> I don't know what triggers this bug. Somehow 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.collectArtifacts(String)
>  produces a List which contains the null object. And therefor an exception is 
> thrown here (2.14):
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project 
> oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed. 
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on 
> project oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>   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:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
>   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:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 19 more
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.configureResourceLocator(DefaultCheckstyleExecutor.java:852)
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:102)
>   at 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:474)
>   at 
> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:156)
>   at 
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
>   at 
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
>   at 
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
>   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
>   at 
>

[jira] [Comment Edited] (MCHECKSTYLE-287) checkstyle report throws NPE

2017-06-24 Thread Ed Randall (JIRA) 

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062053#comment-16062053
 ] 

Ed Randall edited comment on MCHECKSTYLE-287 at 6/24/17 4:37 PM:
-

Still affects 2.17 with maven 3.3.9 Google shows that quite a few users 
have suffered this issue;  Is there any chance we could have a release with the 
quick tactical fix (catch NullPointerException in the offending Artifact loop) 
so we can run 'mvn site' on a multimodule project without having to figure out 
tedious workarounds?
You guys can then continue to research the root cause... it's been going on too 
long.  Thanks!


was (Author: edrandall):
Still affects 2.17 Google shows that quite a few users have suffered this 
issue;  Is there any chance we could have a release with the quick tactical fix 
(catch NullPointerException in the offending Artifact loop) so we can run 'mvn 
site' on a multimodule project without having to figure out tedious workarounds?
You guys can then continue to research the root cause... it's been going on too 
long.  Thanks!

> checkstyle report throws NPE
> 
>
> Key: MCHECKSTYLE-287
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-287
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>Affects Versions: 2.13, 2.14
>Reporter: Thomas Scheffler
> Attachments: patch1.diff, projects.tar.gz
>
>
> I don't know what triggers this bug. Somehow 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.collectArtifacts(String)
>  produces a List which contains the null object. And therefor an exception is 
> thrown here (2.14):
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project 
> oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed. 
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on 
> project oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>   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:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
>   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:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 19 more
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.configureResourceLocator(DefaultCheckstyleExecutor.java:852)
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:102)
>   at 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:474)
>   at 
>

[jira] [Commented] (MNG-6243) Build fails with ArrayIndexOutOfBoundsException: 53090

2017-06-24 Thread Dave Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/MNG-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062104#comment-16062104
 ] 

Dave Wolf commented on MNG-6243:


Removing my .m2/repository/* contents did in fact correct the problem. I also 
understand why none of my searches turned up MNG-6216, it (incorrectly) has the 
exception as IndexArrayOutOfBounds. IMO, the title of 6216 should be changed to 
"ArrayIndexOutOfBoundsException when parsing POM" so that anyone using the 
actual exception name would have the possibility of finding it.

> Build fails with ArrayIndexOutOfBoundsException: 53090
> --
>
> Key: MNG-6243
> URL: https://issues.apache.org/jira/browse/MNG-6243
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.5.0
> Environment: macos 10.12.6 & CENTOS 7, java 8_131, maven 3.5
>Reporter: Dave Wolf
>Assignee: Robert Scholte
> Attachments: redacted_dtos_pom.xml, redacted_pom.xml
>
>
> my team has a multi-module maven project that builds fine using Maven 3.3.9, 
> but fails when using Maven 3.5.0. In both cases (i.e. maven versions), the 
> build is using java 8_131. The failures occur both on MacOS Sierra 10.12.6 
> and CENTOS 7. A separate non-multi-module project builds fine under both 
> versions of Maven.
> I've updated the parent pom with the flatten-maven-plugin per the Maven CI 
> Friendly Versions doc. I've checked the other issues on here and else where 
> not finding an answered similar issue. There is another unanswered 
> StackOverflow 
> [question|https://stackoverflow.com/questions/44559325/maven-is-throwing-arrayoutofboundsexception]:
>  that may have it's roots in the same issue.
> Any help determining the problem would be much appreciated.
> failed build with [Maven 3.5.0|https://pastebin.com/vHTE7HGA]:
> successful build with [Maven 3.3.9|https://pastebin.com/37wc4Ybq]:
> I've attached the parent pom and one of the child pom files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MCHECKSTYLE-287) checkstyle report throws NPE

2017-06-24 Thread Ed Randall (JIRA) 

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062053#comment-16062053
 ] 

Ed Randall commented on MCHECKSTYLE-287:


Google shows that quite a few users have suffered this issue;  Is there any 
chance we could have a release with the quick tactical fix (catch 
NullPointerException in the offending Artifact loop) so we can run 'mvn site' 
on a multimodule project without having to figure out tedious workarounds?
You guys can then continue to research the root cause... it's been going on too 
long.  Thanks!

> checkstyle report throws NPE
> 
>
> Key: MCHECKSTYLE-287
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-287
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>Affects Versions: 2.13, 2.14
>Reporter: Thomas Scheffler
> Attachments: patch1.diff, projects.tar.gz
>
>
> I don't know what triggers this bug. Somehow 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.collectArtifacts(String)
>  produces a List which contains the null object. And therefor an exception is 
> thrown here (2.14):
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project 
> oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed. 
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on 
> project oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>   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:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
>   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:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 19 more
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.configureResourceLocator(DefaultCheckstyleExecutor.java:852)
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:102)
>   at 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:474)
>   at 
> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:156)
>   at 
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
>   at 
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
>   at 
>

[jira] [Comment Edited] (MCHECKSTYLE-287) checkstyle report throws NPE

2017-06-24 Thread Ed Randall (JIRA) 

[ 
https://issues.apache.org/jira/browse/MCHECKSTYLE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062053#comment-16062053
 ] 

Ed Randall edited comment on MCHECKSTYLE-287 at 6/24/17 4:36 PM:
-

Still affects 2.17 Google shows that quite a few users have suffered this 
issue;  Is there any chance we could have a release with the quick tactical fix 
(catch NullPointerException in the offending Artifact loop) so we can run 'mvn 
site' on a multimodule project without having to figure out tedious workarounds?
You guys can then continue to research the root cause... it's been going on too 
long.  Thanks!


was (Author: edrandall):
Google shows that quite a few users have suffered this issue;  Is there any 
chance we could have a release with the quick tactical fix (catch 
NullPointerException in the offending Artifact loop) so we can run 'mvn site' 
on a multimodule project without having to figure out tedious workarounds?
You guys can then continue to research the root cause... it's been going on too 
long.  Thanks!

> checkstyle report throws NPE
> 
>
> Key: MCHECKSTYLE-287
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-287
> Project: Maven Checkstyle Plugin
>  Issue Type: Bug
>Affects Versions: 2.13, 2.14
>Reporter: Thomas Scheffler
> Attachments: patch1.diff, projects.tar.gz
>
>
> I don't know what triggers this bug. Somehow 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.collectArtifacts(String)
>  produces a List which contains the null object. And therefor an exception is 
> thrown here (2.14):
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project 
> oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed. 
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on 
> project oaipmh: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.3:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
>   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:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
>   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:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 19 more
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.configureResourceLocator(DefaultCheckstyleExecutor.java:852)
>   at 
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:102)
>   at 
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:474)
>   at 
>

[jira] [Created] (MSKINS-135) add an option to edit page with Apache CMS

2017-06-24 Thread JIRA 
Hervé Boutemy created MSKINS-135:


 Summary: add an option to edit page with Apache CMS
 Key: MSKINS-135
 URL: https://issues.apache.org/jira/browse/MSKINS-135
 Project: Maven Skins
  Issue Type: New Feature
  Components: Fluido Skin
Affects Versions: fluido-1.6
Reporter: Hervé Boutemy


it would be useful if a link to edit the current page with Apache CMS could be 
configured: this would avoid the need to have CMS bookmarklet 
https://cms.apache.org/#bookmark
ideally even as anonymous user (anonymous users for sure don't know the CMS and 
its bookmarklet)
see Apache CMS reference: https://www.apache.org/dev/cmsref.html




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MSKINS-135) add an option to edit page with Apache CMS

2017-06-24 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/MSKINS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MSKINS-135:
-
Description: 
it would be useful if a link to edit the current page with Apache CMS could be 
configured: this would avoid the need to have CMS bookmarklet 
https://cms.apache.org/#bookmark
ideally even as anonymous user (anonymous users for sure don't know the CMS and 
its bookmarklet)
see Apache CMS reference: https://www.apache.org/dev/cmsref.html
and the bookmarklet: 
javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))


  was:
it would be useful if a link to edit the current page with Apache CMS could be 
configured: this would avoid the need to have CMS bookmarklet 
https://cms.apache.org/#bookmark
ideally even as anonymous user (anonymous users for sure don't know the CMS and 
its bookmarklet)
see Apache CMS reference: https://www.apache.org/dev/cmsref.html



> add an option to edit page with Apache CMS
> --
>
> Key: MSKINS-135
> URL: https://issues.apache.org/jira/browse/MSKINS-135
> Project: Maven Skins
>  Issue Type: New Feature
>  Components: Fluido Skin
>Affects Versions: fluido-1.6
>Reporter: Hervé Boutemy
>
> it would be useful if a link to edit the current page with Apache CMS could 
> be configured: this would avoid the need to have CMS bookmarklet 
> https://cms.apache.org/#bookmark
> ideally even as anonymous user (anonymous users for sure don't know the CMS 
> and its bookmarklet)
> see Apache CMS reference: https://www.apache.org/dev/cmsref.html
> and the bookmarklet: 
> javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)