[jira] [Updated] (MNG-6026) Extend the Project Object Model (POM) with trust information (OpenPGP, hash values)
[
https://issues.apache.org/jira/browse/MNG-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Schmaus updated MNG-6026:
-
Description:
I'm not sure if this is the right place to raise an feature request for the POM
format itself. I've already tried to get in touch with the right people about
this feature request, but failed. I'm willing to help designing and
implementing this, but need guidance.
The origin of this feature request is
[http://stackoverflow.com/a/34795359/194894], and [especially a SO user
requesting me to put this
up|http://stackoverflow.com/questions/3307146/verification-of-dependency-authenticy-in-maven-pom-based-automated-build-systems/34795359?noredirect=1#comment62178671_34795359].
h2. Extend the Project Object Model (POM) with trust information (OpenPGP - RFC
4480 and hash values)
What we need is the possibility to model a trust relation from your project or
artifact to the declared dependencies. So that, if all involved parties declare
such a relation, we are able to create a "chain of trust" from the root (e.g.
the project) over its dependencies down to the very last transitive dependency.
The Project Object Model (POM) needs to be extended by a
element for dependencies.
h3. Current Situation
Right now we have something like
{code:xml}
junit
junit
4.0
{code}
h3. Hard dependencies
For hard dependencies, could include the sha256sum of artifact
and its POM file:
{code:xml}
junit
junit
[4.0]
[sha256 of junit pom file]
[sha256sum of artifact (junit.jar)]
{code}
h3. Soft dependencies
If soft or ranged dependencies are used, then we could specify the public key
(or multiple) of the keypair used to sign the artifacts
{code:xml}
junit
junit
[4.0,4.5)
[secure fingerprint of OpenPGP key]
{code}
was:
I'm not sure if this is the right place to raise an feature request for the POM
format itself. I've already tried to get in touch with the right people about
this feature request, but failed. I'm willing to help designing and
implementing tihs, but need guidance.
The origin of this feature request is
http://stackoverflow.com/a/34795359/194894, and [especially a SO user
requesting me to put this
up|http://stackoverflow.com/questions/3307146/verification-of-dependency-authenticy-in-maven-pom-based-automated-build-systems/34795359?noredirect=1#comment62178671_34795359].
h2. Extend the Project Object Model (POM) with trust information (OpenPGP - RFC
4480 and hash values)
What we need is the possibility to model a trust relation from your project or
artifact to the declared dependencies. So that, if all involved parties declare
such a relation, we are able to create a "chain of trust" from the root (e.g.
the project) over its dependencies down to the very last transitive dependency.
The Project Object Model (POM) needs to be extended by a
element for dependencies.
h3. Current Situation
Right now we have something like
{code:xml}
junit
junit
4.0
{code}
h3. Hard dependencies
For hard dependencies, could include the sha256sum of artifact
and its POM file:
{code:xml}
junit
junit
[4.0]
[sha256 of junit pom file]
[sha256sum of artifact (junit.jar)]
{code}
h3. Soft dependencies
If soft or ranged dependencies are used, then we could specify the public key
(or multiple) of the keypair used to sign the artifacts
{code:xml}
junit
junit
[4.0,4.5)
[secure fingerprint of OpenPGP key]
{code}
> Extend the Project Object Model (POM) with trust information (OpenPGP, hash
> values)
> ---
>
> Key: MNG-6026
> URL: https://issues.apache.org/jira/browse/MNG-6026
> Project: Maven
> Issue Type: New Feature
> Components: core
>Reporter: Florian Schmaus
>Priority: Major
>
> I'm not sure if this is the right place to raise an feature request for the
> POM format itself. I've already tried to get in touch with the right people
> about this feature request, but failed. I'm willing to help designing and
> implementing this, but need guidance.
> The origin of this feature request is
> [http://stackoverflow.com/a/34795359/194894], and [especially a SO user
> requesting me to put this
> up|http://stackoverflow.com/questions/3307146/verification-of-dependency-authenticy-in-maven-pom-based-automated-build-systems/34795359?noredirect=1#comment62178671_34795359].
> h2. Extend the Project Object Model (POM) with trust information (OpenPGP -
> RFC 4480 and hash values)
> What we need is the possibility to model a trust relation from your project
> or artifact to the declared dependencies. So that, if all involved parties
> declare such a relation, we are able to create a "chain of trust" from the
> root (e.g.
[jira] [Updated] (MNG-6026) Extend the Project Object Model (POM) with trust information (OpenPGP, hash values)
[
https://issues.apache.org/jira/browse/MNG-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Schmaus updated MNG-6026:
-
Labels: artifact-verification security (was: )
> Extend the Project Object Model (POM) with trust information (OpenPGP, hash
> values)
> ---
>
> Key: MNG-6026
> URL: https://issues.apache.org/jira/browse/MNG-6026
> Project: Maven
> Issue Type: New Feature
> Components: core
>Reporter: Florian Schmaus
>Priority: Major
> Labels: artifact-verification, security
>
> I'm not sure if this is the right place to raise an feature request for the
> POM format itself. I've already tried to get in touch with the right people
> about this feature request, but failed. I'm willing to help designing and
> implementing this, but need guidance.
> The origin of this feature request is
> [http://stackoverflow.com/a/34795359/194894], and [especially a SO user
> requesting me to put this
> up|http://stackoverflow.com/questions/3307146/verification-of-dependency-authenticy-in-maven-pom-based-automated-build-systems/34795359?noredirect=1#comment62178671_34795359].
> h2. Extend the Project Object Model (POM) with trust information (OpenPGP -
> RFC 4480 and hash values)
> What we need is the possibility to model a trust relation from your project
> or artifact to the declared dependencies. So that, if all involved parties
> declare such a relation, we are able to create a "chain of trust" from the
> root (e.g. the project) over its dependencies down to the very last
> transitive dependency. The Project Object Model (POM) needs to be extended by
> a element for dependencies.
> h3. Current Situation
> Right now we have something like
> {code:xml}
>
> junit
> junit
> 4.0
>
> {code}
> h3. Hard dependencies
> For hard dependencies, could include the sha256sum of artifact
> and its POM file:
> {code:xml}
>
> junit
> junit
> [4.0]
>
>
> [sha256 of junit pom file]
> [sha256sum of artifact (junit.jar)]
>
>
>
> {code}
> h3. Soft dependencies
> If soft or ranged dependencies are used, then we could specify the public key
> (or multiple) of the keypair used to sign the artifacts
> {code:xml}
>
> junit
> junit
> [4.0,4.5)
>
> [secure fingerprint of OpenPGP key]
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1487) ParallelComputerBuilderTest fails on overloaded system because internal delay are shorter than blocking time of JVM
[
https://issues.apache.org/jira/browse/SUREFIRE-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1487:
---
Fix Version/s: 3.0.0-M1
> ParallelComputerBuilderTest fails on overloaded system because internal delay
> are shorter than blocking time of JVM
> ---
>
> Key: SUREFIRE-1487
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1487
> Project: Maven Surefire
> Issue Type: Task
> Components: Junit 4.7+ (parallel) support
>Reporter: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> The delays are 500 ms and variations 250 ms.
> The JVM was blocked for 675 ms.
> From these measurements, the new delay should be 3-times longer at least.
> [windows] Tests in error:
> [windows]
> separatePoolsWithSuiteAndSequentialClasses(org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilderTest):
> (..)
> [windows]
> parallelMethodsReuseOneOrTwoThreads(org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilderTest):
> (..)
> [windows]
> suiteAndClassInOnePool(org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilderTest):
> (..)
> suiteAndClassInOnePool:
> Expected: (between <1450L> and <1750L> or between <1950L> and <2250L> or
> between <2450L> and <2750L>)
> but: was <3175L>
> parallelMethodsReuseOneOrTwoThreads:
> Expected: between <1450L> and <1750L>
> but: was <1837L>
> separatePoolsWithSuiteAndSequentialClasses:
> Expected: between <1450L> and <1750L>
> but: was <3562L>
> In this case the JVM was blocked for 2.062 second and the delays should be 9
> times longer. The test {{ParallelComputerBuilderTest}} has small number of
> tests, so we can prolong the delays 10 times.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MSITE-815) highlight skin used to render site and documents statistics
Hervé Boutemy created MSITE-815:
---
Summary: highlight skin used to render site and documents
statistics
Key: MSITE-815
URL: https://issues.apache.org/jira/browse/MSITE-815
Project: Maven Site Plugin
Issue Type: Wish
Components: doxia integration
Affects Versions: 3.7
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
Fix For: 3.7.1
current typical output is:
{noformat}[INFO] --- maven-site-plugin:3.7:site (default-site) @ maven-site ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.9
[INFO] 21 reports configured for maven-project-info-reports-plugin:2.9: index,
summary, dependency-info, modules, project-team, scm, issue-tracking,
mailing-list, dependency-management, dependencies, dependency-convergence, cim,
plugin-management, plugins, distribution-management, index, project-team,
mailing-list, scm, issue-tracking, cim
[INFO] Relativizing decoration links with respect to localized project URL:
https://maven.apache.org/
[INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.7
skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:2.9:index),
file "index.html" already exists for the English version.
[INFO] Skipped "Source Code Management" report
(maven-project-info-reports-plugin:2.9:scm), file "source-repository.html"
already exists for the English version.
[INFO] Skipped "Issue Management" report
(maven-project-info-reports-plugin:2.9:issue-tracking), file
"issue-tracking.html" already exists for the English version.
[INFO] Rendering 197 Doxia documents: 142 apt, 4 fml, 41 markdown, 9 xdoc, 1
xhtml{noformat}
hightlighting the skin artifact id and the Doxia documents statistics would
improve user experience by showing prominently key info at key steps
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421655#comment-16421655 ] Hudson commented on MPIR-366: - Build failed in Jenkins: Maven TLP » maven-project-info-reports-plugin » MPIR-366 #12 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/MPIR-366/12/ > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-815) highlight skin used to render site and documents statistics
[
https://issues.apache.org/jira/browse/MSITE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421663#comment-16421663
]
Hudson commented on MSITE-815:
--
Build succeeded in Jenkins: Maven TLP » maven-site-plugin » master #27
See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/27/
> highlight skin used to render site and documents statistics
> ---
>
> Key: MSITE-815
> URL: https://issues.apache.org/jira/browse/MSITE-815
> Project: Maven Site Plugin
> Issue Type: Wish
> Components: doxia integration
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> current typical output is:
> {noformat}[INFO] --- maven-site-plugin:3.7:site (default-site) @ maven-site
> ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.9
> [INFO] 21 reports configured for maven-project-info-reports-plugin:2.9:
> index, summary, dependency-info, modules, project-team, scm, issue-tracking,
> mailing-list, dependency-management, dependencies, dependency-convergence,
> cim, plugin-management, plugins, distribution-management, index,
> project-team, mailing-list, scm, issue-tracking, cim
> [INFO] Relativizing decoration links with respect to localized project URL:
> https://maven.apache.org/
> [INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.7
> skin.
> [INFO] Skipped "About" report (maven-project-info-reports-plugin:2.9:index),
> file "index.html" already exists for the English version.
> [INFO] Skipped "Source Code Management" report
> (maven-project-info-reports-plugin:2.9:scm), file "source-repository.html"
> already exists for the English version.
> [INFO] Skipped "Issue Management" report
> (maven-project-info-reports-plugin:2.9:issue-tracking), file
> "issue-tracking.html" already exists for the English version.
> [INFO] Rendering 197 Doxia documents: 142 apt, 4 fml, 41 markdown, 9 xdoc, 1
> xhtml{noformat}
> hightlighting the skin artifact id and the Doxia documents statistics would
> improve user experience by showing prominently key info at key steps
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421665#comment-16421665 ] Hudson commented on MPIR-366: - Build failed in Jenkins: Maven TLP » maven-project-info-reports-plugin » MPIR-366 #13 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/MPIR-366/13/ > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-695) Move checksum creation from install part to deploy part
[ https://issues.apache.org/jira/browse/MSHARED-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421684#comment-16421684 ] Hudson commented on MSHARED-695: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-695 #2 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-695/2/ > Move checksum creation from install part to deploy part > --- > > Key: MSHARED-695 > URL: https://issues.apache.org/jira/browse/MSHARED-695 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: maven-artifact-transfer-0.10.0 > > > We should remove the checksum generation from install parts and move them > consistently to the deploy part instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-148) Upgrade xstream to 1.4.10
[
https://issues.apache.org/jira/browse/MPH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421688#comment-16421688
]
Hudson commented on MPH-148:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-148 #2
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-148/2/
> Upgrade xstream to 1.4.10
> -
>
> Key: MPH-148
> URL: https://issues.apache.org/jira/browse/MPH-148
> Project: Maven Help Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently the upgrade will causes failures in IT's like the
> following:evaluate-settings-servers
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (M
[jira] [Commented] (MPH-148) Upgrade xstream to 1.4.10
[
https://issues.apache.org/jira/browse/MPH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421692#comment-16421692
]
Hudson commented on MPH-148:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-148 #3
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-148/3/
> Upgrade xstream to 1.4.10
> -
>
> Key: MPH-148
> URL: https://issues.apache.org/jira/browse/MPH-148
> Project: Maven Help Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently the upgrade will causes failures in IT's like the
> following:evaluate-settings-servers
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (M
[jira] [Updated] (MPH-148) Upgrade xstream to 1.4.10
[
https://issues.apache.org/jira/browse/MPH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-148:
Description:
Currently the upgrade will causes failures in IT's like the
following:evaluate-settings-servers
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
(default-cli) on project test: Execution default-cli of goal
org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
(default-cli) on project test: Execution default-cli of goal
org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
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.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal
org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:148)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
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.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
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: com.thoughtworks.xstream.InitializationException: Could no
[jira] [Issue Comment Deleted] (MPH-148) Upgrade xstream to 1.4.10
[
https://issues.apache.org/jira/browse/MPH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-148:
Comment: was deleted
(was: Upgrading to 1.4.9 or 1.4.8 will not work cause both of them contain JDK
8 compiled classes See https://github.com/x-stream/xstream/issues/113)
> Upgrade xstream to 1.4.10
> -
>
> Key: MPH-148
> URL: https://issues.apache.org/jira/browse/MPH-148
> Project: Maven Help Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently the upgrade will causes failures in IT's like the
> following:evaluate-settings-servers
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.
[jira] [Created] (MPH-151) Add documentation information for GitHub
Karl Heinz Marbaise created MPH-151: --- Summary: Add documentation information for GitHub Key: MPH-151 URL: https://issues.apache.org/jira/browse/MPH-151 Project: Maven Help Plugin Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Fix For: 3.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSITE-815) highlight skin used to render site and documents statistics
[
https://issues.apache.org/jira/browse/MSITE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy closed MSITE-815.
---
Resolution: Fixed
https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=53905d8f1740a364e13e1ee6d2f98d8bcd26ea88
> highlight skin used to render site and documents statistics
> ---
>
> Key: MSITE-815
> URL: https://issues.apache.org/jira/browse/MSITE-815
> Project: Maven Site Plugin
> Issue Type: Wish
> Components: doxia integration
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> current typical output is:
> {noformat}[INFO] --- maven-site-plugin:3.7:site (default-site) @ maven-site
> ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.9
> [INFO] 21 reports configured for maven-project-info-reports-plugin:2.9:
> index, summary, dependency-info, modules, project-team, scm, issue-tracking,
> mailing-list, dependency-management, dependencies, dependency-convergence,
> cim, plugin-management, plugins, distribution-management, index,
> project-team, mailing-list, scm, issue-tracking, cim
> [INFO] Relativizing decoration links with respect to localized project URL:
> https://maven.apache.org/
> [INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.7
> skin.
> [INFO] Skipped "About" report (maven-project-info-reports-plugin:2.9:index),
> file "index.html" already exists for the English version.
> [INFO] Skipped "Source Code Management" report
> (maven-project-info-reports-plugin:2.9:scm), file "source-repository.html"
> already exists for the English version.
> [INFO] Skipped "Issue Management" report
> (maven-project-info-reports-plugin:2.9:issue-tracking), file
> "issue-tracking.html" already exists for the English version.
> [INFO] Rendering 197 Doxia documents: 142 apt, 4 fml, 41 markdown, 9 xdoc, 1
> xhtml{noformat}
> hightlighting the skin artifact id and the Doxia documents statistics would
> improve user experience by showing prominently key info at key steps
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-150) Reference of scm url to gitbox instead of github
[
https://issues.apache.org/jira/browse/MPH-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421709#comment-16421709
]
Hervé Boutemy commented on MPH-150:
---
IMHO, having both GitBox and GitHub pointers in the scm report is good to let
users choose where the want to look at: that was the rationale behind the
choice I did when migrating our repositories from svn to GitBox
> Reference of scm url to gitbox instead of github
>
>
> Key: MPH-150
> URL: https://issues.apache.org/jira/browse/MPH-150
> Project: Maven Help Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently our scm entry
> {{https://github.com/apache/maven-help-plugin/tree/${project.scm.tag}}}
> points to github.
> Shouldn't we point to gitbox of Apache instead ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSITE-811) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSITE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421717#comment-16421717 ] Hudson commented on MSITE-811: -- Build failed in Jenkins: Maven TLP » maven-site-plugin » master #28 See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/28/ > Upgrade parent to 31 > > > Key: MSITE-811 > URL: https://issues.apache.org/jira/browse/MSITE-811 > Project: Maven Site Plugin > Issue Type: Improvement >Affects Versions: 3.7.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-521) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MJAVADOC-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421722#comment-16421722 ] Hudson commented on MJAVADOC-521: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-521 #5 See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-521/5/ > Add documentation information for GitHub > > > Key: MJAVADOC-521 > URL: https://issues.apache.org/jira/browse/MJAVADOC-521 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-521) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MJAVADOC-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421725#comment-16421725 ] Hudson commented on MJAVADOC-521: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-521 #6 See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-521/6/ > Add documentation information for GitHub > > > Key: MJAVADOC-521 > URL: https://issues.apache.org/jira/browse/MJAVADOC-521 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-521) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MJAVADOC-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421726#comment-16421726 ] Hudson commented on MJAVADOC-521: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-521 #7 See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-521/7/ > Add documentation information for GitHub > > > Key: MJAVADOC-521 > URL: https://issues.apache.org/jira/browse/MJAVADOC-521 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-148) Upgrade xstream to 1.4.10
[
https://issues.apache.org/jira/browse/MPH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421737#comment-16421737
]
Hudson commented on MPH-148:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #30
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/30/
> Upgrade xstream to 1.4.10
> -
>
> Key: MPH-148
> URL: https://issues.apache.org/jira/browse/MPH-148
> Project: Maven Help Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently the upgrade will causes failures in IT's like the
> following:evaluate-settings-servers
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (M
[jira] [Commented] (MPH-148) Upgrade xstream to 1.4.10
[
https://issues.apache.org/jira/browse/MPH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421744#comment-16421744
]
Hudson commented on MPH-148:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-150 #2
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-150/2/
> Upgrade xstream to 1.4.10
> -
>
> Key: MPH-148
> URL: https://issues.apache.org/jira/browse/MPH-148
> Project: Maven Help Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently the upgrade will causes failures in IT's like the
> following:evaluate-settings-servers
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (M
[jira] [Commented] (MPH-150) Reference of scm url to gitbox instead of github
[
https://issues.apache.org/jira/browse/MPH-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421745#comment-16421745
]
Hudson commented on MPH-150:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-150 #2
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-150/2/
> Reference of scm url to gitbox instead of github
>
>
> Key: MPH-150
> URL: https://issues.apache.org/jira/browse/MPH-150
> Project: Maven Help Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently our scm entry
> {{https://github.com/apache/maven-help-plugin/tree/${project.scm.tag}}}
> points to github.
> Shouldn't we point to gitbox of Apache instead ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPH-148) Upgrade xstream to 1.4.10
[
https://issues.apache.org/jira/browse/MPH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MPH-148.
---
Resolution: Done
Done in
[342e3ef2dfe5fc93fd728f8ea070061a9050914a|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=342e3ef2dfe5fc93fd728f8ea070061a9050914a]
> Upgrade xstream to 1.4.10
> -
>
> Key: MPH-148
> URL: https://issues.apache.org/jira/browse/MPH-148
> Project: Maven Help Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently the upgrade will causes failures in IT's like the
> following:evaluate-settings-servers
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate
> (default-cli) on project test: Execution default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-help-plugin:3.0.2-SNAPSHOT:evaluate failed:
> Could not instantiate mapper : com.thoughtworks.xstream.mapper.LambdaMapper
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> 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.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main
[jira] [Commented] (MPH-149) Upgrade jdom-legacy to jdom2 2.0.6
[ https://issues.apache.org/jira/browse/MPH-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421743#comment-16421743 ] Hudson commented on MPH-149: Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-150 #2 See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-150/2/ > Upgrade jdom-legacy to jdom2 2.0.6 > -- > > Key: MPH-149 > URL: https://issues.apache.org/jira/browse/MPH-149 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-146) JavaDoc Issues / Code cleanups
[
https://issues.apache.org/jira/browse/MPH-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421742#comment-16421742
]
Hudson commented on MPH-146:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-150 #2
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-150/2/
> JavaDoc Issues / Code cleanups
> --
>
> Key: MPH-146
> URL: https://issues.apache.org/jira/browse/MPH-146
> Project: Maven Help Plugin
> Issue Type: Task
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.1.0
>
>
> * Currently building JavaDoc with JDK 8 fails.
> * Each {{Version: $Id$}} should be removed
> *
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MWAR-413) Upgrade xstream to 1.4.10
Karl Heinz Marbaise created MWAR-413: Summary: Upgrade xstream to 1.4.10 Key: MWAR-413 URL: https://issues.apache.org/jira/browse/MWAR-413 Project: Maven WAR Plugin Issue Type: Dependency upgrade Affects Versions: 3.3.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-151) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MPH-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421748#comment-16421748 ] Hudson commented on MPH-151: Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-151 #3 See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-151/3/ > Add documentation information for GitHub > > > Key: MPH-151 > URL: https://issues.apache.org/jira/browse/MPH-151 > Project: Maven Help Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAVADOC-521) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MJAVADOC-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421752#comment-16421752 ] Hudson commented on MJAVADOC-521: - Build unstable in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-521 #8 See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-521/8/ > Add documentation information for GitHub > > > Key: MJAVADOC-521 > URL: https://issues.apache.org/jira/browse/MJAVADOC-521 > Project: Maven Javadoc Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MWAR-414) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MWAR-414: Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MWAR-414 URL: https://issues.apache.org/jira/browse/MWAR-414 Project: Maven WAR Plugin Issue Type: Dependency upgrade Affects Versions: 3.3.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-414) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MWAR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421755#comment-16421755 ] Hudson commented on MWAR-414: - Build succeeded in Jenkins: Maven TLP » maven-war-plugin » master #9 See https://builds.apache.org/job/maven-box/job/maven-war-plugin/job/master/9/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MWAR-414 > URL: https://issues.apache.org/jira/browse/MWAR-414 > Project: Maven WAR Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MWAR-414) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MWAR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MWAR-414. Resolution: Fixed Done in [8a3a3d41ec1bec2ef4060c5b0fa99812967b55fb|https://gitbox.apache.org/repos/asf?p=maven-war-plugin.git;a=commitdiff;h=8a3a3d41ec1bec2ef4060c5b0fa99812967b55fb] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MWAR-414 > URL: https://issues.apache.org/jira/browse/MWAR-414 > Project: Maven WAR Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-414) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MWAR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421758#comment-16421758 ] Hudson commented on MWAR-414: - Build succeeded in Jenkins: Maven TLP » maven-war-plugin » MWAR-413 #2 See https://builds.apache.org/job/maven-box/job/maven-war-plugin/job/MWAR-413/2/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MWAR-414 > URL: https://issues.apache.org/jira/browse/MWAR-414 > Project: Maven WAR Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-413) Upgrade xstream to 1.4.10
[ https://issues.apache.org/jira/browse/MWAR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421759#comment-16421759 ] Hudson commented on MWAR-413: - Build succeeded in Jenkins: Maven TLP » maven-war-plugin » MWAR-413 #2 See https://builds.apache.org/job/maven-box/job/maven-war-plugin/job/MWAR-413/2/ > Upgrade xstream to 1.4.10 > - > > Key: MWAR-413 > URL: https://issues.apache.org/jira/browse/MWAR-413 > Project: Maven WAR Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MWAR-406) custom artifact types don't get copied to WEB-INF/lib
[ https://issues.apache.org/jira/browse/MWAR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MWAR-406: - Fix Version/s: waiting-for-feedback > custom artifact types don't get copied to WEB-INF/lib > - > > Key: MWAR-406 > URL: https://issues.apache.org/jira/browse/MWAR-406 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Jimmy Praet >Priority: Major > Fix For: waiting-for-feedback > > > We are attempting to switch our projects over from ejb+ear packaging to war > packaging. But we have a series of custom maven artifact types (e.g. xsd, > wsdl), and these don't get copied to the WEB-INF/lib folder. > For the maven-ear-plugin there was the option to configure [custom artifact > types|http://maven.apache.org/plugins/maven-ear-plugin/modules.html#Custom_Artifact_Types]. > It doesn't look like such a thing exists for the maven-war-plugin? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-413) Upgrade xstream to 1.4.10
[ https://issues.apache.org/jira/browse/MWAR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421765#comment-16421765 ] Hudson commented on MWAR-413: - Build succeeded in Jenkins: Maven TLP » maven-war-plugin » master #10 See https://builds.apache.org/job/maven-box/job/maven-war-plugin/job/master/10/ > Upgrade xstream to 1.4.10 > - > > Key: MWAR-413 > URL: https://issues.apache.org/jira/browse/MWAR-413 > Project: Maven WAR Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MWAR-413) Upgrade xstream to 1.4.10
[ https://issues.apache.org/jira/browse/MWAR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MWAR-413. Resolution: Fixed Done in [434c91751ab4b8bc6d77e6e3d1fa9267068410d6|https://gitbox.apache.org/repos/asf?p=maven-war-plugin.git;a=commitdiff;h=434c91751ab4b8bc6d77e6e3d1fa9267068410d6] > Upgrade xstream to 1.4.10 > - > > Key: MWAR-413 > URL: https://issues.apache.org/jira/browse/MWAR-413 > Project: Maven WAR Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] raphw opened a new pull request #1: Update ASM to latest version
raphw opened a new pull request #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1 Update to ASM 6.1.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
[GitHub] struberg commented on issue #1: Update ASM to latest version
struberg commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377816090 is probably related to MSHADE-275 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
[GitHub] khmarbaise commented on issue #1: Update ASM to latest version
khmarbaise commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377816221 Exactly it is... 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] (SUREFIRE-1487) ParallelComputerBuilderTest fails on overloaded system because internal delay are shorter than blocking time of JVM
[
https://issues.apache.org/jira/browse/SUREFIRE-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1487.
--
Resolution: Fixed
Assignee: Tibor Digana
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=882cbb62c084442bd2540a0747295f9908e90e63
> ParallelComputerBuilderTest fails on overloaded system because internal delay
> are shorter than blocking time of JVM
> ---
>
> Key: SUREFIRE-1487
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1487
> Project: Maven Surefire
> Issue Type: Task
> Components: Junit 4.7+ (parallel) support
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> The delays are 500 ms and variations 250 ms.
> The JVM was blocked for 675 ms.
> From these measurements, the new delay should be 3-times longer at least.
> [windows] Tests in error:
> [windows]
> separatePoolsWithSuiteAndSequentialClasses(org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilderTest):
> (..)
> [windows]
> parallelMethodsReuseOneOrTwoThreads(org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilderTest):
> (..)
> [windows]
> suiteAndClassInOnePool(org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilderTest):
> (..)
> suiteAndClassInOnePool:
> Expected: (between <1450L> and <1750L> or between <1950L> and <2250L> or
> between <2450L> and <2750L>)
> but: was <3175L>
> parallelMethodsReuseOneOrTwoThreads:
> Expected: between <1450L> and <1750L>
> but: was <1837L>
> separatePoolsWithSuiteAndSequentialClasses:
> Expected: between <1450L> and <1750L>
> but: was <3562L>
> In this case the JVM was blocked for 2.062 second and the delays should be 9
> times longer. The test {{ParallelComputerBuilderTest}} has small number of
> tests, so we can prolong the delays 10 times.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] khmarbaise commented on issue #1: Update ASM to latest version
khmarbaise commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377816221 Exactly it is...The problem is at the moment that org.vafer:jdependency contains an older version of ASM shaded in the jar which means at the moment that we can't overwrite the dependency nor replace it simple...also excluding does not help here...See https://github.com/tcurdt/jdependency/issues/13 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
[GitHub] raphw commented on issue #1: Update ASM to latest version
raphw commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377817912 I did not know that but I just overruled the dependencies in my build within the tag and I can now successfully build on Java 10. I had to do the same for the maven-plugin-plugin. 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] (SCM-878) .AbstractConsumer#parseDate() logs wrong locale in case of ParseException
Michael Osipov created SCM-878:
--
Summary: .AbstractConsumer#parseDate() logs wrong locale in case
of ParseException
Key: SCM-878
URL: https://issues.apache.org/jira/browse/SCM-878
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-api
Affects Versions: 1.9.5
Environment: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
Java version: 10, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk-10
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 1.9.6
While testing SCM with JDK 10 the Jazz provider fails with:
{noformat}
skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
at java.base/java.text.DateFormat.parse(DateFormat.java:395)
at
org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
at
org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
Looking th the Jazz test code, no locale is actually passed, so the default
locale is used.
The issue is rooted in the catch warn statement (in
{{org.apache.maven.scm.util.AbstractConsumer.parseDate(String, String, String,
Locale)}}) which assumes that a passed null locale defaults to
{{Locale.ENGLISH}}. It shall display {{Locale.getDefault()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCM-878) .AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
[
https://issues.apache.org/jira/browse/SCM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SCM-878:
---
Description:
While testing SCM with JDK 10 the Jazz provider fails with:
{noformat}
skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
at java.base/java.text.DateFormat.parse(DateFormat.java:395)
at
org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
at
org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
Looking at the Jazz test code no locale is actually passed, so the default
locale is used.
The issue is rooted in the catch warn statement (in
{{org.apache.maven.scm.util.AbstractConsumer.parseDate(String, String, String,
Locale)}}) which assumes that a passed null locale defaults to
{{Locale.ENGLISH}}. It shall display {{Locale.getDefault()}}.
was:
While testing SCM with JDK 10 the Jazz provider fails with:
{noformat}
skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
at java.base/java.text.DateFormat.parse(DateFormat.java:395)
at
org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
at
org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
Looking th the Jazz test code, no locale is actually passed, so the default
locale is used.
The issue is rooted in the catch warn statement (in
{{org.apache.maven.scm.util.AbstractConsumer.parseDate(String, String, String,
Locale)}}) which assumes that a passed null locale defaults to
{{Locale.ENGLISH}}. It shall display {{Locale.getDefault()}}.
> .AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
> ---
>
> Key: SCM-878
> URL: https://issues.apache.org/jira/browse/SCM-878
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-api
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> While testing SCM with JDK 10 the Jazz provider fails with:
> {noformat}
> skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
> date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
> java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
> at java.base/java.text.DateFormat.parse(DateFormat.java:395)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
> Looking at the Jazz test code no locale is actually passed,
[jira] [Updated] (SCM-878) .AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
[
https://issues.apache.org/jira/browse/SCM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SCM-878:
---
Summary: .AbstractConsumer#parseDate() logs wrong locale in case of a
ParseException (was: .AbstractConsumer#parseDate() logs wrong locale in case
of ParseException)
> .AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
> ---
>
> Key: SCM-878
> URL: https://issues.apache.org/jira/browse/SCM-878
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-api
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> While testing SCM with JDK 10 the Jazz provider fails with:
> {noformat}
> skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
> date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
> java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
> at java.base/java.text.DateFormat.parse(DateFormat.java:395)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
> Looking th the Jazz test code, no locale is actually passed, so the default
> locale is used.
> The issue is rooted in the catch warn statement (in
> {{org.apache.maven.scm.util.AbstractConsumer.parseDate(String, String,
> String, Locale)}}) which assumes that a passed null locale defaults to
> {{Locale.ENGLISH}}. It shall display {{Locale.getDefault()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MSHADE-279) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MSHADE-279: -- Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MSHADE-279 URL: https://issues.apache.org/jira/browse/MSHADE-279 Project: Maven Shade Plugin Issue Type: Dependency upgrade Affects Versions: 3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] khmarbaise commented on issue #1: Update ASM to latest version
khmarbaise commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377819013 Have you run the IT's ? 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] (MSHADE-280) Upgrade jdom 1.1.3 to jdom2 2.0.6
Karl Heinz Marbaise created MSHADE-280: -- Summary: Upgrade jdom 1.1.3 to jdom2 2.0.6 Key: MSHADE-280 URL: https://issues.apache.org/jira/browse/MSHADE-280 Project: Maven Shade Plugin Issue Type: Dependency upgrade Affects Versions: 3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-279) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MSHADE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421826#comment-16421826 ] Hudson commented on MSHADE-279: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #8 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/8/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MSHADE-279 > URL: https://issues.apache.org/jira/browse/MSHADE-279 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHADE-279) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MSHADE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-279. -- Resolution: Fixed Done in [602cab789d2a33666dd56a5bf6f7385c5dc1e688|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=602cab789d2a33666dd56a5bf6f7385c5dc1e688] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MSHADE-279 > URL: https://issues.apache.org/jira/browse/MSHADE-279 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCM-878) AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
[
https://issues.apache.org/jira/browse/SCM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SCM-878:
---
Summary: AbstractConsumer#parseDate() logs wrong locale in case of a
ParseException (was: .AbstractConsumer#parseDate() logs wrong locale in case
of a ParseException)
> AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
> --
>
> Key: SCM-878
> URL: https://issues.apache.org/jira/browse/SCM-878
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-api
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> While testing SCM with JDK 10 the Jazz provider fails with:
> {noformat}
> skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
> date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
> java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
> at java.base/java.text.DateFormat.parse(DateFormat.java:395)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
> Looking at the Jazz test code no locale is actually passed, so the default
> locale is used.
> The issue is rooted in the catch warn statement (in
> {{org.apache.maven.scm.util.AbstractConsumer.parseDate(String, String,
> String, Locale)}}) which assumes that a passed null locale defaults to
> {{Locale.ENGLISH}}. It shall display {{Locale.getDefault()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-275) Maven Shade Plugin does not work under Java 10
[
https://issues.apache.org/jira/browse/MSHADE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421829#comment-16421829
]
Hudson commented on MSHADE-275:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-275 #5
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-275/5/
> Maven Shade Plugin does not work under Java 10
> --
>
> Key: MSHADE-275
> URL: https://issues.apache.org/jira/browse/MSHADE-275
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10, 64 Bit; Java 10, 64 Bit
> Maven 3.3.9, Shade Plugin 3.1.0
>Reporter: Markus Grech
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Creating an uber-jar works fine for my project under Java 9, fails under Java
> 10 with the following Exception:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> compiler: Error creating shaded jar: null: IllegalArgumentException -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project compiler: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 21 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:97)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:834)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:434)
> ... 23 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-275) Maven Shade Plugin does not work under Java 10
[
https://issues.apache.org/jira/browse/MSHADE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421831#comment-16421831
]
Hudson commented on MSHADE-275:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-275 #6
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-275/6/
> Maven Shade Plugin does not work under Java 10
> --
>
> Key: MSHADE-275
> URL: https://issues.apache.org/jira/browse/MSHADE-275
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10, 64 Bit; Java 10, 64 Bit
> Maven 3.3.9, Shade Plugin 3.1.0
>Reporter: Markus Grech
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Creating an uber-jar works fine for my project under Java 9, fails under Java
> 10 with the following Exception:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> compiler: Error creating shaded jar: null: IllegalArgumentException -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project compiler: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 21 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:97)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:834)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:434)
> ... 23 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-280) Upgrade jdom 1.1.3 to jdom2 2.0.6
[ https://issues.apache.org/jira/browse/MSHADE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421833#comment-16421833 ] Hudson commented on MSHADE-280: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #9 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/9/ > Upgrade jdom 1.1.3 to jdom2 2.0.6 > - > > Key: MSHADE-280 > URL: https://issues.apache.org/jira/browse/MSHADE-280 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHADE-280) Upgrade jdom 1.1.3 to jdom2 2.0.6
[ https://issues.apache.org/jira/browse/MSHADE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-280. -- Resolution: Fixed Done in [f487898382847b093196eee4be486b34ba92b039|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=f487898382847b093196eee4be486b34ba92b039] > Upgrade jdom 1.1.3 to jdom2 2.0.6 > - > > Key: MSHADE-280 > URL: https://issues.apache.org/jira/browse/MSHADE-280 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCM-878) AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
[
https://issues.apache.org/jira/browse/SCM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421839#comment-16421839
]
Michael Osipov commented on SCM-878:
Branch pushed, verified to work on:
{noformat}
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
Java version: 10, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk-10
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family:
"windows"{noformat}
and
{noformat}
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: /opt/apache-maven-3.5.3
Java version: 10, vendor: Azul Systems, Inc.
Java home: /usr/lib/jvm/zulu-10
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "4.11.12-200.fc25.x86_64", arch: "amd64", family:
"unix"{noformat}
tried with {{de_DE}} and {{en_AU}} which has a period after short month name in
Java 10 (not Java 8).
> AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
> --
>
> Key: SCM-878
> URL: https://issues.apache.org/jira/browse/SCM-878
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-api
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> While testing SCM with JDK 10 the Jazz provider fails with:
> {noformat}
> skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
> date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
> java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
> at java.base/java.text.DateFormat.parse(DateFormat.java:395)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
> Looking at the Jazz test code no locale is actually passed, so the default
> locale is used.
> The issue is rooted in the catch warn statement (in
> {{org.apache.maven.scm.util.AbstractConsumer.parseDate(String, String,
> String, Locale)}}) which assumes that a passed null locale defaults to
> {{Locale.ENGLISH}}. It shall display {{Locale.getDefault()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCM-879) JazzChangeLogCommandTest#testListChangesetConsumerWithTimeOnly() fails with NPE on Java 10
Michael Osipov created SCM-879:
--
Summary:
JazzChangeLogCommandTest#testListChangesetConsumerWithTimeOnly() fails with NPE
on Java 10
Key: SCM-879
URL: https://issues.apache.org/jira/browse/SCM-879
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-jazz
Affects Versions: 1.9.5
Environment: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
Java version: 10, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk-10
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 1.9.6
Surefire says:
{noformat}
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.917 sec <<<
FAILURE! - in
org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest
testListChangesetConsumerWithTimeOnly(org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest)
Time elapsed: 0.678 sec <<< ERROR!
java.lang.NullPointerException
at
org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumerWithTimeOnly(JazzChangeLogCommandTest.java:294){noformat}
The error is rooted in
{{org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(String)}}.
It does not parse the given time with {{JAZZ_TIMESTAMP_PATTERN_TIME}} *and*
{{Locale.ENGLISH}}, but relies on the system locale which will fail for
non-English parsing {{AM/PM}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCM-879) JazzChangeLogCommandTest#testListChangesetConsumerWithTimeOnly() fails with NPE on Java 10
[
https://issues.apache.org/jira/browse/SCM-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421848#comment-16421848
]
Michael Osipov commented on SCM-879:
Branch pushed, verified to work on:
{noformat}
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
Java version: 10, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk-10
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{noformat}
{noformat}
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
Java version: 1.7.0_171, vendor: Azul Systems, Inc.
Java home: C:\Program Files\Zulu\zulu-7\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{noformat}
{noformat}
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: /opt/apache-maven-3.5.3
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.fc25.x86_64/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "4.13.16-100.fc25.x86_64", arch: "amd64", family:
"unix"
{noformat}
{noformat}
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T20:49:05+01:00)
Maven home: /opt/apache-maven-3.5.3
Java version: 10, vendor: Azul Systems, Inc.
Java home: /usr/lib/jvm/zulu-10
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "4.13.16-100.fc25.x86_64", arch: "amd64", family:
"unix"
{noformat}
> JazzChangeLogCommandTest#testListChangesetConsumerWithTimeOnly() fails with
> NPE on Java 10
> --
>
> Key: SCM-879
> URL: https://issues.apache.org/jira/browse/SCM-879
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-jazz
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> Surefire says:
> {noformat}
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.917 sec <<<
> FAILURE! - in
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest
> testListChangesetConsumerWithTimeOnly(org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest)
> Time elapsed: 0.678 sec <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumerWithTimeOnly(JazzChangeLogCommandTest.java:294){noformat}
> The error is rooted in
> {{org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(String)}}.
> It does not parse the given time with {{JAZZ_TIMESTAMP_PATTERN_TIME}} *and*
> {{Locale.ENGLISH}}, but relies on the system locale which will fail for
> non-English parsing {{AM/PM}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MSHADE-281) Upgrade plexus-utils 3.1.0
Karl Heinz Marbaise created MSHADE-281: -- Summary: Upgrade plexus-utils 3.1.0 Key: MSHADE-281 URL: https://issues.apache.org/jira/browse/MSHADE-281 Project: Maven Shade Plugin Issue Type: Dependency upgrade Affects Versions: 3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPH-150) Reference of scm url to gitbox instead of github
[
https://issues.apache.org/jira/browse/MPH-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-150:
Fix Version/s: (was: 3.1.0)
> Reference of scm url to gitbox instead of github
>
>
> Key: MPH-150
> URL: https://issues.apache.org/jira/browse/MPH-150
> Project: Maven Help Plugin
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> Currently our scm entry
> {{https://github.com/apache/maven-help-plugin/tree/${project.scm.tag}}}
> points to github.
> Shouldn't we point to gitbox of Apache instead ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-150) Reference of scm url to gitbox instead of github
[
https://issues.apache.org/jira/browse/MPH-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-150:
Affects Version/s: (was: 3.1.0)
(was: 3.0.1)
> Reference of scm url to gitbox instead of github
>
>
> Key: MPH-150
> URL: https://issues.apache.org/jira/browse/MPH-150
> Project: Maven Help Plugin
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> Currently our scm entry
> {{https://github.com/apache/maven-help-plugin/tree/${project.scm.tag}}}
> points to github.
> Shouldn't we point to gitbox of Apache instead ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPH-150) Reference of scm url to gitbox instead of github
[
https://issues.apache.org/jira/browse/MPH-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MPH-150.
---
Resolution: Won't Do
> Reference of scm url to gitbox instead of github
>
>
> Key: MPH-150
> URL: https://issues.apache.org/jira/browse/MPH-150
> Project: Maven Help Plugin
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> Currently our scm entry
> {{https://github.com/apache/maven-help-plugin/tree/${project.scm.tag}}}
> points to github.
> Shouldn't we point to gitbox of Apache instead ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-150) Reference of scm url to gitbox instead of github
[
https://issues.apache.org/jira/browse/MPH-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421850#comment-16421850
]
Karl Heinz Marbaise commented on MPH-150:
-
Based on the comments we do not change this and keep the reference on Github as
before.
> Reference of scm url to gitbox instead of github
>
>
> Key: MPH-150
> URL: https://issues.apache.org/jira/browse/MPH-150
> Project: Maven Help Plugin
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> Currently our scm entry
> {{https://github.com/apache/maven-help-plugin/tree/${project.scm.tag}}}
> points to github.
> Shouldn't we point to gitbox of Apache instead ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCM-880) Maven SCM Client fails to be assembled on Java 10
Michael Osipov created SCM-880:
--
Summary: Maven SCM Client fails to be assembled on Java 10
Key: SCM-880
URL: https://issues.apache.org/jira/browse/SCM-880
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-client
Affects Versions: 1.9.5
Environment: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
Maven home: /opt/apache-maven-3.5.3
Java version: 10, vendor: Azul Systems, Inc.
Java home: /usr/lib/jvm/zulu-10
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "4.13.16-100.fc25.x86_64", arch: "amd64", family:
"unix"
Reporter: Michael Osipov
{{mvn clean verify}} fails with:
{noformat}
[INFO] Maven SCM Client ... FAILURE [ 2.317 s]
[INFO] Maven SCM Plugin 1.9.6-SNAPSHOT SUCCESS [ 16.081 s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 03:08 min
[INFO] Finished at: 2018-04-02T01:50:55+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default) on project
maven-scm-client: Execution default of goal
org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-assembly-plugin:2.6:single:
java.lang.ExceptionInInitializerError: null
[ERROR] -
[ERROR] realm = plugin>org.apache.maven.plugins:maven-assembly-plugin:2.6
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/home/mosipov/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.6/maven-assembly-plugin-2.6.jar
[ERROR] urls[1] =
file:/home/mosipov/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
[ERROR] urls[2] =
file:/home/mosipov/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
[ERROR] urls[3] =
file:/home/mosipov/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.2.1/maven-reporting-api-2.2.1.jar
[ERROR] urls[4] =
file:/home/mosipov/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.1/doxia-sink-api-1.1.jar
[ERROR] urls[5] =
file:/home/mosipov/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.1/doxia-logging-api-1.1.jar
[ERROR] urls[6] =
file:/home/mosipov/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[7] =
file:/home/mosipov/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
[ERROR] urls[8] =
file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
[ERROR] urls[9] =
file:/home/mosipov/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[ERROR] urls[10] =
file:/home/mosipov/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[11] =
file:/home/mosipov/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[12] =
file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/1.4/maven-common-artifact-filters-1.4.jar
[ERROR] urls[13] =
file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.22/plexus-interpolation-1.22.jar
[ERROR] urls[14] =
file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-archiver/3.0.1/plexus-archiver-3.0.1.jar
[ERROR] urls[15] =
file:/home/mosipov/.m2/repository/org/iq80/snappy/snappy/0.3/snappy-0.3.jar
[ERROR] urls[16] =
file:/home/mosipov/.m2/repository/org/apache/maven/shared/file-management/1.1/file-management-1.1.jar
[ERROR] urls[17] =
file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar
[ERROR] urls[18] =
file:/home/mosipov/.m2/repository/commons-io/commons-io/2.2/commons-io-2.2.jar
[ERROR] urls[19] =
file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
[ERROR] urls[20] =
file:/home/mosipov/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
[ERROR] urls[21] =
file:/home/mosipov/.m2/repository/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar
[ERROR] urls[22] =
file:/home/mosipov/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar
[ERROR] urls[23] =
file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-io/2.6/plexus-io-2.6.jar
[ERROR] urls[24] =
file:/home/mosipov/.m2/repository/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.jar
[ERROR] urls[25] =
file:/home/mosipov/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.21/plexus-utils-3
[jira] [Commented] (MSHADE-281) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MSHADE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421851#comment-16421851 ] Hudson commented on MSHADE-281: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #10 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/10/ > Upgrade plexus-utils 3.1.0 > -- > > Key: MSHADE-281 > URL: https://issues.apache.org/jira/browse/MSHADE-281 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MPH-151) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MPH-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MPH-151: --- Assignee: Karl Heinz Marbaise > Add documentation information for GitHub > > > Key: MPH-151 > URL: https://issues.apache.org/jira/browse/MPH-151 > Project: Maven Help Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MPH-146) JavaDoc Issues / Code cleanups
[
https://issues.apache.org/jira/browse/MPH-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MPH-146:
---
Assignee: Karl Heinz Marbaise
> JavaDoc Issues / Code cleanups
> --
>
> Key: MPH-146
> URL: https://issues.apache.org/jira/browse/MPH-146
> Project: Maven Help Plugin
> Issue Type: Task
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.1.0
>
>
> * Currently building JavaDoc with JDK 8 fails.
> * Each {{Version: $Id$}} should be removed
> *
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-151) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MPH-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421852#comment-16421852 ] Hudson commented on MPH-151: Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #31 See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/31/ > Add documentation information for GitHub > > > Key: MPH-151 > URL: https://issues.apache.org/jira/browse/MPH-151 > Project: Maven Help Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPH-151) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MPH-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-151. --- Resolution: Fixed Done in [14a28b5a2914a2eef40ac144e5eec741fb05bfb0|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=14a28b5a2914a2eef40ac144e5eec741fb05bfb0] > Add documentation information for GitHub > > > Key: MPH-151 > URL: https://issues.apache.org/jira/browse/MPH-151 > Project: Maven Help Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHADE-281) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MSHADE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-281. -- Resolution: Fixed Done in [6b71bded759180509d906cc71d3597d8766c65d4|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=6b71bded759180509d906cc71d3597d8766c65d4] > Upgrade plexus-utils 3.1.0 > -- > > Key: MSHADE-281 > URL: https://issues.apache.org/jira/browse/MSHADE-281 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-275) Maven Shade Plugin does not work under Java 10
[
https://issues.apache.org/jira/browse/MSHADE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421856#comment-16421856
]
Hudson commented on MSHADE-275:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-275 #12
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-275/12/
> Maven Shade Plugin does not work under Java 10
> --
>
> Key: MSHADE-275
> URL: https://issues.apache.org/jira/browse/MSHADE-275
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10, 64 Bit; Java 10, 64 Bit
> Maven 3.3.9, Shade Plugin 3.1.0
>Reporter: Markus Grech
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Creating an uber-jar works fine for my project under Java 9, fails under Java
> 10 with the following Exception:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> compiler: Error creating shaded jar: null: IllegalArgumentException -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project compiler: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 21 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:97)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:834)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:434)
> ... 23 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] raphw commented on issue #1: Update ASM to latest version
raphw commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377864297 No, I meant that I can build my project on Java 10 that uses the Maven Shade plugin which did not build because of the outdated ASM version before. 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
