[jira] [Updated] (MNG-6374) ModelBuilder hangs with malformed pom.xml

[Rohan Padhye (JIRA)]

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

Rohan Padhye updated MNG-6374:
--
Affects Version/s: (was: 3.5.0)
   3.5.3
 Priority: Major  (was: Minor)
  Description: 
Maven hangs when provided with a malformed pom.xml file that contains a 
question mark in a tag name.

Minimal example for a pom.xml: 
{noformat}
{noformat}
 
 Running {{mvn}} results in the output:
{noformat}
[INFO] Scanning for projects...{noformat}
  
 And is stuck there forever, instead of providing an error message.

I found this issue using [JQF|https://github.com/rohanpadhye/jqf].

  was:
Maven's build hangs when provided with a malformed pom.xml file that contains a 
question mark in a tag name.

Minimal example for a pom.xml: 
{noformat}
{noformat}
 
Running {{mvn}} results in the output:

{noformat}
[INFO] Scanning for projects...{noformat}
  
And is stuck there forever, instead of providing an error message.

I found this issue with JQF.

  Component/s: (was: Bootstrap & Build)
   POM

> ModelBuilder hangs with malformed pom.xml
> -
>
> Key: MNG-6374
> URL: https://issues.apache.org/jira/browse/MNG-6374
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.5.2, 3.5.3
>Reporter: Rohan Padhye
>Priority: Major
>
> Maven hangs when provided with a malformed pom.xml file that contains a 
> question mark in a tag name.
> Minimal example for a pom.xml: 
> {noformat}
> {noformat}
>  
>  Running {{mvn}} results in the output:
> {noformat}
> [INFO] Scanning for projects...{noformat}
>   
>  And is stuck there forever, instead of providing an error message.
> I found this issue using [JQF|https://github.com/rohanpadhye/jqf].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MNG-6375) NullPointerException when pom.xml has incomplete XML tag.

[Rohan Padhye (JIRA)]

Rohan Padhye created MNG-6375:
-

 Summary: NullPointerException when pom.xml has incomplete XML tag.
 Key: MNG-6375
 URL: https://issues.apache.org/jira/browse/MNG-6375
 Project: Maven
  Issue Type: Bug
  Components: POM
Affects Versions: 3.5.3, 3.5.2
Reporter: Rohan Padhye


Test case is a pom.xml with an incomplete XML tag. 
{noformat}
$ echo -n " pom.xml # No newlines
$ mvn
org.apache.maven.InternalErrorException: Internal error: 
java.lang.NullPointerException
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:122)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
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: java.lang.NullPointerException
at 
org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:3054)
at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3080)
at 
org.codehaus.plexus.util.xml.pull.MXParser.parseStartTag(MXParser.java:1776)
at 
org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1517)
at 
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1436)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1131)
at 
org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.read(MavenXpp3ReaderEx.java:4399)
at 
org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.read(MavenXpp3ReaderEx.java:598)
at 
org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:105)
at 
org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:82)
at 
org.apache.maven.model.building.DefaultModelProcessor.read(DefaultModelProcessor.java:81)
at 
org.apache.maven.model.building.DefaultModelBuilder.readModel(DefaultModelBuilder.java:535)
at 
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:275)
at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:429)
at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:398)
at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:361)
at 
org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:400)
at 
org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:391)
at 
org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:78)
at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:511)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:221)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at 
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107){noformat}
 

Bug was found automatically by [JQF|https://github.com/rohanpadhye/jqf].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (DOXIASITETOOLS-189) improve html generated for menus

[JIRA]

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

Hervé Boutemy closed DOXIASITETOOLS-189.

Resolution: Fixed

done in 
https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git=commit=c3485f12c234e7bd92af45b9da4d4a3ddf8da81f

> improve html generated for menus
> 
>
> Key: DOXIASITETOOLS-189
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-189
> Project: Maven Doxia Sitetools
>  Issue Type: Improvement
>  Components: Site renderer
>Affects Versions: 1.8
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 1.8.1
>
>
> currently not properly indented
> while doing it for Fluido, doing it for default



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MJMOD-12) Let POM parent do it's work

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MJMOD-12.

Resolution: Fixed

Done in 
[13874cdf5d053e901bcfa77567a00edd950bc59e|https://gitbox.apache.org/repos/asf?p=maven-jmod-plugin.git;a=commitdiff;h=13874cdf5d053e901bcfa77567a00edd950bc59e]

> Let POM parent do it's work
> ---
>
> Key: MJMOD-12
> URL: https://issues.apache.org/jira/browse/MJMOD-12
> Project: Maven JMod Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>
> The following plugins are already defined correctly in the parent:‚
>  * maven-compiler-plugin
>  * maven-invoker-plugin
>  * maven-plugin-plugin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJMOD-12) Let POM parent do it's work

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJMOD-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394645#comment-16394645
 ] 

Hudson commented on MJMOD-12:
-

Build succeeded in Jenkins: Maven TLP » maven-jmod-plugin » master #5

See https://builds.apache.org/job/maven-box/job/maven-jmod-plugin/job/master/5/

> Let POM parent do it's work
> ---
>
> Key: MJMOD-12
> URL: https://issues.apache.org/jira/browse/MJMOD-12
> Project: Maven JMod Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>
> The following plugins are already defined correctly in the parent:‚
>  * maven-compiler-plugin
>  * maven-invoker-plugin
>  * maven-plugin-plugin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MJLINK-14) Let POM parent do it's work

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MJLINK-14.
-
Resolution: Fixed

Done in 
[52a3ee3faede8f4c2f681acd6bac422253772c7d|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=52a3ee3faede8f4c2f681acd6bac422253772c7d]

> Let POM parent do it's work
> ---
>
> Key: MJLINK-14
> URL: https://issues.apache.org/jira/browse/MJLINK-14
> Project: Maven JLink Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>
> Currently several plugin versions are hard coded in the pom after the upgrade 
> we can remove several of them:
>  * maven-compiler-plugin
>  * maven-invoker-plugin
>  * maven-javadoc-plugin
>  * maven-plugin-plugin
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJLINK-14) Let POM parent do it's work

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJLINK-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394642#comment-16394642
 ] 

Hudson commented on MJLINK-14:
--

Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » master #6

See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/master/6/

> Let POM parent do it's work
> ---
>
> Key: MJLINK-14
> URL: https://issues.apache.org/jira/browse/MJLINK-14
> Project: Maven JLink Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>
> Currently several plugin versions are hard coded in the pom after the upgrade 
> we can remove several of them:
>  * maven-compiler-plugin
>  * maven-invoker-plugin
>  * maven-javadoc-plugin
>  * maven-plugin-plugin
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJMOD-12) Let POM parent do it's work

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJMOD-12:
-
Description: 
The following plugins are already defined correctly in the parent:‚
 * maven-compiler-plugin
 * maven-invoker-plugin
 * maven-plugin-plugin

> Let POM parent do it's work
> ---
>
> Key: MJMOD-12
> URL: https://issues.apache.org/jira/browse/MJMOD-12
> Project: Maven JMod Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>
> The following plugins are already defined correctly in the parent:‚
>  * maven-compiler-plugin
>  * maven-invoker-plugin
>  * maven-plugin-plugin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJLINK-4) NPE on execution

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394638#comment-16394638
 ] 

Karl Heinz Marbaise commented on MJLINK-4:
--

Many thanks [~b.eckenfels] for the feedback.

> NPE on execution 
> -
>
> Key: MJLINK-4
> URL: https://issues.apache.org/jira/browse/MJLINK-4
> Project: Maven JLink Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1
> Environment: Ubuntu 16.04.3 LTS
> Linux 4.4.0-93-generic
>Reporter: Johannes Boesl
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0-alpha-2
>
>
> When I try to run my maven build I get the following exception:
> {noformat}[ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink 
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.: 
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink 
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>   at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
>   at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-jlink of goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 11 more
> Caused by: java.lang.NullPointerException
>   at 
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:52)
>   at 
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:48)
>   at 
> org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths(LocationManager.java:109)
>   at 
> org.apache.maven.plugins.jlink.JLinkMojo.preparePaths(JLinkMojo.java:347)
>   at org.apache.maven.plugins.jlink.JLinkMojo.execute(JLinkMojo.java:264)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   ... 12 more{quote}
> {noformat}
> The cause seems to be that the following code in line 337 in JLinkMojo 
> returns a collection with only 'null' entries:
> {{Collection dependencyArtifacts = getCompileClasspathElements( 
> getProject() );}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MJMOD-12) Let POM parent do it's work

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJMOD-12:


 Summary: Let POM parent do it's work
 Key: MJMOD-12
 URL: https://issues.apache.org/jira/browse/MJMOD-12
 Project: Maven JMod Plugin
  Issue Type: Improvement
Affects Versions: 3.0.0-alpha-2
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0-alpha-2






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJLINK-4) NPE on execution

[Bernd Eckenfels (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394636#comment-16394636
 ] 

Bernd Eckenfels commented on MJLINK-4:
--

I can confirm the NPE is gone with 

https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-jlink-plugin/3.0.0-alpha-2-SNAPSHOT/

> NPE on execution 
> -
>
> Key: MJLINK-4
> URL: https://issues.apache.org/jira/browse/MJLINK-4
> Project: Maven JLink Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1
> Environment: Ubuntu 16.04.3 LTS
> Linux 4.4.0-93-generic
>Reporter: Johannes Boesl
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0-alpha-2
>
>
> When I try to run my maven build I get the following exception:
> {noformat}[ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink 
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.: 
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink 
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>   at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
>   at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-jlink of goal 
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   ... 11 more
> Caused by: java.lang.NullPointerException
>   at 
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:52)
>   at 
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:48)
>   at 
> org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths(LocationManager.java:109)
>   at 
> org.apache.maven.plugins.jlink.JLinkMojo.preparePaths(JLinkMojo.java:347)
>   at org.apache.maven.plugins.jlink.JLinkMojo.execute(JLinkMojo.java:264)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   ... 12 more{quote}
> {noformat}
> The cause seems to be that the following code in line 337 in JLinkMojo 
> returns a collection with only 'null' entries:
> {{Collection dependencyArtifacts = getCompileClasspathElements( 
> getProject() );}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJLINK-14) Let POM parent do it's work

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJLINK-14:
--
Description: 
Currently several plugin versions are hard coded in the pom after the upgrade 
we can remove several of them:
 * maven-compiler-plugin
 * maven-invoker-plugin
 * maven-javadoc-plugin
 * maven-plugin-plugin

 

> Let POM parent do it's work
> ---
>
> Key: MJLINK-14
> URL: https://issues.apache.org/jira/browse/MJLINK-14
> Project: Maven JLink Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>
> Currently several plugin versions are hard coded in the pom after the upgrade 
> we can remove several of them:
>  * maven-compiler-plugin
>  * maven-invoker-plugin
>  * maven-javadoc-plugin
>  * maven-plugin-plugin
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MJLINK-14) Let POM parent do it's work

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJLINK-14:
-

 Summary: Let POM parent do it's work
 Key: MJLINK-14
 URL: https://issues.apache.org/jira/browse/MJLINK-14
 Project: Maven JLink Plugin
  Issue Type: Improvement
Affects Versions: 3.0.0-alpha-2
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0-alpha-2






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394625#comment-16394625
 ] 

ASF GitHub Bot commented on MPIR-365:
-

slachiewicz closed pull request #2: MPIR-365 Upgrade keytool-maven-plugin to 1.5
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/2
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/pom.xml b/pom.xml
index 9b7ff0e..d3a991e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -428,7 +428,7 @@ under the License.
 
   org.codehaus.mojo
   keytool-maven-plugin
-  1.0
+  1.5
   
 ${basedir}/target/jetty.jks
 cn=jetty, ou=jetty, L=Unknown, ST=Unknown, o=Apache, 
c=Unknown
@@ -478,7 +478,7 @@ under the License.
 initialize
 
   clean
-  genkey
+  generateKeyPair
 
   
 


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Failed tests on Java 9 due to error with keytool plugin "keytool: not found"
> 
>
> Key: MPIR-365
> URL: https://issues.apache.org/jira/browse/MPIR-365
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0
>
>
> Jenkins build failed with error:
>  Windows:
> {noformat}
> [windows-jdk9] [ERROR] Failed to execute goal 
> org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
> maven-project-info-reports-plugin: Result of cmd.exe /X /C 
> '"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
> ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
> apache -keystore 
> f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
>  -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
> cannot find the path specified.. -> [Help 1]{noformat}
> For linux also:
> {noformat}
> [linux-jdk9] [WARNING] /bin/sh: 1: 
> /usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
> To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
> Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] slachiewicz closed pull request #2: MPIR-365 Upgrade keytool-maven-plugin to 1.5

[GitBox]

slachiewicz closed pull request #2: MPIR-365 Upgrade keytool-maven-plugin to 1.5
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/2
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/pom.xml b/pom.xml
index 9b7ff0e..d3a991e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -428,7 +428,7 @@ under the License.
 
   org.codehaus.mojo
   keytool-maven-plugin
-  1.0
+  1.5
   
 ${basedir}/target/jetty.jks
 cn=jetty, ou=jetty, L=Unknown, ST=Unknown, o=Apache, 
c=Unknown
@@ -478,7 +478,7 @@ under the License.
 initialize
 
   clean
-  genkey
+  generateKeyPair
 
   
 


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394610#comment-16394610
 ] 

ASF GitHub Bot commented on MPIR-365:
-

khmarbaise commented on issue #2: MPIR-365 Upgrade keytool-maven-plugin to 1.5
URL: 
https://github.com/apache/maven-project-info-reports-plugin/pull/2#issuecomment-372140442
 
 
   Patch is integrated and fixed the build. Thanks for the patch. You can close 
now this PR.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Failed tests on Java 9 due to error with keytool plugin "keytool: not found"
> 
>
> Key: MPIR-365
> URL: https://issues.apache.org/jira/browse/MPIR-365
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0
>
>
> Jenkins build failed with error:
>  Windows:
> {noformat}
> [windows-jdk9] [ERROR] Failed to execute goal 
> org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
> maven-project-info-reports-plugin: Result of cmd.exe /X /C 
> '"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
> ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
> apache -keystore 
> f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
>  -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
> cannot find the path specified.. -> [Help 1]{noformat}
> For linux also:
> {noformat}
> [linux-jdk9] [WARNING] /bin/sh: 1: 
> /usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
> To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
> Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] khmarbaise commented on issue #2: MPIR-365 Upgrade keytool-maven-plugin to 1.5

[GitBox]

khmarbaise commented on issue #2: MPIR-365 Upgrade keytool-maven-plugin to 1.5
URL: 
https://github.com/apache/maven-project-info-reports-plugin/pull/2#issuecomment-372140442
 
 
   Patch is integrated and fixed the build. Thanks for the patch. You can close 
now this PR.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Comment Edited] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394609#comment-16394609
 ] 

Karl Heinz Marbaise edited comment on MPIR-365 at 3/11/18 7:06 PM:
---

Done via PR of [~slachiewicz] 
[b7e2ec380ae8e1740dab5e688b8c81af351b212a|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commitdiff;h=b7e2ec380ae8e1740dab5e688b8c81af351b212a]
 Thanks for the patch.


was (Author: khmarbaise):
Done via PR of [~slachiewicz] 
[b7e2ec380ae8e1740dab5e688b8c81af351b212a|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commitdiff;h=b7e2ec380ae8e1740dab5e688b8c81af351b212a]

> Failed tests on Java 9 due to error with keytool plugin "keytool: not found"
> 
>
> Key: MPIR-365
> URL: https://issues.apache.org/jira/browse/MPIR-365
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0
>
>
> Jenkins build failed with error:
>  Windows:
> {noformat}
> [windows-jdk9] [ERROR] Failed to execute goal 
> org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
> maven-project-info-reports-plugin: Result of cmd.exe /X /C 
> '"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
> ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
> apache -keystore 
> f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
>  -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
> cannot find the path specified.. -> [Help 1]{noformat}
> For linux also:
> {noformat}
> [linux-jdk9] [WARNING] /bin/sh: 1: 
> /usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
> To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
> Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MPIR-365.

Resolution: Fixed
  Assignee: Karl Heinz Marbaise

Done via PR of [~slachiewicz] 
[b7e2ec380ae8e1740dab5e688b8c81af351b212a|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commitdiff;h=b7e2ec380ae8e1740dab5e688b8c81af351b212a]

> Failed tests on Java 9 due to error with keytool plugin "keytool: not found"
> 
>
> Key: MPIR-365
> URL: https://issues.apache.org/jira/browse/MPIR-365
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0
>
>
> Jenkins build failed with error:
>  Windows:
> {noformat}
> [windows-jdk9] [ERROR] Failed to execute goal 
> org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
> maven-project-info-reports-plugin: Result of cmd.exe /X /C 
> '"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
> ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
> apache -keystore 
> f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
>  -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
> cannot find the path specified.. -> [Help 1]{noformat}
> For linux also:
> {noformat}
> [linux-jdk9] [WARNING] /bin/sh: 1: 
> /usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
> To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
> Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MPIR-365:
-
Fix Version/s: 3.0

> Failed tests on Java 9 due to error with keytool plugin "keytool: not found"
> 
>
> Key: MPIR-365
> URL: https://issues.apache.org/jira/browse/MPIR-365
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 3.0
>
>
> Jenkins build failed with error:
>  Windows:
> {noformat}
> [windows-jdk9] [ERROR] Failed to execute goal 
> org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
> maven-project-info-reports-plugin: Result of cmd.exe /X /C 
> '"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
> ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
> apache -keystore 
> f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
>  -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
> cannot find the path specified.. -> [Help 1]{noformat}
> For linux also:
> {noformat}
> [linux-jdk9] [WARNING] /bin/sh: 1: 
> /usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
> To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
> Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394605#comment-16394605
 ] 

Hudson commented on MPIR-365:
-

Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » 
master #5

See 
https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/5/

> Failed tests on Java 9 due to error with keytool plugin "keytool: not found"
> 
>
> Key: MPIR-365
> URL: https://issues.apache.org/jira/browse/MPIR-365
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Sylwester Lachiewicz
>Priority: Minor
>
> Jenkins build failed with error:
>  Windows:
> {noformat}
> [windows-jdk9] [ERROR] Failed to execute goal 
> org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
> maven-project-info-reports-plugin: Result of cmd.exe /X /C 
> '"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
> ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
> apache -keystore 
> f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
>  -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
> cannot find the path specified.. -> [Help 1]{noformat}
> For linux also:
> {noformat}
> [linux-jdk9] [WARNING] /bin/sh: 1: 
> /usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
> To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
> Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (DOXIASITETOOLS-189) improve html generated for menus

[JIRA]

Hervé Boutemy created DOXIASITETOOLS-189:


 Summary: improve html generated for menus
 Key: DOXIASITETOOLS-189
 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-189
 Project: Maven Doxia Sitetools
  Issue Type: Improvement
  Components: Site renderer
Affects Versions: 1.8
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
 Fix For: 1.8.1


currently not properly indented

while doing it for Fluido, doing it for default



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSKINS-142) indent html for sub-menus

[JIRA]

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

Hervé Boutemy closed MSKINS-142.

Resolution: Fixed

done in 
https://gitbox.apache.org/repos/asf?p=maven-fluido-skin.git=commit=7bd5f8bcefa3147eddccdf41db657e9f86fbdaca

> indent html for sub-menus
> -
>
> Key: MSKINS-142
> URL: https://issues.apache.org/jira/browse/MSKINS-142
> Project: Maven Skins
>  Issue Type: Improvement
>  Components: Fluido Skin
>Affects Versions: fluido-1.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: fluido-1.8
>
>
> currently, when there are sub-menus, html code is not indented: you can't see 
> easily in html source code
> and in addition,  and  are on multiple lines
>  
> improving generated html can help working on skin improvements



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSKINS-142) indent html for sub-menus

[Hudson (JIRA)]

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

Hudson commented on MSKINS-142:
---

Build succeeded in Jenkins: Maven TLP » maven-fluido-skin » master #15

See https://builds.apache.org/job/maven-box/job/maven-fluido-skin/job/master/15/

> indent html for sub-menus
> -
>
> Key: MSKINS-142
> URL: https://issues.apache.org/jira/browse/MSKINS-142
> Project: Maven Skins
>  Issue Type: Improvement
>  Components: Fluido Skin
>Affects Versions: fluido-1.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: fluido-1.8
>
>
> currently, when there are sub-menus, html code is not indented: you can't see 
> easily in html source code
> and in addition,  and  are on multiple lines
>  
> improving generated html can help working on skin improvements



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSKINS-142) indent html for sub-menus

[JIRA]

Hervé Boutemy created MSKINS-142:


 Summary: indent html for sub-menus
 Key: MSKINS-142
 URL: https://issues.apache.org/jira/browse/MSKINS-142
 Project: Maven Skins
  Issue Type: Improvement
  Components: Fluido Skin
Affects Versions: fluido-1.7
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
 Fix For: fluido-1.8


currently, when there are sub-menus, html code is not indented: you can't see 
easily in html source code

and in addition,  and  are on multiple lines

 

improving generated html can help working on skin improvements



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] slachiewicz opened a new pull request #3: Small link corrections

[GitBox]

slachiewicz opened a new pull request #3: Small link corrections
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/3
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MPIR-361) Upgrade parent to 31

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394561#comment-16394561
 ] 

ASF GitHub Bot commented on MPIR-361:
-

slachiewicz commented on issue #1: [MPIR-361] Fix checkstyle errors after 
chekstyle update
URL: 
https://github.com/apache/maven-project-info-reports-plugin/pull/1#issuecomment-372128441
 
 
   With upgrade of keytool plugin, looks like problem is partialy resolved 
[MPIR-365](https://issues.apache.org/jira/browse/MPIR-365)
#2 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Upgrade parent to 31
> 
>
> Key: MPIR-361
> URL: https://issues.apache.org/jira/browse/MPIR-361
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 2.10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 2.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] slachiewicz commented on issue #1: [MPIR-361] Fix checkstyle errors after chekstyle update

[GitBox]

slachiewicz commented on issue #1: [MPIR-361] Fix checkstyle errors after 
chekstyle update
URL: 
https://github.com/apache/maven-project-info-reports-plugin/pull/1#issuecomment-372128441
 
 
   With upgrade of keytool plugin, looks like problem is partialy resolved 
[MPIR-365](https://issues.apache.org/jira/browse/MPIR-365)
#2 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394559#comment-16394559
 ] 

ASF GitHub Bot commented on MPIR-365:
-

slachiewicz opened a new pull request #2: MPIR-365 Upgrade keytool-maven-plugin 
to 1.5
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/2
 
 
   Fixes problem with keytool run for Java 9 on Windows/Linux


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Failed tests on Java 9 due to error with keytool plugin "keytool: not found"
> 
>
> Key: MPIR-365
> URL: https://issues.apache.org/jira/browse/MPIR-365
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Sylwester Lachiewicz
>Priority: Minor
>
> Jenkins build failed with error:
>  Windows:
> {noformat}
> [windows-jdk9] [ERROR] Failed to execute goal 
> org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
> maven-project-info-reports-plugin: Result of cmd.exe /X /C 
> '"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
> ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
> apache -keystore 
> f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
>  -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
> cannot find the path specified.. -> [Help 1]{noformat}
> For linux also:
> {noformat}
> [linux-jdk9] [WARNING] /bin/sh: 1: 
> /usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
> To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
> Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] slachiewicz opened a new pull request #2: MPIR-365 Upgrade keytool-maven-plugin to 1.5

[GitBox]

slachiewicz opened a new pull request #2: MPIR-365 Upgrade keytool-maven-plugin 
to 1.5
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/2
 
 
   Fixes problem with keytool run for Java 9 on Windows/Linux


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (MPIR-365) Failed tests on Java 9 due to error with keytool plugin "keytool: not found"

[Sylwester Lachiewicz (JIRA)]

Sylwester Lachiewicz created MPIR-365:
-

 Summary: Failed tests on Java 9 due to error with keytool plugin 
"keytool: not found"
 Key: MPIR-365
 URL: https://issues.apache.org/jira/browse/MPIR-365
 Project: Maven Project Info Reports Plugin
  Issue Type: Bug
Affects Versions: 2.10
Reporter: Sylwester Lachiewicz


Jenkins build failed with error:
 Windows:
{noformat}
[windows-jdk9] [ERROR] Failed to execute goal 
org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
maven-project-info-reports-plugin: Result of cmd.exe /X /C 
'"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
apache -keystore 
f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
 -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
cannot find the path specified.. -> [Help 1]{noformat}
For linux also:
{noformat}
[linux-jdk9] [WARNING] /bin/sh: 1: 
/usr/local/asfpackages/java/jdk-9.0.1/../bin/keytool: not found{noformat}
To resolve problem - upgrade to keytool-maven-plugin:1.5 - tested on 
Windows/Jdk9



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without updateing any pom

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394549#comment-16394549
 ] 

ASF GitHub Bot commented on MENFORCER-142:
--

HongkaiWen commented on issue #31: MENFORCER-142 Initial poc implementation of 
adding rules from cmdline (WIP)
URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-372125616
 
 
   this is really a great job!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Specify enforcer rule in command line without updateing any pom
> ---
>
> Key: MENFORCER-142
> URL: https://issues.apache.org/jira/browse/MENFORCER-142
> Project: Maven Enforcer Plugin
>  Issue Type: Improvement
>  Components: Plugin
>Reporter: Arnaud Bourrée
>Priority: Major
> Fix For: more-investigation
>
>
> Hello,
> How could we specify enforcer:enforce rules from command line?
> I want to run command line like following without updating any pom.xml:
> mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom
> The goal of this enforcer:enforce rule is to check that Acme's
> developers write pom.xml which inherit from acme's parent pom.xml
> And because they may not inherit from acme's parent pom.xml, I cannot
> specify enforcer rule in.
> Regards,
> Arnaud.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] HongkaiWen commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP)

[GitBox]

HongkaiWen commented on issue #31: MENFORCER-142 Initial poc implementation of 
adding rules from cmdline (WIP)
URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-372125616
 
 
   this is really a great job!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Closed] (SCM-804) Expand SVN's useCygwinPath to all commands needed by release plugin

[Michael Osipov (JIRA)]

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

Michael Osipov closed SCM-804.
--
Resolution: Won't Fix

> Expand SVN's useCygwinPath to all commands needed by release plugin
> ---
>
> Key: SCM-804
> URL: https://issues.apache.org/jira/browse/SCM-804
> Project: Maven SCM
>  Issue Type: Improvement
>  Components: maven-scm-provider-svn
>Reporter: Eric Pederson
>Priority: Minor
>
> As mentioned in SCM-213, the Maven release plugin breaks when using Cygwin's 
> {{svn}}.  There is a workaround to use a Windows Subversion client instead.  
> Since the documentation lists {{useCygwinPath}} as an option it would be good 
> if it worked everywhere.  I checked the source and {{useCygwinPath}} only 
> appears to be used in the Update command.  Either the docs should clarify 
> where it can be used or (ideally) it could be used for Commit and Checkout 
> too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1495) Encoding of TXT report file should be configured by ${project.reporting.outputEncoding} and MOJO parameter encoding

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1495:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/176
  
@eolivelli 
done. I did git commit amend so you have to clone the repo again.


> Encoding of TXT report file should be configured by 
> ${project.reporting.outputEncoding} and MOJO parameter encoding
> ---
>
> Key: SUREFIRE-1495
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1495
> Project: Maven Surefire
>  Issue Type: New Feature
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] the integration test {{UnicodeTestNamesIT}} 
> fails due to Japanese encoding.
> The entire problem is with using only system file encoding in Surefire TXT 
> report files in {{target/surefire-reports}}, similar with Failsafe.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/eddec1bf40f900f07be67be9e79e686654fd6ec44c672a4ae58d4650@%3Cdev.maven.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #176: [SUREFIRE-1495] Encoding of TXT report file shoul...

[Tibor17]

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/176
  
@eolivelli 
done. I did git commit amend so you have to clone the repo again.


---

[GitHub] maven-archetype issue #17: Fix spelling of rigorous

[hboutemy]

Github user hboutemy commented on the issue:

https://github.com/apache/maven-archetype/pull/17
  
merged
thank you


---

[GitHub] maven-archetype issue #21: fixed typo repsoitory

[hboutemy]

Github user hboutemy commented on the issue:

https://github.com/apache/maven-archetype/pull/21
  
merged, thank you


---

[jira] [Commented] (SCM-804) Expand SVN's useCygwinPath to all commands needed by release plugin

[Eric Pederson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SCM-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394489#comment-16394489
 ] 

Eric Pederson commented on SCM-804:
---

I’m at another job now and that doesn’t use maven. You can close this.
Thanks.

On Sat, Mar 10, 2018 at 6:26 PM Michael Osipov (JIRA) 

-- 
Sent from Gmail Mobile


> Expand SVN's useCygwinPath to all commands needed by release plugin
> ---
>
> Key: SCM-804
> URL: https://issues.apache.org/jira/browse/SCM-804
> Project: Maven SCM
>  Issue Type: Improvement
>  Components: maven-scm-provider-svn
>Reporter: Eric Pederson
>Priority: Minor
>
> As mentioned in SCM-213, the Maven release plugin breaks when using Cygwin's 
> {{svn}}.  There is a workaround to use a Windows Subversion client instead.  
> Since the documentation lists {{useCygwinPath}} as an option it would be good 
> if it worked everywhere.  I checked the source and {{useCygwinPath}} only 
> appears to be used in the Update command.  Either the docs should clarify 
> where it can be used or (ideally) it could be used for Commit and Checkout 
> too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (DOXIASITETOOLS-188) add parent menu items in breadcrumbs

[JIRA]

Hervé Boutemy created DOXIASITETOOLS-188:


 Summary: add parent menu items in breadcrumbs
 Key: DOXIASITETOOLS-188
 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-188
 Project: Maven Doxia Sitetools
  Issue Type: Task
  Components: Site renderer
Affects Versions: 1.8
Reporter: Hervé Boutemy


site rendering is able to highlight menu entries in left menu: see 
[http://maven.apache.org/developers/website/website-overview.html]

on this example, the document menu entry is "Complete Overview", which is part 
of "Deploy Maven Website", which is part of "Maven Developer Center"

it would be nice to have these intermediate menu entries displayed as 
breadcrumd also: Apache/ Maven/ Maven Developer Center/ Deploy Maven Website/ 
Deploy Maven Website

 

(notice that the document title in this case is not well chosen: should be 
changed...)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (DOXIASITETOOLS-188) add parent menu items in breadcrumbs

[JIRA]

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

Hervé Boutemy updated DOXIASITETOOLS-188:
-
Issue Type: New Feature  (was: Task)

> add parent menu items in breadcrumbs
> 
>
> Key: DOXIASITETOOLS-188
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-188
> Project: Maven Doxia Sitetools
>  Issue Type: New Feature
>  Components: Site renderer
>Affects Versions: 1.8
>Reporter: Hervé Boutemy
>Priority: Major
>
> site rendering is able to highlight menu entries in left menu: see 
> [http://maven.apache.org/developers/website/website-overview.html]
> on this example, the document menu entry is "Complete Overview", which is 
> part of "Deploy Maven Website", which is part of "Maven Developer Center"
> it would be nice to have these intermediate menu entries displayed as 
> breadcrumd also: Apache/ Maven/ Maven Developer Center/ Deploy Maven Website/ 
> Deploy Maven Website
>  
> (notice that the document title in this case is not well chosen: should be 
> changed...)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1498) Surefire prints own logs "Couldn't load group class" to native stream.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1498:
--

Github user eolivelli commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
@Tibor17 I will be happy to pick up this issue and continue the work. I am 
an user of the feature. I will continue the work as soon as I have time


> Surefire prints own logs "Couldn't load group class" to native stream.
> --
>
> Key: SUREFIRE-1498
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1498
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] surefire prints error logs [2] to the 
> native stdout.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/1743a7da6e4ce4a51074f22b4f380dbc3c4462bb563777c08ccf0671@%3Cdev.maven.apache.org%3E
> [2]: [WARNING] Couldn't load group class 'MinimumAcceptance' in
> Surefire|Failsafe plugin. The group class is ignored!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #177: [SUREFIRE-1498] Surefire prints own logs "Couldn'...

[eolivelli]

Github user eolivelli commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
@Tibor17 I will be happy to pick up this issue and continue the work. I am 
an user of the feature. I will continue the work as soon as I have time


---

[GitHub] maven-surefire issue #177: [SUREFIRE-1498] Surefire prints own logs "Couldn'...

[Tibor17]

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
Maybe not necessary to test it again because I downloaded logs from our 
Jenkins ans I see the IT
JUnit48TestCategoriesIT_testBadCategoryForkAlways
which has the Warning message in log.txt and not in the *.dump stream.
[INFO] 
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[WARNING] Couldn't load group class 'BadCategory' in Surefire|Failsafe 
plugin. The group class is ignored!
[WARNING] Couldn't load group class 'BadCategory' in Surefire|Failsafe 
plugin. The group class is ignored!
[WARNING] Couldn't load group class 'BadCategory' in Surefire|Failsafe 
plugin. The group class is ignored!
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0



---

[jira] [Commented] (SUREFIRE-1498) Surefire prints own logs "Couldn't load group class" to native stream.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1498:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
Maybe not necessary to test it again because I downloaded logs from our 
Jenkins ans I see the IT
JUnit48TestCategoriesIT_testBadCategoryForkAlways
which has the Warning message in log.txt and not in the *.dump stream.
[INFO] 
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[WARNING] Couldn't load group class 'BadCategory' in Surefire|Failsafe 
plugin. The group class is ignored!
[WARNING] Couldn't load group class 'BadCategory' in Surefire|Failsafe 
plugin. The group class is ignored!
[WARNING] Couldn't load group class 'BadCategory' in Surefire|Failsafe 
plugin. The group class is ignored!
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0



> Surefire prints own logs "Couldn't load group class" to native stream.
> --
>
> Key: SUREFIRE-1498
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1498
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] surefire prints error logs [2] to the 
> native stdout.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/1743a7da6e4ce4a51074f22b4f380dbc3c4462bb563777c08ccf0671@%3Cdev.maven.apache.org%3E
> [2]: [WARNING] Couldn't load group class 'MinimumAcceptance' in
> Surefire|Failsafe plugin. The group class is ignored!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-345) Upgrade to Doxia 1.7

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394465#comment-16394465
 ] 

Michael Osipov commented on MPIR-345:
-

That's correct. Maybe some combined update is necessary. This is a needle in 
the haystack.

> Upgrade to Doxia 1.7
> 
>
> Key: MPIR-345
> URL: https://issues.apache.org/jira/browse/MPIR-345
> Project: Maven Project Info Reports Plugin
>  Issue Type: Task
>Affects Versions: 2.9
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 2.10
>
> Attachments: 1.7.log, MPIR-345.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1498) Surefire prints own logs "Couldn't load group class" to native stream.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1498:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
@eolivelli 
Pls check it our with your code. The log should not appear in the dump file.


> Surefire prints own logs "Couldn't load group class" to native stream.
> --
>
> Key: SUREFIRE-1498
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1498
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] surefire prints error logs [2] to the 
> native stdout.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/1743a7da6e4ce4a51074f22b4f380dbc3c4462bb563777c08ccf0671@%3Cdev.maven.apache.org%3E
> [2]: [WARNING] Couldn't load group class 'MinimumAcceptance' in
> Surefire|Failsafe plugin. The group class is ignored!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #177: [SUREFIRE-1498] Surefire prints own logs "Couldn'...

[Tibor17]

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
@eolivelli 
Pls check it our with your code. The log should not appear in the dump file.


---

[jira] [Commented] (SUREFIRE-1498) Surefire prints own logs "Couldn't load group class" to native stream.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1498:
--

Github user eolivelli commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
I think that in "Branch Sources" you have to enable GitHub and work with 
"iscover pull requests from forks" options.
It is a kind of Jenkins Job I have never used.

Usually I setup jobs like this, using "GitHub Pull Request Builder"
https://builds.apache.org/job/bookkeeper_precommit_pullrequest_java8/


> Surefire prints own logs "Couldn't load group class" to native stream.
> --
>
> Key: SUREFIRE-1498
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1498
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] surefire prints error logs [2] to the 
> native stdout.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/1743a7da6e4ce4a51074f22b4f380dbc3c4462bb563777c08ccf0671@%3Cdev.maven.apache.org%3E
> [2]: [WARNING] Couldn't load group class 'MinimumAcceptance' in
> Surefire|Failsafe plugin. The group class is ignored!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #177: [SUREFIRE-1498] Surefire prints own logs "Couldn'...

[eolivelli]

Github user eolivelli commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
I think that in "Branch Sources" you have to enable GitHub and work with 
"iscover pull requests from forks" options.
It is a kind of Jenkins Job I have never used.

Usually I setup jobs like this, using "GitHub Pull Request Builder"
https://builds.apache.org/job/bookkeeper_precommit_pullrequest_java8/


---

[jira] [Commented] (SUREFIRE-1498) Surefire prints own logs "Couldn't load group class" to native stream.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1498:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
@eolivelli 
If you know how to do it in CI, just tell me.
You can see CI Mulibranch Pipeline in 
https://builds.apache.org/job/maven-wip/job/maven-surefire/


> Surefire prints own logs "Couldn't load group class" to native stream.
> --
>
> Key: SUREFIRE-1498
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1498
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] surefire prints error logs [2] to the 
> native stdout.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/1743a7da6e4ce4a51074f22b4f380dbc3c4462bb563777c08ccf0671@%3Cdev.maven.apache.org%3E
> [2]: [WARNING] Couldn't load group class 'MinimumAcceptance' in
> Surefire|Failsafe plugin. The group class is ignored!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire issue #177: [SUREFIRE-1498] Surefire prints own logs "Couldn'...

[Tibor17]

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/177
  
@eolivelli 
If you know how to do it in CI, just tell me.
You can see CI Mulibranch Pipeline in 
https://builds.apache.org/job/maven-wip/job/maven-surefire/


---

[jira] [Commented] (SUREFIRE-1495) Encoding of TXT report file should be configured by ${project.reporting.outputEncoding} and MOJO parameter encoding

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1495:
--

Github user eolivelli commented on a diff in the pull request:

https://github.com/apache/maven-surefire/pull/176#discussion_r173648023
  
--- Diff: 
surefire-its/src/test/java/org/apache/maven/surefire/its/fixture/HelperAssertions.java
 ---
@@ -171,4 +172,9 @@ public static void assumeJavaVersion( double 
expectedVersion )
 assumeTrue( "java.specification.version: " + thisVersion,
 Double.valueOf( thisVersion ) >= expectedVersion );
 }
+
+public static String toUTF8( String unicode )
--- End diff --

maybe the name is not explaining the purpose of the function


> Encoding of TXT report file should be configured by 
> ${project.reporting.outputEncoding} and MOJO parameter encoding
> ---
>
> Key: SUREFIRE-1495
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1495
> Project: Maven Surefire
>  Issue Type: New Feature
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] the integration test {{UnicodeTestNamesIT}} 
> fails due to Japanese encoding.
> The entire problem is with using only system file encoding in Surefire TXT 
> report files in {{target/surefire-reports}}, similar with Failsafe.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/eddec1bf40f900f07be67be9e79e686654fd6ec44c672a4ae58d4650@%3Cdev.maven.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1495) Encoding of TXT report file should be configured by ${project.reporting.outputEncoding} and MOJO parameter encoding

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1495:
--

Github user eolivelli commented on a diff in the pull request:

https://github.com/apache/maven-surefire/pull/176#discussion_r173648002
  
--- Diff: 
surefire-its/src/test/java/org/apache/maven/surefire/its/UnicodeTestNamesIT.java
 ---
@@ -62,14 +65,13 @@ public void checkFileNamesWithUnicode()
 unpacked.executeTest()
 .assertTestSuiteResults( 2, 0, 0, 0 );
 
-TestFile surefireReportFile = 
outputValidator.getSurefireReportsFile( TXT_REPORT );
+TestFile surefireReportFile = 
outputValidator.getSurefireReportsFile( TXT_REPORT, UTF_8 );
 assertTrue( surefireReportFile.exists() );
-surefireReportFile.assertContainsText( 
"junit.twoTestCases.Test" );
+surefireReportFile.assertContainsText( toUTF8( REPORT_FILE_CONTENT 
) );
--- End diff --

@Tibor17 isnt's obvious that
toUTF8( REPORT_FILE_CONTENT ) not equals(REPORT_FILE_CONTENT)

IMHO we could write a comment to explain why this toUTF8 is needed, or add a
assertNotEquals(REPORT_FILE_CONTENT, toUTF8( REPORT_FILE_CONTENT ))


> Encoding of TXT report file should be configured by 
> ${project.reporting.outputEncoding} and MOJO parameter encoding
> ---
>
> Key: SUREFIRE-1495
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1495
> Project: Maven Surefire
>  Issue Type: New Feature
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> According to the release vote [1] the integration test {{UnicodeTestNamesIT}} 
> fails due to Japanese encoding.
> The entire problem is with using only system file encoding in Surefire TXT 
> report files in {{target/surefire-reports}}, similar with Failsafe.
> [1]: [VOTE] Release Apache Maven Surefire Plugin version 2.21.0
> https://lists.apache.org/thread.html/eddec1bf40f900f07be67be9e79e686654fd6ec44c672a4ae58d4650@%3Cdev.maven.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-surefire pull request #176: [SUREFIRE-1495] Encoding of TXT report fil...

[eolivelli]

Github user eolivelli commented on a diff in the pull request:

https://github.com/apache/maven-surefire/pull/176#discussion_r173648023
  
--- Diff: 
surefire-its/src/test/java/org/apache/maven/surefire/its/fixture/HelperAssertions.java
 ---
@@ -171,4 +172,9 @@ public static void assumeJavaVersion( double 
expectedVersion )
 assumeTrue( "java.specification.version: " + thisVersion,
 Double.valueOf( thisVersion ) >= expectedVersion );
 }
+
+public static String toUTF8( String unicode )
--- End diff --

maybe the name is not explaining the purpose of the function


---

[GitHub] maven-surefire pull request #176: [SUREFIRE-1495] Encoding of TXT report fil...

[eolivelli]

Github user eolivelli commented on a diff in the pull request:

https://github.com/apache/maven-surefire/pull/176#discussion_r173648002
  
--- Diff: 
surefire-its/src/test/java/org/apache/maven/surefire/its/UnicodeTestNamesIT.java
 ---
@@ -62,14 +65,13 @@ public void checkFileNamesWithUnicode()
 unpacked.executeTest()
 .assertTestSuiteResults( 2, 0, 0, 0 );
 
-TestFile surefireReportFile = 
outputValidator.getSurefireReportsFile( TXT_REPORT );
+TestFile surefireReportFile = 
outputValidator.getSurefireReportsFile( TXT_REPORT, UTF_8 );
 assertTrue( surefireReportFile.exists() );
-surefireReportFile.assertContainsText( 
"junit.twoTestCases.Test" );
+surefireReportFile.assertContainsText( toUTF8( REPORT_FILE_CONTENT 
) );
--- End diff --

@Tibor17 isnt's obvious that
toUTF8( REPORT_FILE_CONTENT ) not equals(REPORT_FILE_CONTENT)

IMHO we could write a comment to explain why this toUTF8 is needed, or add a
assertNotEquals(REPORT_FILE_CONTENT, toUTF8( REPORT_FILE_CONTENT ))


---

[jira] [Commented] (MPIR-363) Update dependences to latest versions (before 3.x)

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394456#comment-16394456
 ] 

Karl Heinz Marbaise commented on MPIR-363:
--

Hi, could we do such discussions on the dev list or via dev chat ? Apart from 
that I would start with the current failing build...

> Update dependences to latest versions (before 3.x)
> --
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Reporter: Sylwester Lachiewicz
>Priority: Major
>
> {code}
> The following plugin updates are available:
> maven-changes-plugin ... 2.11 -> 2.12.1
> maven-jarsigner-plugin ... 1.3.2 -> 1.4
> org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5
> The following dependencies in Dependency Management have newer versions:
> org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1
> org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1
> The following dependencies in Dependencies have newer versions:
> commons-validator:commons-validator . 1.5.1 -> 1.6
> httpunit:httpunit ... 1.6 -> 1.6.1
> junit:junit  3.8.2 -> 4.12
> org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3
> org.apache.maven:maven-model .. 2.2.1 -> 3.5.3
> org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3
> org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2
> org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3
> org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3
> org.apache.maven.doxia:doxia-core . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8
> org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8
> org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 3.3.0
> org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0
> org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1
> org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1
> org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0
> org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 1.7.1
> org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0
> The following dependencies in pluginManagement of plugins have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.apache.maven.shared:maven-shared-resources  1 -> 2
> The following dependencies in Plugin Dependencies have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MPIR-363) Update dependences to latest versions (before 3.x)

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MPIR-363:
-
Description: 
{code}
The following plugin updates are available:
maven-changes-plugin ... 2.11 -> 2.12.1
maven-jarsigner-plugin ... 1.3.2 -> 1.4
org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5

The following dependencies in Dependency Management have newer versions:
org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1
org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1

The following dependencies in Dependencies have newer versions:
commons-validator:commons-validator . 1.5.1 -> 1.6
httpunit:httpunit ... 1.6 -> 1.6.1
junit:junit  3.8.2 -> 4.12
org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3
org.apache.maven:maven-model .. 2.2.1 -> 3.5.3
org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3
org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2
org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3
org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3
org.apache.maven.doxia:doxia-core . 1.6 -> 1.8
org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8
org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8
org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8
org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8
org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 3.3.0
org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0
org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1
org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1
org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0
org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0
org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0
org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0
org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 1.7.1
org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0

The following dependencies in pluginManagement of plugins have newer versions:
org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
org.apache.maven.shared:maven-shared-resources  1 -> 2

The following dependencies in Plugin Dependencies have newer versions:
org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7
{code}

  was:
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
 {{org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1}}
 {{org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
 {{commons-validator:commons-validator . 1.5.1 -> 1.6}}
 {{httpunit:httpunit ... 1.6 -> 1.6.1}}
 {{junit:junit  3.8.2 -> 4.12}}
 {{org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
 {{org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
 {{org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 
3.3.0}}
 {{org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
 {{org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
 {{org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
 {{org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
 {{org.apache.maven.wagon:wagon-http-lightweight 

[jira] [Commented] (MPIR-364) Update plexus-container-default to 1.7.1 causes tests with maven-plugin-testing-harness 1.3 to fail

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394451#comment-16394451
 ] 

Karl Heinz Marbaise commented on MPIR-364:
--

Just try to update the maven-plugin-testing-harness to 2.1 first and then try 
to update of plexus-container...

> Update plexus-container-default to 1.7.1 causes tests with 
> maven-plugin-testing-harness 1.3 to fail
> ---
>
> Key: MPIR-364
> URL: https://issues.apache.org/jira/browse/MPIR-364
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Priority: Major
>
> When testing update to Doxia 1.7/1.8 i got issue.with Plexus
> To reproduce error - change version of _plexus-container-default_ to 1.7.1
> {code}
> Running org.apache.maven.report.projectinfo.CiManagementReportTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.955 sec <<< 
> FAILURE! - in org.apache.maven.report.projectinfo.CiManagementReportTest
> testReport(org.apache.maven.report.projectinfo.CiManagementReportTest) Time 
> elapsed: 0.684 sec <<< ERROR!
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository
>  role: org.apache.maven.plugin.Mojo
>  roleHint: 
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.10-SNAPSHOT:cim
> classRealm: none specified
>  at 
> org.codehaus.plexus.DefaultComponentRegistry.getComponentManager(DefaultComponentRegistry.java:435)
>  at 
> org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:353)
>  at 
> org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178)
>  at 
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:378)
>  at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:205)
>  at 
> org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:203)
>  at 
> org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:133)
>  at 
> org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.createReportMojo(AbstractProjectInfoTestCase.java:188)
>  at 
> org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.generateReport(AbstractProjectInfoTestCase.java:181)
>  at 
> org.apache.maven.report.projectinfo.CiManagementReportTest.testReport(CiManagementReportTest.java:51)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-363) Update dependences to latest versions (before 3.x)

[Sylwester Lachiewicz (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394452#comment-16394452
 ] 

Sylwester Lachiewicz commented on MPIR-363:
---

Yes, lets keep this as a discussion and decide what plugins needs to be updated 
to which version then i will prepare PR for each update. 

Bloker is MPIR-364 and I dont know how to fix this

> Update dependences to latest versions (before 3.x)
> --
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Reporter: Sylwester Lachiewicz
>Priority: Major
>
> {{The following plugin updates are available:}}
>  {{maven-changes-plugin ... 2.11 -> 2.12.1}}
>  {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
>  {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}
> {{The following dependencies in Dependency Management have newer versions:}}
>  {{org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1}}
>  {{org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}
> {{The following dependencies in Dependencies have newer versions:}}
>  {{commons-validator:commons-validator . 1.5.1 -> 1.6}}
>  {{httpunit:httpunit ... 1.6 -> 1.6.1}}
>  {{junit:junit  3.8.2 -> 4.12}}
>  {{org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
>  {{org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
>  {{org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
>  {{org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 
> 3.3.0}}
>  {{org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
>  {{org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
>  {{org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
>  {{org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
>  {{org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 
> 1.7.1}}
>  {{org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}
> {{The following dependencies in pluginManagement of plugins have newer 
> versions:}}
>  {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
>  {{org.apache.maven.shared:maven-shared-resources  1 -> 2}}
> {{The following dependencies in Plugin Dependencies have newer versions:}}
>  {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
>  {{org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MPIR-364) Update plexus-container-default to 1.7.1 causes tests with maven-plugin-testing-harness 1.3 to fail

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MPIR-364:
-
Description: 
When testing update to Doxia 1.7/1.8 i got issue.with Plexus

To reproduce error - change version of _plexus-container-default_ to 1.7.1

{code}
Running org.apache.maven.report.projectinfo.CiManagementReportTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.955 sec <<< 
FAILURE! - in org.apache.maven.report.projectinfo.CiManagementReportTest
testReport(org.apache.maven.report.projectinfo.CiManagementReportTest) Time 
elapsed: 0.684 sec <<< ERROR!
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component repository
 role: org.apache.maven.plugin.Mojo
 roleHint: 
org.apache.maven.plugins:maven-project-info-reports-plugin:2.10-SNAPSHOT:cim
classRealm: none specified
 at 
org.codehaus.plexus.DefaultComponentRegistry.getComponentManager(DefaultComponentRegistry.java:435)
 at 
org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:353)
 at 
org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178)
 at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:378)
 at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:205)
 at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:203)
 at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:133)
 at 
org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.createReportMojo(AbstractProjectInfoTestCase.java:188)
 at 
org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.generateReport(AbstractProjectInfoTestCase.java:181)
 at 
org.apache.maven.report.projectinfo.CiManagementReportTest.testReport(CiManagementReportTest.java:51)
{code}

  was:
When testing update to Doxia 1.7/1.8 i got issue.with Plexus

To reproduce error - change version of _plexus-container-default_ to 1.7.1

{{Running org.apache.maven.report.projectinfo.CiManagementReportTest}}
{{Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.955 sec <<< 
FAILURE! - in org.apache.maven.report.projectinfo.CiManagementReportTest}}
{{testReport(org.apache.maven.report.projectinfo.CiManagementReportTest) Time 
elapsed: 0.684 sec <<< ERROR!}}
{{org.codehaus.plexus.component.repository.exception.ComponentLookupException:}}
{{Component descriptor cannot be found in the component repository}}
{{ role: org.apache.maven.plugin.Mojo}}
{{ roleHint: 
org.apache.maven.plugins:maven-project-info-reports-plugin:2.10-SNAPSHOT:cim}}
{{classRealm: none specified}}
{{ at 
org.codehaus.plexus.DefaultComponentRegistry.getComponentManager(DefaultComponentRegistry.java:435)}}
{{ at 
org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:353)}}
{{ at 
org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178)}}
{{ at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:378)}}
{{ at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:205)}}
{{ at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:203)}}
{{ at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:133)}}
{{ at 
org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.createReportMojo(AbstractProjectInfoTestCase.java:188)}}
{{ at 
org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.generateReport(AbstractProjectInfoTestCase.java:181)}}
{{ at 
org.apache.maven.report.projectinfo.CiManagementReportTest.testReport(CiManagementReportTest.java:51)}}


> Update plexus-container-default to 1.7.1 causes tests with 
> maven-plugin-testing-harness 1.3 to fail
> ---
>
> Key: MPIR-364
> URL: https://issues.apache.org/jira/browse/MPIR-364
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Priority: Major
>
> When testing update to Doxia 1.7/1.8 i got issue.with Plexus
> To reproduce error - change version of _plexus-container-default_ to 1.7.1
> {code}
> Running org.apache.maven.report.projectinfo.CiManagementReportTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.955 sec <<< 
> FAILURE! - in org.apache.maven.report.projectinfo.CiManagementReportTest
> testReport(org.apache.maven.report.projectinfo.CiManagementReportTest) Time 
> elapsed: 0.684 sec <<< ERROR!
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository
>  role: org.apache.maven.plugin.Mojo
>  roleHint: 

[jira] [Commented] (MPIR-345) Upgrade to Doxia 1.7

[Sylwester Lachiewicz (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394449#comment-16394449
 ] 

Sylwester Lachiewicz commented on MPIR-345:
---

Hi [~michael-o] looks like issue somewhere between plexus and m-p-t-h because 
only tests are failing. When i skip test i can generate site using latest Doxia

> Upgrade to Doxia 1.7
> 
>
> Key: MPIR-345
> URL: https://issues.apache.org/jira/browse/MPIR-345
> Project: Maven Project Info Reports Plugin
>  Issue Type: Task
>Affects Versions: 2.9
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 2.10
>
> Attachments: 1.7.log, MPIR-345.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-361) Upgrade parent to 31

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394448#comment-16394448
 ] 

Karl Heinz Marbaise commented on MPIR-361:
--

[~slachiewicz] could you take a look why the build is failing that would really 
help...Thanks.

> Upgrade parent to 31
> 
>
> Key: MPIR-361
> URL: https://issues.apache.org/jira/browse/MPIR-361
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 2.10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 2.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MPIR-364) Update plexus-container-default to 1.7.1 causes tests with maven-plugin-testing-harness 1.3 to fail

[Sylwester Lachiewicz (JIRA)]

Sylwester Lachiewicz created MPIR-364:
-

 Summary: Update plexus-container-default to 1.7.1 causes tests 
with maven-plugin-testing-harness 1.3 to fail
 Key: MPIR-364
 URL: https://issues.apache.org/jira/browse/MPIR-364
 Project: Maven Project Info Reports Plugin
  Issue Type: Bug
Reporter: Sylwester Lachiewicz


When testing update to Doxia 1.7/1.8 i got issue.with Plexus

To reproduce error - change version of _plexus-container-default_ to 1.7.1

{{Running org.apache.maven.report.projectinfo.CiManagementReportTest}}
{{Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.955 sec <<< 
FAILURE! - in org.apache.maven.report.projectinfo.CiManagementReportTest}}
{{testReport(org.apache.maven.report.projectinfo.CiManagementReportTest) Time 
elapsed: 0.684 sec <<< ERROR!}}
{{org.codehaus.plexus.component.repository.exception.ComponentLookupException:}}
{{Component descriptor cannot be found in the component repository}}
{{ role: org.apache.maven.plugin.Mojo}}
{{ roleHint: 
org.apache.maven.plugins:maven-project-info-reports-plugin:2.10-SNAPSHOT:cim}}
{{classRealm: none specified}}
{{ at 
org.codehaus.plexus.DefaultComponentRegistry.getComponentManager(DefaultComponentRegistry.java:435)}}
{{ at 
org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:353)}}
{{ at 
org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178)}}
{{ at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:378)}}
{{ at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:205)}}
{{ at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:203)}}
{{ at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:133)}}
{{ at 
org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.createReportMojo(AbstractProjectInfoTestCase.java:188)}}
{{ at 
org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.generateReport(AbstractProjectInfoTestCase.java:181)}}
{{ at 
org.apache.maven.report.projectinfo.CiManagementReportTest.testReport(CiManagementReportTest.java:51)}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (MPIR-363) Update dependences to latest versions (before 3.x)

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394446#comment-16394446
 ] 

Karl Heinz Marbaise edited comment on MPIR-363 at 3/11/18 8:40 AM:
---

I would check this after MPIR-361 is done...apart from that a model upgrade to 
3.5.3 is not a good idea...


was (Author: khmarbaise):
I would check this after MPIR-361 is done...

> Update dependences to latest versions (before 3.x)
> --
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Reporter: Sylwester Lachiewicz
>Priority: Major
>
> {{The following plugin updates are available:}}
>  {{maven-changes-plugin ... 2.11 -> 2.12.1}}
>  {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
>  {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}
> {{The following dependencies in Dependency Management have newer versions:}}
>  {{org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1}}
>  {{org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}
> {{The following dependencies in Dependencies have newer versions:}}
>  {{commons-validator:commons-validator . 1.5.1 -> 1.6}}
>  {{httpunit:httpunit ... 1.6 -> 1.6.1}}
>  {{junit:junit  3.8.2 -> 4.12}}
>  {{org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
>  {{org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
>  {{org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
>  {{org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 
> 3.3.0}}
>  {{org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
>  {{org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
>  {{org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
>  {{org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
>  {{org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 
> 1.7.1}}
>  {{org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}
> {{The following dependencies in pluginManagement of plugins have newer 
> versions:}}
>  {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
>  {{org.apache.maven.shared:maven-shared-resources  1 -> 2}}
> {{The following dependencies in Plugin Dependencies have newer versions:}}
>  {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
>  {{org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-363) Update dependences to latest versions (before 3.x)

[Karl Heinz Marbaise (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394446#comment-16394446
 ] 

Karl Heinz Marbaise commented on MPIR-363:
--

I would check this after MPIR-361 is done...

> Update dependences to latest versions (before 3.x)
> --
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Reporter: Sylwester Lachiewicz
>Priority: Major
>
> {{The following plugin updates are available:}}
>  {{maven-changes-plugin ... 2.11 -> 2.12.1}}
>  {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
>  {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}
> {{The following dependencies in Dependency Management have newer versions:}}
>  {{org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1}}
>  {{org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}
> {{The following dependencies in Dependencies have newer versions:}}
>  {{commons-validator:commons-validator . 1.5.1 -> 1.6}}
>  {{httpunit:httpunit ... 1.6 -> 1.6.1}}
>  {{junit:junit  3.8.2 -> 4.12}}
>  {{org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
>  {{org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
>  {{org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
>  {{org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
>  {{org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
>  {{org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 
> 3.3.0}}
>  {{org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
>  {{org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
>  {{org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
>  {{org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
>  {{org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
>  {{org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 
> 1.7.1}}
>  {{org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}
> {{The following dependencies in pluginManagement of plugins have newer 
> versions:}}
>  {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
>  {{org.apache.maven.shared:maven-shared-resources  1 -> 2}}
> {{The following dependencies in Plugin Dependencies have newer versions:}}
>  {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
>  {{org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-361) Upgrade parent to 31

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1639#comment-1639
 ] 

ASF GitHub Bot commented on MPIR-361:
-

khmarbaise commented on issue #1: [MPIR-361] Fix checkstyle errors after 
chekstyle update
URL: 
https://github.com/apache/maven-project-info-reports-plugin/pull/1#issuecomment-372098703
 
 
   Hi, could you please have a look here: 
   
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-project-info-reports-plugin/job/MPIR-361/2/console
   furthermore https://issues.apache.org/jira/browse/MPIR-361
   That means the branch for this issue is already there and build fails based 
on other reasons...
   ```
   [windows-jdk9] [ERROR] Failed to execute goal 
org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
maven-project-info-reports-plugin: Result of cmd.exe /X /C 
'"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
apache -keystore 
f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
 -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
cannot find the path specified.. -> [Help 1]
   ```


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Upgrade parent to 31
> 
>
> Key: MPIR-361
> URL: https://issues.apache.org/jira/browse/MPIR-361
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 2.10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 2.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] khmarbaise commented on issue #1: [MPIR-361] Fix checkstyle errors after chekstyle update

[GitBox]

khmarbaise commented on issue #1: [MPIR-361] Fix checkstyle errors after 
chekstyle update
URL: 
https://github.com/apache/maven-project-info-reports-plugin/pull/1#issuecomment-372098703
 
 
   Hi, could you please have a look here: 
   
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-project-info-reports-plugin/job/MPIR-361/2/console
   furthermore https://issues.apache.org/jira/browse/MPIR-361
   That means the branch for this issue is already there and build fails based 
on other reasons...
   ```
   [windows-jdk9] [ERROR] Failed to execute goal 
org.codehaus.mojo:keytool-maven-plugin:1.0:genkey (init) on project 
maven-project-info-reports-plugin: Result of cmd.exe /X /C 
'"f:\jenkins\tools\java\latest9\..\bin\keytool.exe -genkey -dname "cn=jetty, 
ou=jetty, L=Unknown, ST=Unknown, o=Apache, c=Unknown" -alias apache -keypass 
apache -keystore 
f:\jenkins\jenkins-slave\workspace\nfo-reports-plugin_MPIR-361-USOHCFAWZ4BXXFD3QLHLQ2HOCUSPDFM5URQGLU7AUHHJFZBJBXTQ\m/target/jetty.jks
 -storepass apache -validity 365 -keyalg RSA"' execution is: '1': The system 
cannot find the path specified.. -> [Help 1]
   ```


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Updated] (MPIR-363) Update dependences to latest versions (before 3.x)

[Sylwester Lachiewicz (JIRA)]

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

Sylwester Lachiewicz updated MPIR-363:
--
Description: 
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
 {{org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1}}
 {{org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
 {{commons-validator:commons-validator . 1.5.1 -> 1.6}}
 {{httpunit:httpunit ... 1.6 -> 1.6.1}}
 {{junit:junit  3.8.2 -> 4.12}}
 {{org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
 {{org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
 {{org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 
3.3.0}}
 {{org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
 {{org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
 {{org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
 {{org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
 {{org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
 {{org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
 {{org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
 {{org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 
1.7.1}}
 {{org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}

{{The following dependencies in pluginManagement of plugins have newer 
versions:}}
 {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
 {{org.apache.maven.shared:maven-shared-resources  1 -> 2}}

{{The following dependencies in Plugin Dependencies have newer versions:}}
 {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
 {{org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}

  was:
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
 {{org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1}}
 {{org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
 {{commons-validator:commons-validator . 1.5.1 -> 1.6}}
 {{httpunit:httpunit ... 1.6 -> 1.6.1}}
 {{junit:junit  3.8.2 -> 4.12}}
 {{org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
 {{org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
 {{org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}{{ 1.3 -> 
3.3.0}}
 {{org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
 {{org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
 

[jira] [Updated] (MPIR-363) Update dependences to latest versions (before 3.x)

[Sylwester Lachiewicz (JIRA)]

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

Sylwester Lachiewicz updated MPIR-363:
--
Description: 
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
 {{org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1}}
 {{org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
 {{commons-validator:commons-validator . 1.5.1 -> 1.6}}
 {{httpunit:httpunit ... 1.6 -> 1.6.1}}
 {{junit:junit  3.8.2 -> 4.12}}
 {{org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
 {{org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
 {{org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
 {{org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
 {{org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
 {{org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}{{ 1.3 -> 
3.3.0}}
 {{org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
 {{org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
 {{org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
 {{org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
 {{org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
 {{org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
 {{org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
 {{org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 
1.7.1}}
 {{org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}

{{The following dependencies in pluginManagement of plugins have newer 
versions:}}
 {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
 {{org.apache.maven.shared:maven-shared-resources  1 -> 2}}

{{The following dependencies in Plugin Dependencies have newer versions:}}
 {{org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
 {{org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}

  was:
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
{{ org.apache.maven.plugin-tools:maven-plugin-annotations ...}}
{{ 3.4 -> 3.5.1}}
\{{ org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
{{ commons-validator:commons-validator . 1.5.1 -> 1.6}}
{{ httpunit:httpunit ... 1.6 -> 1.6.1}}
{{ junit:junit  3.8.2 -> 4.12}}
{{ org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
{{ org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
{{ org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}{{ 1.3 -> 
3.3.0}}
{{ org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
{{ org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
{{ 

[jira] [Updated] (MPIR-363) Update dependences to latest versions (before 3.x)

[Sylwester Lachiewicz (JIRA)]

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

Sylwester Lachiewicz updated MPIR-363:
--
Description: 
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
{{ org.apache.maven.plugin-tools:maven-plugin-annotations ...}}
{{ 3.4 -> 3.5.1}}
\{{ org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
{{ commons-validator:commons-validator . 1.5.1 -> 1.6}}
{{ httpunit:httpunit ... 1.6 -> 1.6.1}}
{{ junit:junit  3.8.2 -> 4.12}}
{{ org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
{{ org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
{{ org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}
{{ 1.3 -> 3.3.0}}
{{ org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
{{ org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
{{ org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
{{ org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
{{ org.codehaus.plexus:plexus-container-default ...}}
{{ 1.0-alpha-9-stable-1 -> 1.7.1}}
{{ org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}

{{The following dependencies in pluginManagement of plugins have newer 
versions:}}
\{{ org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
 \{{ org.apache.maven.shared:maven-shared-resources  1 -> 2}}

{{The following dependencies in Plugin Dependencies have newer versions:}}
 \{{ org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
 \{{ org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}

 

  was:
{{The following plugin updates are available:}}
{{maven-changes-plugin ... 2.11 -> 2.12.1}}
{{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
{{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}


{{The following dependencies in Dependency Management have newer versions:}}
{{ org.apache.maven.plugin-tools:maven-plugin-annotations ...}}
{{ 3.4 -> 3.5.1}}
{{ org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
{{ commons-validator:commons-validator . 1.5.1 -> 1.6}}
{{ httpunit:httpunit ... 1.6 -> 1.6.1}}
{{ junit:junit  3.8.2 -> 4.12}}
{{ org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
{{ org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
{{ org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}
{{ 1.3 -> 3.3.0}}
{{ org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
{{ org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 

[jira] [Updated] (MPIR-363) Update dependences to latest versions (before 3.x)

[Sylwester Lachiewicz (JIRA)]

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

Sylwester Lachiewicz updated MPIR-363:
--
Description: 
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
{{ org.apache.maven.plugin-tools:maven-plugin-annotations ...}}
{{ 3.4 -> 3.5.1}}
\{{ org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
{{ commons-validator:commons-validator . 1.5.1 -> 1.6}}
{{ httpunit:httpunit ... 1.6 -> 1.6.1}}
{{ junit:junit  3.8.2 -> 4.12}}
{{ org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
{{ org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
{{ org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}{{ 1.3 -> 
3.3.0}}
{{ org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
{{ org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
{{ org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
{{ org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
{{ org.codehaus.plexus:plexus-container-default ...}}
{{ 1.0-alpha-9-stable-1 -> 1.7.1}}
{{ org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}

{{The following dependencies in pluginManagement of plugins have newer 
versions:}}
{{ org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
{{ org.apache.maven.shared:maven-shared-resources  1 -> 2}}

{{The following dependencies in Plugin Dependencies have newer versions:}}
{{ org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
{{ org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}

 

  was:
{{The following plugin updates are available:}}
 {{maven-changes-plugin ... 2.11 -> 2.12.1}}
 {{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
 {{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}

{{The following dependencies in Dependency Management have newer versions:}}
{{ org.apache.maven.plugin-tools:maven-plugin-annotations ...}}
{{ 3.4 -> 3.5.1}}
\{{ org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
{{ commons-validator:commons-validator . 1.5.1 -> 1.6}}
{{ httpunit:httpunit ... 1.6 -> 1.6.1}}
{{ junit:junit  3.8.2 -> 4.12}}
{{ org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
{{ org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
{{ org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}
{{ 1.3 -> 3.3.0}}
{{ org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
{{ org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}

[jira] [Created] (MPIR-363) Update dependences to latest versions (before 3.x)

[Sylwester Lachiewicz (JIRA)]

Sylwester Lachiewicz created MPIR-363:
-

 Summary: Update dependences to latest versions (before 3.x)
 Key: MPIR-363
 URL: https://issues.apache.org/jira/browse/MPIR-363
 Project: Maven Project Info Reports Plugin
  Issue Type: Dependency upgrade
Reporter: Sylwester Lachiewicz


{{The following plugin updates are available:}}
{{maven-changes-plugin ... 2.11 -> 2.12.1}}
{{maven-jarsigner-plugin ... 1.3.2 -> 1.4}}
{{org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5}}


{{The following dependencies in Dependency Management have newer versions:}}
{{ org.apache.maven.plugin-tools:maven-plugin-annotations ...}}
{{ 3.4 -> 3.5.1}}
{{ org.codehaus.plexus:plexus-component-annotations  1.6 -> 1.7.1}}

{{The following dependencies in Dependencies have newer versions:}}
{{ commons-validator:commons-validator . 1.5.1 -> 1.6}}
{{ httpunit:httpunit ... 1.6 -> 1.6.1}}
{{ junit:junit  3.8.2 -> 4.12}}
{{ org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-model .. 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2}}
{{ org.apache.maven:maven-repository-metadata  2.2.1 -> 3.5.3}}
{{ org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3}}
{{ org.apache.maven.doxia:doxia-core . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-integration-tools  1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8}}
{{ org.apache.maven.doxia:doxia-site-renderer  1.6 -> 1.8}}
{{ org.apache.maven.plugin-testing:maven-plugin-testing-harness ...}}
{{ 1.3 -> 3.3.0}}
{{ org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0}}
{{ org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1}}
{{ org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1}}
{{ org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0}}
{{ org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0}}
{{ org.codehaus.plexus:plexus-container-default ...}}
{{ 1.0-alpha-9-stable-1 -> 1.7.1}}
{{ org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0}}

{{The following dependencies in pluginManagement of plugins have newer 
versions:}}
{{ org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
{{ org.apache.maven.shared:maven-shared-resources  1 -> 2}}

{{The following dependencies in Plugin Dependencies have newer versions:}}
{{ org.apache.maven.doxia:doxia-core . 1.2 -> 1.8}}
{{ org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7}}

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MPIR-361) Upgrade parent to 31

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPIR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394443#comment-16394443
 ] 

ASF GitHub Bot commented on MPIR-361:
-

slachiewicz opened a new pull request #1: [MPIR-361] Fix checkstyle errors 
after chekstyle update
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Upgrade parent to 31
> 
>
> Key: MPIR-361
> URL: https://issues.apache.org/jira/browse/MPIR-361
> Project: Maven Project Info Reports Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 2.10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 2.10
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] slachiewicz opened a new pull request #1: [MPIR-361] Fix checkstyle errors after chekstyle update

[GitBox]

slachiewicz opened a new pull request #1: [MPIR-361] Fix checkstyle errors 
after chekstyle update
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MPLUGINTESTING-49) Clover plugin is not working properly

[Sylwester Lachiewicz (JIRA)]

[ 
https://issues.apache.org/jira/browse/MPLUGINTESTING-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394438#comment-16394438
 ] 

Sylwester Lachiewicz commented on MPLUGINTESTING-49:


Looks like issue with Clover plugin - not with 
_org.apache.maven.plugin-testing:maven-plugin-testing-harness_.

Please report error to Atlassian Clover or try wit 
[OpenClover|http://openclover.org/]

> Clover plugin is not working properly
> -
>
> Key: MPLUGINTESTING-49
> URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-49
> Project: Maven Plugin Testing
>  Issue Type: Bug
>Reporter: dinesh
>Priority: Major
>
> Getting the below error. 
> initializationError(za.co.sb.core.datamodel.serializer.test.ObjectSerializerTest):
>  com_atlassian_clover/TestNameSniffer
>   initializationError(za.co.sb.core.datamodel.test.DataImplTest): 
> com_atlassian_clover/TestNameSniffer
>   initializationError(za.co.sb.core.datamodel.test.ErrorImplTest): 
> com_atlassian_clover/TestNameSniffer
> plugin using.
> 
>   com.atlassian.maven.plugins
>maven-clover2-plugin
> 
>
>
> C:\Users\w728473\Desktop\clover\clover.license
>  
> 
> 
> 
> com.atlassian.clover 
> clover
> 
> 
>  
>   
> 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)