[jira] [Commented] (MRESOLVER-36) SLFJ - remove LoggerFactory from dependency injection
[
https://issues.apache.org/jira/browse/MRESOLVER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530461#comment-16530461
]
Sylwester Lachiewicz commented on MRESOLVER-36:
---
i’ll look on this tommorow
> SLFJ - remove LoggerFactory from dependency injection
> -
>
> Key: MRESOLVER-36
> URL: https://issues.apache.org/jira/browse/MRESOLVER-36
> Project: Maven Resolver
> Issue Type: Improvement
> Components: resolver
>Affects Versions: Maven Artifact Resolver 1.1.1
>Reporter: Sylwester Lachiewicz
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Fix For: Maven Artifact Resolver 1.1.2
>
>
> Because Maven moved to SL4J as the primary login structure we can remove
> {{NullLoggerFactory}} class and replace {{loggerFactory}} variables with
> {{LoggerFactory.getLogger}}
> To maintain compatibility constructors will be Deprecated
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530450#comment-16530450 ] Michael Osipov commented on MRESOLVER-7: Master is currently broken. > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Assignee: Michael Osipov >Priority: Major > Fix For: Maven Artifact Resolver 1.1.2 > > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (MRESOLVER-36) SLFJ - remove LoggerFactory from dependency injection
[
https://issues.apache.org/jira/browse/MRESOLVER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MRESOLVER-36:
-
I need to reopen this issue because it causes a regression in Maven. As soon as
you update Resolver to 1.1.2-SNAPSHOT in Maven you get this:
{noformat}
[INFO] --- maven-surefire-plugin:2.20.1:test (default-test) @ maven-resolver-pro
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.maven.repository.internal.DefaultArtifactDescriptorRea
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.508 s
[ERROR] testMng5459(org.apache.maven.repository.internal.DefaultArtifactDescript
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
com.google.inject.ProvisionException: Unable to provision, see the following err
1) null returned by binding at org.eclipse.sisu.wire.LocatorWiring
but the 1st parameter of org.eclipse.aether.internal.impl.DefaultMetadataResolv
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.RepositoryEventDispatcher
for the 1st parameter of org.eclipse.aether.internal.impl.DefaultMetadataRes
while locating org.eclipse.aether.internal.impl.DefaultMetadataResolver
while locating java.lang.Object annotated with *
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.MetadataResolver
for the 1st parameter of org.apache.maven.repository.internal.DefaultVersion
at ClassRealm[plexus.core, parent: null] (via modules: org.eclipse.sisu.wire.W
while locating org.apache.maven.repository.internal.DefaultVersionResolver
while locating java.lang.Object annotated with *
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.VersionResolver
for the 1st parameter of org.eclipse.aether.internal.impl.DefaultRepositoryS
while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
while locating java.lang.Object annotated with *
1 error
role: org.eclipse.aether.RepositorySystem
roleHint:
Caused by: com.google.inject.ProvisionException:
Unable to provision, see the following errors:
1) null returned by binding at org.eclipse.sisu.wire.LocatorWiring
but the 1st parameter of org.eclipse.aether.internal.impl.DefaultMetadataResolv
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.RepositoryEventDispatcher
for the 1st parameter of org.eclipse.aether.internal.impl.DefaultMetadataRes
while locating org.eclipse.aether.internal.impl.DefaultMetadataResolver
while locating java.lang.Object annotated with *
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.MetadataResolver
for the 1st parameter of org.apache.maven.repository.internal.DefaultVersion
at ClassRealm[plexus.core, parent: null] (via modules: org.eclipse.sisu.wire.W
while locating org.apache.maven.repository.internal.DefaultVersionResolver
while locating java.lang.Object annotated with *
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.VersionResolver
for the 1st parameter of org.eclipse.aether.internal.impl.DefaultRepositoryS
while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
while locating java.lang.Object annotated with *
1 error
[INFO] Running org.apache.maven.repository.internal.DefaultModelResolverTest
[ERROR] Tests run: 10, Failures: 0, Errors: 10, Skipped: 0, Time elapsed: 0.291
[ERROR] testResolveParentThrowsUnresolvableModelExceptionWhenNotFound(org.apache
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
com.google.inject.ProvisionException: Unable to provision, see the following err
1) null returned by binding at org.eclipse.sisu.wire.LocatorWiring
but the 1st parameter of org.eclipse.aether.internal.impl.DefaultMetadataResolv
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.RepositoryEventDispatcher
for the 1st parameter of org.eclipse.aether.internal.impl.DefaultMetadataRes
while locating org.eclipse.aether.internal.impl.DefaultMetadataResolver
while locating java.lang.Object annotated with *
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.MetadataResolver
for the 1st parameter of org.apache.maven.repository.internal.DefaultVersion
at ClassRealm[plexus.core, parent: null] (via modules: org.eclipse.sisu.wire.W
while locating org.apache.maven.repository.internal.DefaultVersionResolver
while locating java.lang.Object annotated with *
at org.eclipse.sisu.wire.LocatorWiring
while locating org.eclipse.aether.impl.VersionResolver
for the 1st parameter of org.eclipse.aether.internal.impl.DefaultRepositoryS
while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
while locating
[jira] [Updated] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-7: --- Fix Version/s: Maven Artifact Resolver 1.1.2 > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Assignee: Michael Osipov >Priority: Major > Fix For: Maven Artifact Resolver 1.1.2 > > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MRESOLVER-7: -- Assignee: Michael Osipov > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Assignee: Michael Osipov >Priority: Major > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6438) Continuous Delivery friendly versions do not work on root pom's parent
[
https://issues.apache.org/jira/browse/MNG-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530302#comment-16530302
]
Karl Heinz Marbaise commented on MNG-6438:
--
If you change your pom file like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
whateverGroup
artifact
4.0.0
root
${sha1}
{code}
Than it will work. The intention was to have a version which can changed by
properties inside the reactor not always which mean in this case not for the
parent...
> Continuous Delivery friendly versions do not work on root pom's parent
> --
>
> Key: MNG-6438
> URL: https://issues.apache.org/jira/browse/MNG-6438
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/local/Cellar/maven/3.5.3/libexec
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"
>Reporter: Konrad Windszus
>Priority: Major
>
> If I use either {{${revision}}},{{${sha1}}}, or {{${changelist}}} in the root
> pom's parent version it simply does not work, even when the project is
> invoked via
> {{mvn package -Drevision=1.0}} and the according parent is available in
> version {{1.0}} in my Maven repo.
> Instead I get the following error
> {code}
> mvn package -Dsha1=1.0
> [INFO] Scanning for projects...
> Downloading from central:
> https://repo.maven.apache.org/maven2/some/test/myparent/$%7Bsha1%7D/myparent-$%7Bsha1%7D.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for some.test:root:[unknown-version]: Could
> not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project some.test:root:[unknown-version]
> (/Users/konradwindszus/Downloads/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for some.test:root:[unknown-version]:
> Could not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
> The following minimum pom can be used for testing
> {code}
>
> xmlns="http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
>
> some.test
> myparent
>
> ${sha1}
>
> root
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530193#comment-16530193
]
GW Rogde edited comment on MPIR-373 at 7/2/18 5:54 PM:
---
maven-reporting-impl:3.0.0 is from 2017, but quite a few of them are old.
Understandable if not worth effort, is it possible to mute the warning message
was (Author: geewee):
maven-reporting-impl:3.0.0 is from 2017, but quite a few of them are old.
understandable if not worth effort, is it possible to mute the warning message
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
>
[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530193#comment-16530193
]
GW Rogde commented on MPIR-373:
---
maven-reporting-impl:3.0.0 is from 2017, but quite a few of them are old.
understandable if not worth effort, is it possible to mute the warning message
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at
[jira] [Commented] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies
[
https://issues.apache.org/jira/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530067#comment-16530067
]
Antoine Morvan commented on MDEP-82:
Hi,
I'm experiencing issues also, with plugin version 3.1.1. I uploaded a small
example project to reproduce:
[https://github.com/antoine-morvan/resolve_plugin_issue]
Best.
> go-offline / resolve-plugins does not resolve all plugin dependencies
> -
>
> Key: MDEP-82
> URL: https://issues.apache.org/jira/browse/MDEP-82
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline, resolve-plugins
>Affects Versions: 2.0-alpha-4, 2.8, 2.10
> Environment: Maven 2.0.6
>Reporter: Arne Degenring
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: maven-dependency-plugin-2.3.patch, pom.xml
>
>
> The attached pom.xml is a very simple JAR project, without any direct
> dependencies or plugin dependencies.
> Start with an empty local repository, and run mvn dependency:go-offline on
> it. Some files get downloaded, but not everything that is needed for the
> build. If you run "mvn -o package" afterwards, you end up with the following
> error:
> {noformat}[ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not
> exist or no valid version could be found{noformat}
> Afterwards, even "mvn package" without the "-o" parameter does not work any
> longer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6438) Continuous Delivery friendly versions do not work on root pom's parent
[
https://issues.apache.org/jira/browse/MNG-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530062#comment-16530062
]
Konrad Windszus commented on MNG-6438:
--
[~khmarbaise] This pom.xml is enough to reproduce the issue. You don't need any
more sources (like the non-existing parent pom) because the error happens so
early in the Maven build.
> Continuous Delivery friendly versions do not work on root pom's parent
> --
>
> Key: MNG-6438
> URL: https://issues.apache.org/jira/browse/MNG-6438
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/local/Cellar/maven/3.5.3/libexec
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"
>Reporter: Konrad Windszus
>Priority: Major
>
> If I use either {{${revision}}},{{${sha1}}}, or {{${changelist}}} in the root
> pom's parent version it simply does not work, even when the project is
> invoked via
> {{mvn package -Drevision=1.0}} and the according parent is available in
> version {{1.0}} in my Maven repo.
> Instead I get the following error
> {code}
> mvn package -Dsha1=1.0
> [INFO] Scanning for projects...
> Downloading from central:
> https://repo.maven.apache.org/maven2/some/test/myparent/$%7Bsha1%7D/myparent-$%7Bsha1%7D.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for some.test:root:[unknown-version]: Could
> not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project some.test:root:[unknown-version]
> (/Users/konradwindszus/Downloads/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for some.test:root:[unknown-version]:
> Could not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
> The following minimum pom can be used for testing
> {code}
>
> xmlns="http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
>
> some.test
> myparent
>
> ${sha1}
>
> root
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-6438) Continuous Delivery friendly versions do not work on root pom's parent
[
https://issues.apache.org/jira/browse/MNG-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530062#comment-16530062
]
Konrad Windszus edited comment on MNG-6438 at 7/2/18 3:15 PM:
--
[~khmarbaise] The given pom.xml is enough to reproduce the issue. You don't
need any more sources (like the non-existing parent pom) because the error
happens so early in the Maven build.
was (Author: kwin):
[~khmarbaise] This pom.xml is enough to reproduce the issue. You don't need any
more sources (like the non-existing parent pom) because the error happens so
early in the Maven build.
> Continuous Delivery friendly versions do not work on root pom's parent
> --
>
> Key: MNG-6438
> URL: https://issues.apache.org/jira/browse/MNG-6438
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/local/Cellar/maven/3.5.3/libexec
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"
>Reporter: Konrad Windszus
>Priority: Major
>
> If I use either {{${revision}}},{{${sha1}}}, or {{${changelist}}} in the root
> pom's parent version it simply does not work, even when the project is
> invoked via
> {{mvn package -Drevision=1.0}} and the according parent is available in
> version {{1.0}} in my Maven repo.
> Instead I get the following error
> {code}
> mvn package -Dsha1=1.0
> [INFO] Scanning for projects...
> Downloading from central:
> https://repo.maven.apache.org/maven2/some/test/myparent/$%7Bsha1%7D/myparent-$%7Bsha1%7D.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for some.test:root:[unknown-version]: Could
> not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project some.test:root:[unknown-version]
> (/Users/konradwindszus/Downloads/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for some.test:root:[unknown-version]:
> Could not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
> The following minimum pom can be used for testing
> {code}
>
> xmlns="http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
>
> some.test
> myparent
>
> ${sha1}
>
> root
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6438) Continuous Delivery friendly versions do not work on root pom's parent
[
https://issues.apache.org/jira/browse/MNG-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530057#comment-16530057
]
Karl Heinz Marbaise commented on MNG-6438:
--
Can you make a full working example and attach to this issue..Thanks.
> Continuous Delivery friendly versions do not work on root pom's parent
> --
>
> Key: MNG-6438
> URL: https://issues.apache.org/jira/browse/MNG-6438
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/local/Cellar/maven/3.5.3/libexec
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"
>Reporter: Konrad Windszus
>Priority: Major
>
> If I use either {{${revision}}},{{${sha1}}}, or {{${changelist}}} in the root
> pom's parent version it simply does not work, even when the project is
> invoked via
> {{mvn package -Drevision=1.0}} and the according parent is available in
> version {{1.0}} in my Maven repo.
> Instead I get the following error
> {code}
> mvn package -Dsha1=1.0
> [INFO] Scanning for projects...
> Downloading from central:
> https://repo.maven.apache.org/maven2/some/test/myparent/$%7Bsha1%7D/myparent-$%7Bsha1%7D.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for some.test:root:[unknown-version]: Could
> not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project some.test:root:[unknown-version]
> (/Users/konradwindszus/Downloads/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for some.test:root:[unknown-version]:
> Could not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
> The following minimum pom can be used for testing
> {code}
>
> xmlns="http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
>
> some.test
> myparent
>
> ${sha1}
>
> root
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529994#comment-16529994
]
Michael Osipov commented on MPIR-373:
-
I just tested your updated POM. Same issue, warnings only. The build succeeds.
The cause is the old Velocity dependencies. ([~cla...@renegat.net]) and me are
working on a new version of VELTOOLS. Though, updating Velocity and Velocity
Tools in our entire toolchain will take months of no one helps with PRs.
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529979#comment-16529979
]
Michael Osipov edited comment on MPIR-373 at 7/2/18 2:12 PM:
-
Thanks for the {{grep}}. Those seem very, very old. I don't know whether it is
worth bothering. As for the MSITE version. If your POM does not contain any
version, it is at the discretion of the Maven version to pull any version. Here
it pulled 3.3 which will not work. Such a build is not reliable. You *must* set
the version of a plugin in use to have stable builds.
was (Author: michael-o):
Thanks for the {{grep}}. Those seem very, very old. I don't know whether it is
worth bothering. As for the MSITE version. If your POM does not contain any
version, it is at the discretion of the Maven version to pull any version. Here
it pulled 3.3 which will not work. Such a build is not reliable. You *must* set
the version of a plugin in use to have stable build.
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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)
>
[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529979#comment-16529979
]
Michael Osipov commented on MPIR-373:
-
Thanks for the {{grep}}. Those seem very, very old. I don't know whether it is
worth bothering. As for the MSITE version. If your POM does not contain any
version, it is at the discretion of the Maven version to pull any version. Here
it pulled 3.3 which will not work. Such a build is not reliable. You *must* set
the version of a plugin in use to have stable build.
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529867#comment-16529867
]
GW Rogde edited comment on MPIR-373 at 7/2/18 1:41 PM:
---
hi,
do not quite follow you on #2, as maven-site-plugin is 3.7.1.
on #1 I agree, the xml-resolver clearly contains a section that is reported as
invalid
{code:java}
deployed
{code}
I did a grep through my local maven repo and there are quite a few of these
libraries coming from central maven repo containing this status-section, and
that probably would cause the same warning message:
I have now updated pom, to use maven-reporting-impl:3.0.0 as example, but now I
see the issue is closed
{code:java}
...repository$ grep -r "deployed" --include=*.pom
asm/asm/3.0/asm-3.0.pom:deployed
commons-fileupload/commons-fileupload/1.2/commons-fileupload-1.2.pom:
deployed
commons-io/commons-io/1.3.2/commons-io-1.3.2.pom:deployed
doxia/doxia-core/1.0-alpha-4/doxia-core-1.0-alpha-4.pom:
deployed
doxia/doxia-sink-api/1.0-alpha-4/doxia-sink-api-1.0-alpha-4.pom:
deployed
org/apache/axis/axis/1.4/axis-1.4.pom:deployed
org/apache/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom:
deployed
org/apache/axis/axis-saaj/1.4/axis-saaj-1.4.pom:deployed
org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.pom:
deployed
org/apache/geronimo/specs/geronimo-jta_1.0.1B_spec/1.0.1/geronimo-jta_1.0.1B_spec-1.0.1.pom:
deployed
org/apache/maven/doxia/doxia-core/1.0-alpha-7/doxia-core-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-7/doxia-decoration-model-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-7/doxia-site-renderer-1.0-alpha-7.pom:
deployed
org/apache/maven/maven/2.0.5/maven-2.0.5.pom:deployed
org/apache/maven/maven-archiver/2.2/maven-archiver-2.2.pom:
deployed
org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom:
deployed
org/apache/maven/maven-artifact/2.0.1/maven-artifact-2.0.1.pom:
deployed
org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.pom:
deployed
org/apache/maven/maven-artifact/2.0.4/maven-artifact-2.0.4.pom:
deployed
org/apache/maven/maven-artifact/2.0.5/maven-artifact-2.0.5.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0/maven-artifact-manager-2.0.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.4/maven-artifact-manager-2.0.4.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.5/maven-artifact-manager-2.0.5.pom:
deployed
org/apache/maven/maven-core/2.0/maven-core-2.0.pom:deployed
org/apache/maven/maven-error-diagnostics/2.0/maven-error-diagnostics-2.0.pom:
deployed
org/apache/maven/maven-model/2.0/maven-model-2.0.pom:
deployed
org/apache/maven/maven-model/2.0.4/maven-model-2.0.4.pom:
deployed
org/apache/maven/maven-model/2.0.5/maven-model-2.0.5.pom:
deployed
org/apache/maven/maven-monitor/2.0/maven-monitor-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.1/maven-plugin-api-2.0.1.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.pom:
deployed
org/apache/maven/maven-plugin-descriptor/2.0/maven-plugin-descriptor-2.0.pom:
deployed
org/apache/maven/maven-plugin-parameter-documenter/2.0/maven-plugin-parameter-documenter-2.0.pom:
deployed
org/apache/maven/maven-plugin-registry/2.0/maven-plugin-registry-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0/maven-profile-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0.4/maven-profile-2.0.4.pom:
deployed
org/apache/maven/maven-profile/2.0.5/maven-profile-2.0.5.pom:
deployed
org/apache/maven/maven-project/2.0/maven-project-2.0.pom:
deployed
org/apache/maven/maven-project/2.0.4/maven-project-2.0.4.pom:
deployed
org/apache/maven/maven-project/2.0.5/maven-project-2.0.5.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.5/maven-repository-metadata-2.0.5.pom:
deployed
org/apache/maven/maven-settings/2.0/maven-settings-2.0.pom:
deployed
org/apache/maven/maven-settings/2.0.4/maven-settings-2.0.4.pom:
deployed
org/apache/maven/maven-settings/2.0.5/maven-settings-2.0.5.pom:
deployed
org/apache/maven/plugins/maven-war-plugin/2.0.2/maven-war-plugin-2.0.2.pom:
deployed
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Rogde updated MPIR-373:
--
Attachment: pom.xml
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Rogde updated MPIR-373:
--
Attachment: (was: pom.xml)
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
>
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529867#comment-16529867
]
GW Rogde edited comment on MPIR-373 at 7/2/18 1:39 PM:
---
hi,
do not quite follow you on #2, as maven-site-plugin is 3.7.1.
on #1 I agree, the xml-resolver clearly contains a section that is reported as
invalid
{code:java}
deployed
{code}
I did a grep through my local maven repo and there are quite a few of these
libraries coming from central maven repo containing this status-section, and
that probably would cause the same warning message:
I have now updated pom, to use maven-reporting-impl:3.0.0 as example
{code:java}
...repository$ grep -r "deployed" --include=*.pom
asm/asm/3.0/asm-3.0.pom:deployed
commons-fileupload/commons-fileupload/1.2/commons-fileupload-1.2.pom:
deployed
commons-io/commons-io/1.3.2/commons-io-1.3.2.pom:deployed
doxia/doxia-core/1.0-alpha-4/doxia-core-1.0-alpha-4.pom:
deployed
doxia/doxia-sink-api/1.0-alpha-4/doxia-sink-api-1.0-alpha-4.pom:
deployed
org/apache/axis/axis/1.4/axis-1.4.pom:deployed
org/apache/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom:
deployed
org/apache/axis/axis-saaj/1.4/axis-saaj-1.4.pom:deployed
org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.pom:
deployed
org/apache/geronimo/specs/geronimo-jta_1.0.1B_spec/1.0.1/geronimo-jta_1.0.1B_spec-1.0.1.pom:
deployed
org/apache/maven/doxia/doxia-core/1.0-alpha-7/doxia-core-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-7/doxia-decoration-model-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-7/doxia-site-renderer-1.0-alpha-7.pom:
deployed
org/apache/maven/maven/2.0.5/maven-2.0.5.pom:deployed
org/apache/maven/maven-archiver/2.2/maven-archiver-2.2.pom:
deployed
org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom:
deployed
org/apache/maven/maven-artifact/2.0.1/maven-artifact-2.0.1.pom:
deployed
org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.pom:
deployed
org/apache/maven/maven-artifact/2.0.4/maven-artifact-2.0.4.pom:
deployed
org/apache/maven/maven-artifact/2.0.5/maven-artifact-2.0.5.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0/maven-artifact-manager-2.0.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.4/maven-artifact-manager-2.0.4.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.5/maven-artifact-manager-2.0.5.pom:
deployed
org/apache/maven/maven-core/2.0/maven-core-2.0.pom:deployed
org/apache/maven/maven-error-diagnostics/2.0/maven-error-diagnostics-2.0.pom:
deployed
org/apache/maven/maven-model/2.0/maven-model-2.0.pom:
deployed
org/apache/maven/maven-model/2.0.4/maven-model-2.0.4.pom:
deployed
org/apache/maven/maven-model/2.0.5/maven-model-2.0.5.pom:
deployed
org/apache/maven/maven-monitor/2.0/maven-monitor-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.1/maven-plugin-api-2.0.1.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.pom:
deployed
org/apache/maven/maven-plugin-descriptor/2.0/maven-plugin-descriptor-2.0.pom:
deployed
org/apache/maven/maven-plugin-parameter-documenter/2.0/maven-plugin-parameter-documenter-2.0.pom:
deployed
org/apache/maven/maven-plugin-registry/2.0/maven-plugin-registry-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0/maven-profile-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0.4/maven-profile-2.0.4.pom:
deployed
org/apache/maven/maven-profile/2.0.5/maven-profile-2.0.5.pom:
deployed
org/apache/maven/maven-project/2.0/maven-project-2.0.pom:
deployed
org/apache/maven/maven-project/2.0.4/maven-project-2.0.4.pom:
deployed
org/apache/maven/maven-project/2.0.5/maven-project-2.0.5.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.5/maven-repository-metadata-2.0.5.pom:
deployed
org/apache/maven/maven-settings/2.0/maven-settings-2.0.pom:
deployed
org/apache/maven/maven-settings/2.0.4/maven-settings-2.0.4.pom:
deployed
org/apache/maven/maven-settings/2.0.5/maven-settings-2.0.5.pom:
deployed
org/apache/maven/plugins/maven-war-plugin/2.0.2/maven-war-plugin-2.0.2.pom:
deployed
org/apache/maven/reporting/maven-reporting-api/2.0/maven-reporting-api-2.0.pom:
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Rogde updated MPIR-373:
--
Attachment: (was: pom.xml)
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Rogde updated MPIR-373:
--
Attachment: pom.xml
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529867#comment-16529867
]
GW Rogde edited comment on MPIR-373 at 7/2/18 1:17 PM:
---
hi,
do not quite follow you on #2, as maven-site-plugin is 3.7.1.
on #1 I agree, the xml-resolver clearly contains a section that is reported as
invalid
{code:java}
deployed
{code}
I did a grep through my local maven repo and there are quite a few of these
libraries coming from central maven repo containing this status-section, and
that probably would cause the same warning message:
{code:java}
...repository$ grep -r "deployed" --include=*.pom
asm/asm/3.0/asm-3.0.pom:deployed
commons-fileupload/commons-fileupload/1.2/commons-fileupload-1.2.pom:
deployed
commons-io/commons-io/1.3.2/commons-io-1.3.2.pom:deployed
doxia/doxia-core/1.0-alpha-4/doxia-core-1.0-alpha-4.pom:
deployed
doxia/doxia-sink-api/1.0-alpha-4/doxia-sink-api-1.0-alpha-4.pom:
deployed
org/apache/axis/axis/1.4/axis-1.4.pom:deployed
org/apache/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom:
deployed
org/apache/axis/axis-saaj/1.4/axis-saaj-1.4.pom:deployed
org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.pom:
deployed
org/apache/geronimo/specs/geronimo-jta_1.0.1B_spec/1.0.1/geronimo-jta_1.0.1B_spec-1.0.1.pom:
deployed
org/apache/maven/doxia/doxia-core/1.0-alpha-7/doxia-core-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-7/doxia-decoration-model-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-7/doxia-site-renderer-1.0-alpha-7.pom:
deployed
org/apache/maven/maven/2.0.5/maven-2.0.5.pom:deployed
org/apache/maven/maven-archiver/2.2/maven-archiver-2.2.pom:
deployed
org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom:
deployed
org/apache/maven/maven-artifact/2.0.1/maven-artifact-2.0.1.pom:
deployed
org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.pom:
deployed
org/apache/maven/maven-artifact/2.0.4/maven-artifact-2.0.4.pom:
deployed
org/apache/maven/maven-artifact/2.0.5/maven-artifact-2.0.5.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0/maven-artifact-manager-2.0.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.4/maven-artifact-manager-2.0.4.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.5/maven-artifact-manager-2.0.5.pom:
deployed
org/apache/maven/maven-core/2.0/maven-core-2.0.pom:deployed
org/apache/maven/maven-error-diagnostics/2.0/maven-error-diagnostics-2.0.pom:
deployed
org/apache/maven/maven-model/2.0/maven-model-2.0.pom:
deployed
org/apache/maven/maven-model/2.0.4/maven-model-2.0.4.pom:
deployed
org/apache/maven/maven-model/2.0.5/maven-model-2.0.5.pom:
deployed
org/apache/maven/maven-monitor/2.0/maven-monitor-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.1/maven-plugin-api-2.0.1.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.pom:
deployed
org/apache/maven/maven-plugin-descriptor/2.0/maven-plugin-descriptor-2.0.pom:
deployed
org/apache/maven/maven-plugin-parameter-documenter/2.0/maven-plugin-parameter-documenter-2.0.pom:
deployed
org/apache/maven/maven-plugin-registry/2.0/maven-plugin-registry-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0/maven-profile-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0.4/maven-profile-2.0.4.pom:
deployed
org/apache/maven/maven-profile/2.0.5/maven-profile-2.0.5.pom:
deployed
org/apache/maven/maven-project/2.0/maven-project-2.0.pom:
deployed
org/apache/maven/maven-project/2.0.4/maven-project-2.0.4.pom:
deployed
org/apache/maven/maven-project/2.0.5/maven-project-2.0.5.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.5/maven-repository-metadata-2.0.5.pom:
deployed
org/apache/maven/maven-settings/2.0/maven-settings-2.0.pom:
deployed
org/apache/maven/maven-settings/2.0.4/maven-settings-2.0.4.pom:
deployed
org/apache/maven/maven-settings/2.0.5/maven-settings-2.0.5.pom:
deployed
org/apache/maven/plugins/maven-war-plugin/2.0.2/maven-war-plugin-2.0.2.pom:
deployed
org/apache/maven/reporting/maven-reporting-api/2.0/maven-reporting-api-2.0.pom:
deployed
[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529867#comment-16529867
]
GW Rogde commented on MPIR-373:
---
hi,
do not quite follow you on #2, as maven-site-plugin is 3.7.1.
on #1 I agree, the xml-resolver clearly contains a section that is reported as
invalid
{code:java}
deployed
{code}
I did a grep through my local maven repo and there are quite a few of these
libraries coming from central maven repo containing this status-section.
{code:java}
...repository$ grep -r "deployed" --include=*.pom
asm/asm/3.0/asm-3.0.pom:deployed
commons-fileupload/commons-fileupload/1.2/commons-fileupload-1.2.pom:
deployed
commons-io/commons-io/1.3.2/commons-io-1.3.2.pom:deployed
doxia/doxia-core/1.0-alpha-4/doxia-core-1.0-alpha-4.pom:
deployed
doxia/doxia-sink-api/1.0-alpha-4/doxia-sink-api-1.0-alpha-4.pom:
deployed
org/apache/axis/axis/1.4/axis-1.4.pom:deployed
org/apache/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom:
deployed
org/apache/axis/axis-saaj/1.4/axis-saaj-1.4.pom:deployed
org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.0.1/geronimo-jms_1.1_spec-1.0.1.pom:
deployed
org/apache/geronimo/specs/geronimo-jta_1.0.1B_spec/1.0.1/geronimo-jta_1.0.1B_spec-1.0.1.pom:
deployed
org/apache/maven/doxia/doxia-core/1.0-alpha-7/doxia-core-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-7/doxia-decoration-model-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/doxia-sink-api-1.0-alpha-7.pom:
deployed
org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-7/doxia-site-renderer-1.0-alpha-7.pom:
deployed
org/apache/maven/maven/2.0.5/maven-2.0.5.pom:deployed
org/apache/maven/maven-archiver/2.2/maven-archiver-2.2.pom:
deployed
org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.pom:
deployed
org/apache/maven/maven-artifact/2.0.1/maven-artifact-2.0.1.pom:
deployed
org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.pom:
deployed
org/apache/maven/maven-artifact/2.0.4/maven-artifact-2.0.4.pom:
deployed
org/apache/maven/maven-artifact/2.0.5/maven-artifact-2.0.5.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0/maven-artifact-manager-2.0.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.4/maven-artifact-manager-2.0.4.pom:
deployed
org/apache/maven/maven-artifact-manager/2.0.5/maven-artifact-manager-2.0.5.pom:
deployed
org/apache/maven/maven-core/2.0/maven-core-2.0.pom:deployed
org/apache/maven/maven-error-diagnostics/2.0/maven-error-diagnostics-2.0.pom:
deployed
org/apache/maven/maven-model/2.0/maven-model-2.0.pom:
deployed
org/apache/maven/maven-model/2.0.4/maven-model-2.0.4.pom:
deployed
org/apache/maven/maven-model/2.0.5/maven-model-2.0.5.pom:
deployed
org/apache/maven/maven-monitor/2.0/maven-monitor-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.1/maven-plugin-api-2.0.1.pom:
deployed
org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.pom:
deployed
org/apache/maven/maven-plugin-descriptor/2.0/maven-plugin-descriptor-2.0.pom:
deployed
org/apache/maven/maven-plugin-parameter-documenter/2.0/maven-plugin-parameter-documenter-2.0.pom:
deployed
org/apache/maven/maven-plugin-registry/2.0/maven-plugin-registry-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0/maven-profile-2.0.pom:
deployed
org/apache/maven/maven-profile/2.0.4/maven-profile-2.0.4.pom:
deployed
org/apache/maven/maven-profile/2.0.5/maven-profile-2.0.5.pom:
deployed
org/apache/maven/maven-project/2.0/maven-project-2.0.pom:
deployed
org/apache/maven/maven-project/2.0.4/maven-project-2.0.4.pom:
deployed
org/apache/maven/maven-project/2.0.5/maven-project-2.0.5.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0/maven-repository-metadata-2.0.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.4/maven-repository-metadata-2.0.4.pom:
deployed
org/apache/maven/maven-repository-metadata/2.0.5/maven-repository-metadata-2.0.5.pom:
deployed
org/apache/maven/maven-settings/2.0/maven-settings-2.0.pom:
deployed
org/apache/maven/maven-settings/2.0.4/maven-settings-2.0.4.pom:
deployed
org/apache/maven/maven-settings/2.0.5/maven-settings-2.0.5.pom:
deployed
org/apache/maven/plugins/maven-war-plugin/2.0.2/maven-war-plugin-2.0.2.pom:
deployed
org/apache/maven/reporting/maven-reporting-api/2.0/maven-reporting-api-2.0.pom:
deployed
org/apache/maven/reporting/maven-reporting-api/2.0.4/maven-reporting-api-2.0.4.pom:
deployed
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Rogde updated MPIR-373:
--
Attachment: pom.xml
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Rogde updated MPIR-373:
--
Attachment: (was: pom.xml)
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
>
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529798#comment-16529798
]
Michael Osipov edited comment on MPIR-373 at 7/2/18 12:20 PM:
--
There are two issued here:
1. The POM of XML Resover is invalid:
https://maven.apache.org/pom.html#Distribution_Management. {{status}} must
*not* be set manually.
2, Your MSITE version is too old.
Here is the output if MSITE is updated to 3.7.1:
{noformat}
C:\Users\osipovmi\AppData\Local\Temp>mvn site -f pom1.xml
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building mpirp-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-site-plugin:3.7.1:site (default-site) @ mpirp-test ---
[WARNING] Input file encoding has not been set, using platform encoding Cp1252,
i.e. build is platfo
rm dependent!
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:3.0.0
[INFO] 15 reports detected for maven-project-info-reports-plugin:3.0.0:
ci-management, dependencies,
dependency-info, dependency-management, distribution-management, index,
issue-management, licenses,
mailing-lists, modules, plugin-management, plugins, scm, summary, team
[INFO] Rendering site with default locale English (en)
[WARNING] No project URL defined - decoration links will not be relativized!
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.2
skin.
[INFO] Generating "Dependencies" report ---
maven-project-info-reports-plugin:3.0.0:dependencies
[WARNING] Unable to create Maven project from repository.
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing t
he POMs:
[ERROR] 'distributionManagement.status' must not be specified. @ line 36,
column 13
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:191)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:326)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepos
itory(RepositoryUtils.java:125)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderArti
factRow(DependenciesRenderer.java:799)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDepe
ndenciesForScope(DependenciesRenderer.java:749)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDepe
ndenciesForAllScopes(DependenciesRenderer.java:413)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSect
ionProjectTransitiveDependencies(DependenciesRenderer.java:438)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
(DependenciesRenderer.java:219)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer
.java:80)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.j
ava:162)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocument
Renderer.java:230)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:3
49)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:134)
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(LifecycleModuleBu
ilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(Si
ngleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
[jira] [Closed] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-373.
---
Resolution: Invalid
There are two issued here:
1. The POM XML Resover is invalid:
https://maven.apache.org/pom.html#Distribution_Management. {{status}} must
*not* be set manually.
2, Your MSITE version is too old.
Here is the output if MSITE is updated to 3.7.1:
{noformat}
C:\Users\osipovmi\AppData\Local\Temp>mvn site -f pom1.xml
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building mpirp-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-site-plugin:3.7.1:site (default-site) @ mpirp-test ---
[WARNING] Input file encoding has not been set, using platform encoding Cp1252,
i.e. build is platfo
rm dependent!
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:3.0.0
[INFO] 15 reports detected for maven-project-info-reports-plugin:3.0.0:
ci-management, dependencies,
dependency-info, dependency-management, distribution-management, index,
issue-management, licenses,
mailing-lists, modules, plugin-management, plugins, scm, summary, team
[INFO] Rendering site with default locale English (en)
[WARNING] No project URL defined - decoration links will not be relativized!
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.2
skin.
[INFO] Generating "Dependencies" report ---
maven-project-info-reports-plugin:3.0.0:dependencies
[WARNING] Unable to create Maven project from repository.
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing t
he POMs:
[ERROR] 'distributionManagement.status' must not be specified. @ line 36,
column 13
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:191)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:326)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepos
itory(RepositoryUtils.java:125)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderArti
factRow(DependenciesRenderer.java:799)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDepe
ndenciesForScope(DependenciesRenderer.java:749)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDepe
ndenciesForAllScopes(DependenciesRenderer.java:413)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSect
ionProjectTransitiveDependencies(DependenciesRenderer.java:438)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
(DependenciesRenderer.java:219)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer
.java:80)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.j
ava:162)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:251)
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocument
Renderer.java:230)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:3
49)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:134)
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(LifecycleModuleBu
ilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(Si
ngleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at
[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529785#comment-16529785
]
GW Rogde commented on MPIR-373:
---
I reduced to minor, the dependencies report is generated as expected, the
stacktrace dump is only a warning message
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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)
[jira] [Commented] (MNG-6437) Generic .uri suffix to get the URI representation of any file property
[
https://issues.apache.org/jira/browse/MNG-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529781#comment-16529781
]
Michael Osipov commented on MNG-6437:
-
I highgly second that. I have so much crap custom code in our modules and
plugins handling URIs (e.g., SCM). It is just a pain to maintain. We should
remove as much as possible and solely rely on {{.uri}} interpolation, and what
Claude recommends: {{Path#toUri()}} only.
One important thing to note is that all of these objects must be available as
{{File}}/{{Path}} first otherwise they have to converted first and
{{Uri#toString()}} must not be used, but only the ASCII-armored version.
> Generic .uri suffix to get the URI representation of any file property
> --
>
> Key: MNG-6437
> URL: https://issues.apache.org/jira/browse/MNG-6437
> Project: Maven
> Issue Type: Improvement
> Components: core
>Affects Versions: 3.5.4
>Reporter: Claude Brisson
>Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> It's impossible to properly generate, for instance, a java policy file which
> needs files URIs, using either Cargo properties and filtered config files, or
> just filtered resources.
> In both cases, the problem is the impossibility to generate proper URIs when
> expanding Maven properties (see also MNG-3760).
> The candidate feature is to add a way to explicitly request the URI when
> expanding a property by means of a {{.uri}} suffix. The underlying
> {{getUri()}} method should rely on the correct {{Path#toUri()}} and neither
> {{File#toUri()}} nor {{File#toString()}}, see the SO reference in MNG-6386.
> For instance:
> * {{${project.basedir.uri}}} instead of the broken {{${project.baseUri}}}
> (and of course fix MNG-6436 otherwise it's useless)
> * {{${project.build.directory.uri}}}
> * {{${settings.localRepository.uri}}}
> * etc
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6438) Continuous Delivery friendly versions do not work on root pom's parent
[
https://issues.apache.org/jira/browse/MNG-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated MNG-6438:
-
Affects Version/s: 3.5.3
> Continuous Delivery friendly versions do not work on root pom's parent
> --
>
> Key: MNG-6438
> URL: https://issues.apache.org/jira/browse/MNG-6438
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/local/Cellar/maven/3.5.3/libexec
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"
>Reporter: Konrad Windszus
>Priority: Major
>
> If I use either {{${revision}}},{{${sha1}}}, or {{${changelist}}} in the root
> pom's parent version it simply does not work, even when the project is
> invoked via
> {{mvn package -Drevision=1.0}} and the according parent is available in
> version {{1.0}} in my Maven repo.
> Instead I get the following error
> {code}
> mvn package -Dsha1=1.0
> [INFO] Scanning for projects...
> Downloading from central:
> https://repo.maven.apache.org/maven2/some/test/myparent/$%7Bsha1%7D/myparent-$%7Bsha1%7D.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for some.test:root:[unknown-version]: Could
> not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project some.test:root:[unknown-version]
> (/Users/konradwindszus/Downloads/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for some.test:root:[unknown-version]:
> Could not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
> The following minimum pom can be used for testing
> {code}
>
> xmlns="http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
>
> some.test
> myparent
>
> ${sha1}
>
> root
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6438) Continuous Delivery friendly versions do not work on root pom's parent
Konrad Windszus created MNG-6438:
Summary: Continuous Delivery friendly versions do not work on root
pom's parent
Key: MNG-6438
URL: https://issues.apache.org/jira/browse/MNG-6438
Project: Maven
Issue Type: Bug
Environment: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
Maven home: /usr/local/Cellar/maven/3.5.3/libexec
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"
Reporter: Konrad Windszus
If I use either {{${revision}}},{{${sha1}}}, or {{${changelist}}} in the root
pom's parent version it simply does not work, even when the project is invoked
via
{{mvn package -Drevision=1.0}} and the according parent is available in version
{{1.0}} in my Maven repo.
Instead I get the following error
{code}
mvn package -Dsha1=1.0
[INFO] Scanning for projects...
Downloading from central:
https://repo.maven.apache.org/maven2/some/test/myparent/$%7Bsha1%7D/myparent-$%7Bsha1%7D.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for some.test:root:[unknown-version]: Could
not find artifact some.test:myparent:pom:${sha1} in central
(https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
wrong local POM @ line 11, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project some.test:root:[unknown-version]
(/Users/konradwindszus/Downloads/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for some.test:root:[unknown-version]:
Could not find artifact some.test:myparent:pom:${sha1} in central
(https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
wrong local POM @ line 11, column 13 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
{code}
The following minimum pom can be used for testing
{code}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
some.test
myparent
${sha1}
root
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6437) Generic .uri suffix to get the URI representation of any file property
[
https://issues.apache.org/jira/browse/MNG-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6437:
Fix Version/s: Issues to be reviewed for 4.x
> Generic .uri suffix to get the URI representation of any file property
> --
>
> Key: MNG-6437
> URL: https://issues.apache.org/jira/browse/MNG-6437
> Project: Maven
> Issue Type: Improvement
> Components: core
>Affects Versions: 3.5.4
>Reporter: Claude Brisson
>Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> It's impossible to properly generate, for instance, a java policy file which
> needs files URIs, using either Cargo properties and filtered config files, or
> just filtered resources.
> In both cases, the problem is the impossibility to generate proper URIs when
> expanding Maven properties (see also MNG-3760).
> The candidate feature is to add a way to explicitly request the URI when
> expanding a property by means of a {{.uri}} suffix. The underlying
> {{getUri()}} method should rely on the correct {{Path#toUri()}} and neither
> {{File#toUri()}} nor {{File#toString()}}, see the SO reference in MNG-6386.
> For instance:
> * {{${project.basedir.uri}}} instead of the broken {{${project.baseUri}}}
> (and of course fix MNG-6436 otherwise it's useless)
> * {{${project.build.directory.uri}}}
> * {{${settings.localRepository.uri}}}
> * etc
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-6437) Generic .uri suffix to get the URI representation of any file property
[
https://issues.apache.org/jira/browse/MNG-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529768#comment-16529768
]
Michael Osipov edited comment on MNG-6437 at 7/2/18 11:59 AM:
--
I highgly second that. I have so much crap custom code in our modules and
plugins handling URIs (e.g., SCM). It is just a pain to maintain. We should
remove as much as possible and solely rely on {{.uri}} interpolation, and what
Claude recommends: {{Path#toUri()}} only.
was (Author: michael-o):
I highgly second that. I have so much crap custom code in our modules and
plugins handling URIs. It is just a pain to maintain. We should remove as much
as possible and solely rely on {{.uri}} interpolation, and what Claude
recommends: {{Path#toUri()}} only.
> Generic .uri suffix to get the URI representation of any file property
> --
>
> Key: MNG-6437
> URL: https://issues.apache.org/jira/browse/MNG-6437
> Project: Maven
> Issue Type: Improvement
> Components: core
>Affects Versions: 3.5.4
>Reporter: Claude Brisson
>Priority: Major
>
> It's impossible to properly generate, for instance, a java policy file which
> needs files URIs, using either Cargo properties and filtered config files, or
> just filtered resources.
> In both cases, the problem is the impossibility to generate proper URIs when
> expanding Maven properties (see also MNG-3760).
> The candidate feature is to add a way to explicitly request the URI when
> expanding a property by means of a {{.uri}} suffix. The underlying
> {{getUri()}} method should rely on the correct {{Path#toUri()}} and neither
> {{File#toUri()}} nor {{File#toString()}}, see the SO reference in MNG-6386.
> For instance:
> * {{${project.basedir.uri}}} instead of the broken {{${project.baseUri}}}
> (and of course fix MNG-6436 otherwise it's useless)
> * {{${project.build.directory.uri}}}
> * {{${settings.localRepository.uri}}}
> * etc
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6437) Generic .uri suffix to get the URI representation of any file property
[
https://issues.apache.org/jira/browse/MNG-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529768#comment-16529768
]
Michael Osipov commented on MNG-6437:
-
I highgly second that. I have so much crap custom code in our modules and
plugins handling URIs. It is just a pain to maintain. We should remove as much
as possible and solely rely on {{.uri}} interpolation, and what Claude
recommends: {{Path#toUri()}} only.
> Generic .uri suffix to get the URI representation of any file property
> --
>
> Key: MNG-6437
> URL: https://issues.apache.org/jira/browse/MNG-6437
> Project: Maven
> Issue Type: Improvement
> Components: core
>Affects Versions: 3.5.4
>Reporter: Claude Brisson
>Priority: Major
>
> It's impossible to properly generate, for instance, a java policy file which
> needs files URIs, using either Cargo properties and filtered config files, or
> just filtered resources.
> In both cases, the problem is the impossibility to generate proper URIs when
> expanding Maven properties (see also MNG-3760).
> The candidate feature is to add a way to explicitly request the URI when
> expanding a property by means of a {{.uri}} suffix. The underlying
> {{getUri()}} method should rely on the correct {{Path#toUri()}} and neither
> {{File#toUri()}} nor {{File#toString()}}, see the SO reference in MNG-6386.
> For instance:
> * {{${project.basedir.uri}}} instead of the broken {{${project.baseUri}}}
> (and of course fix MNG-6436 otherwise it's useless)
> * {{${project.build.directory.uri}}}
> * {{${settings.localRepository.uri}}}
> * etc
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529766#comment-16529766
]
Michael Osipov commented on MPIR-373:
-
Thanks, I'll have a look at it.
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
>
[jira] [Assigned] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPIR-373:
---
Assignee: Michael Osipov
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Assignee: Michael Osipov
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529447#comment-16529447
]
GW Rogde edited comment on MPIR-373 at 7/2/18 10:29 AM:
Sure, I have attached a reduced pom, to reproduce issue.
generating a dependencies-report using 3.0.0 will reproduce issue, while no
warning with 2.9
mvn project-info-reports:dependencies
was (Author: geewee):
Sure, I have attached a reduced pom, to reproduce issue.
generating a dependencies-report using 3.0.0 will reproduce issue, while no
warning with 2.9
mvn project-info-reports:dependencies
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Priority: Major
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Rogde updated MPIR-373:
--
Priority: Minor (was: Major)
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Rogde
>Priority: Minor
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
>
[jira] [Comment Edited] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529447#comment-16529447
]
GW Ro edited comment on MPIR-373 at 7/2/18 7:33 AM:
Sure, I have attached a reduced pom, to reproduce issue.
generating a dependencies-report using 3.0.0 will reproduce issue, while no
warning with 2.9
mvn project-info-reports:dependencies
was (Author: geewee):
Sure, I will prepare a reduced pom, to reproduce issue.
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Ro
>Priority: Major
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at
[jira] [Updated] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GW Ro updated MPIR-373:
---
Attachment: pom.xml
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Ro
>Priority: Major
> Attachments: pom.xml
>
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
>
[jira] [Created] (MPOM-193) Upgrade extra-enforcer-rule to 1.0-beta-9
Karl Heinz Marbaise created MPOM-193: Summary: Upgrade extra-enforcer-rule to 1.0-beta-9 Key: MPOM-193 URL: https://issues.apache.org/jira/browse/MPOM-193 Project: Maven POMs Issue Type: Dependency upgrade Components: maven Affects Versions: MAVEN-32 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: MAVEN-32 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529474#comment-16529474
]
Hudson commented on MJLINK-19:
--
Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » master #15
See
https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/master/15/
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINSTALL-143) Move checksum generation from install to deploy plugin
[ https://issues.apache.org/jira/browse/MINSTALL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529470#comment-16529470 ] Karl Heinz Marbaise commented on MINSTALL-143: -- The maven-artifact-transfer component 0.10.0 implements this. Need to wait for release of 0.10.0 > Move checksum generation from install to deploy plugin > -- > > Key: MINSTALL-143 > URL: https://issues.apache.org/jira/browse/MINSTALL-143 > Project: Maven Install Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > We should move the checksum generation from maven-install-plugin to > maven-deploy-plugin cause the checksums will only be needed as a preparation > for the transfer to a remote repository but not for an installation into a > local repository. > This needed to be done within maven-artifact-transfer component first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNGSITE-332) Changed download templates of plugins not to reference .md5 anymore
[
https://issues.apache.org/jira/browse/MNGSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNGSITE-332.
---
Resolution: Done
Assignee: Karl Heinz Marbaise
> Changed download templates of plugins not to reference .md5 anymore
> ---
>
> Key: MNGSITE-332
> URL: https://issues.apache.org/jira/browse/MNGSITE-332
> Project: Maven Project Web Site
> Issue Type: Task
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
>
> Currently we have links to md5 checksums for the plugin download pages this
> has to be changed into links to {{sha1}} and {{sha256}} instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MJLINK-19.
-
Resolution: Done
Assignee: Karl Heinz Marbaise
Done in
[88afd0d09fad3d1eb096a313a338fda697ecd7f5|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=88afd0d09fad3d1eb096a313a338fda697ecd7f5]
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MASSEMBLY-617) Add a suffix element in fileSet (same as destName in file)
[ https://issues.apache.org/jira/browse/MASSEMBLY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529460#comment-16529460 ] ASF GitHub Bot commented on MASSEMBLY-617: -- tcollignon commented on issue #4: [MASSEMBLY-617] add ability to give a fileSuffix to a FileSet URL: https://github.com/apache/maven-assembly-plugin/pull/4#issuecomment-401690432 Thx for your precious help, I will try to implement this 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 > Add a suffix element in fileSet (same as destName in file) > -- > > Key: MASSEMBLY-617 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-617 > Project: Maven Assembly Plugin > Issue Type: Wish >Affects Versions: 2.3 >Reporter: thomas collignon >Priority: Minor > > The purpose of the wish is to add a "fileSuffix" attribute in fileSet > descriptor. This will add a suffix in all files in the fileSet. > Exemple : > test.xml with TOTO suffix => testTOTO.xml (in the zip) > This is the same as destName in file descriptor but this is for all the files > in the fileSet. > I think this need to modify this jars too : > - plexus-io > - plexus-archiver > I have already made all of this modification and if you want the source code, > I can give you. > Regards -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] tcollignon commented on issue #4: [MASSEMBLY-617] add ability to give a fileSuffix to a FileSet
tcollignon commented on issue #4: [MASSEMBLY-617] add ability to give a fileSuffix to a FileSet URL: https://github.com/apache/maven-assembly-plugin/pull/4#issuecomment-401690432 Thx for your precious help, I will try to implement this This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529459#comment-16529459
]
Hudson commented on MJLINK-19:
--
Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » MJLINK-19 #4
See
https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/MJLINK-19/4/
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJLINK-21) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/MJLINK-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529458#comment-16529458 ] Hudson commented on MJLINK-21: -- Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » MJLINK-19 #4 See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/MJLINK-19/4/ > Upgrade test dependencies > - > > Key: MJLINK-21 > URL: https://issues.apache.org/jira/browse/MJLINK-21 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > > * assertj-core 2.9.1 (max cause latest for JDK 7) > * mockito-core 2.19.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-20) Upgrade plexus-archiver to 3.6.0
[ https://issues.apache.org/jira/browse/MJLINK-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529457#comment-16529457 ] Hudson commented on MJLINK-20: -- Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » MJLINK-19 #4 See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/MJLINK-19/4/ > Upgrade plexus-archiver to 3.6.0 > > > Key: MJLINK-20 > URL: https://issues.apache.org/jira/browse/MJLINK-20 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-21) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/MJLINK-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529455#comment-16529455 ] Hudson commented on MJLINK-21: -- Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » master #14 See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/master/14/ > Upgrade test dependencies > - > > Key: MJLINK-21 > URL: https://issues.apache.org/jira/browse/MJLINK-21 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > > * assertj-core 2.9.1 (max cause latest for JDK 7) > * mockito-core 2.19.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529447#comment-16529447
]
GW Ro commented on MPIR-373:
Sure, I will prepare a reduced pom, to reproduce issue.
> upgrade from 2.9 to 3.0.0 introduce additional warning issue
>
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: GW Ro
>Priority: Major
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
> 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:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 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
[jira] [Comment Edited] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath
[ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529216#comment-16529216 ] Olivier Lamy (*$^¨%`£) edited comment on SUREFIRE-1527 at 7/2/18 6:45 AM: -- [~dantran] what about a pull request or branch with the fix and a test to demonstrate the fix? was (Author: olamy): [~dantran] sounds good but what about a pull request or branch with the fix and a test to demonstrate the fix? > Surefire does not discover junit5 test case when testng is in the classpath > --- > > Key: SUREFIRE-1527 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1527 > Project: Maven Surefire > Issue Type: Improvement > Components: JUnit 5.x support, TestNG support >Affects Versions: 2.22.0 >Reporter: Dan Tran >Priority: Major > > My maven module uses junit5 but also has testng in its test classpath and my > surefire does not specify any testng.xml files > Looks like surefire only look for testng test cases -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528576#comment-16528576
]
Karl Heinz Marbaise edited comment on MJLINK-19 at 7/2/18 6:41 AM:
---
* plexus-java 0.9.10
* plexus-archiver 3.6.0 see MJLINK-20
* assertj-core 2.9.1 (max cause latest for JDK 7) see MJLINK-21
* mockito-core 2.19.0 see MJLINK-21
was (Author: khmarbaise):
* plexus-java 0.9.10
* plexus-archiver 3.6.0 see MJLINK-20
* assertj-core 2.9.1 (max cause latest for JDK 7)
* mockito-core 2.19.0
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MJLINK-21) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/MJLINK-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJLINK-21. - Resolution: Done Done in [aa68f672c8943c46d05571ad1d3fd8bf34125f3a|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=aa68f672c8943c46d05571ad1d3fd8bf34125f3a] > Upgrade test dependencies > - > > Key: MJLINK-21 > URL: https://issues.apache.org/jira/browse/MJLINK-21 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > > * assertj-core 2.9.1 (max cause latest for JDK 7) > * mockito-core 2.19.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MJLINK-21) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/MJLINK-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MJLINK-21: -- Description: * assertj-core 2.9.1 (max cause latest for JDK 7) * mockito-core 2.19.0 > Upgrade test dependencies > - > > Key: MJLINK-21 > URL: https://issues.apache.org/jira/browse/MJLINK-21 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > > * assertj-core 2.9.1 (max cause latest for JDK 7) > * mockito-core 2.19.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MJLINK-21) Upgrade test dependencies
Karl Heinz Marbaise created MJLINK-21: - Summary: Upgrade test dependencies Key: MJLINK-21 URL: https://issues.apache.org/jira/browse/MJLINK-21 Project: Maven JLink Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0-alpha-2 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0-alpha-2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MJLINK-20) Upgrade plexus-archiver to 3.6.0
[ https://issues.apache.org/jira/browse/MJLINK-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJLINK-20. - Resolution: Done Done in [aa24aceafd82ed352181a3e41626062be89b7df8|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=aa24aceafd82ed352181a3e41626062be89b7df8] > Upgrade plexus-archiver to 3.6.0 > > > Key: MJLINK-20 > URL: https://issues.apache.org/jira/browse/MJLINK-20 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-20) Upgrade plexus-archiver to 3.6.0
[ https://issues.apache.org/jira/browse/MJLINK-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529416#comment-16529416 ] Hudson commented on MJLINK-20: -- Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » master #13 See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/master/13/ > Upgrade plexus-archiver to 3.6.0 > > > Key: MJLINK-20 > URL: https://issues.apache.org/jira/browse/MJLINK-20 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
