[jira] [Commented] (MPIR-363) Upgrade dependencies to latest versions
[
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459223#comment-16459223
]
Michael Osipov commented on MPIR-363:
-
So, I have pushed a branch with some updates which do not require any actions.
These
{noformat}
maven-dependency-tree
aether-connector-wagon
maven-plugin-testing-harness
{noformat}
require changes. I do not even know wether they can be updated at all.
[~rfscholte], can they because you haven't done this with the Maven 3 upgrade.
> Upgrade dependencies to latest versions
> ---
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Sylwester Lachiewicz
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> {code}
> The following plugin updates are available:
> maven-changes-plugin ... 2.11 -> 2.12.1
> maven-jarsigner-plugin ... 1.3.2 -> 1.4
> org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5
> The following dependencies in Dependency Management have newer versions:
> org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1
> org.codehaus.plexus:plexus-component-annotations 1.6 -> 1.7.1
> The following dependencies in Dependencies have newer versions:
> commons-validator:commons-validator . 1.5.1 -> 1.6
> httpunit:httpunit ... 1.6 -> 1.6.1
> junit:junit 3.8.2 -> 4.12
> org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3
> org.apache.maven:maven-model .. 2.2.1 -> 3.5.3
> org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3
> org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2
> org.apache.maven:maven-repository-metadata 2.2.1 -> 3.5.3
> org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3
> org.apache.maven.doxia:doxia-core . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-integration-tools 1.6 -> 1.8
> org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-site-renderer 1.6 -> 1.8
> org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 3.3.0
> org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0
> org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1
> org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1
> org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0
> org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 1.7.1
> org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0
> The following dependencies in pluginManagement of plugins have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.apache.maven.shared:maven-shared-resources 1 -> 2
> The following dependencies in Plugin Dependencies have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPIR-363) Upgrade dependencies to latest versions
[
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-363:
Summary: Upgrade dependencies to latest versions (was: Update dependences
to latest versions (before 3.x))
> Upgrade dependencies to latest versions
> ---
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Sylwester Lachiewicz
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> {code}
> The following plugin updates are available:
> maven-changes-plugin ... 2.11 -> 2.12.1
> maven-jarsigner-plugin ... 1.3.2 -> 1.4
> org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5
> The following dependencies in Dependency Management have newer versions:
> org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1
> org.codehaus.plexus:plexus-component-annotations 1.6 -> 1.7.1
> The following dependencies in Dependencies have newer versions:
> commons-validator:commons-validator . 1.5.1 -> 1.6
> httpunit:httpunit ... 1.6 -> 1.6.1
> junit:junit 3.8.2 -> 4.12
> org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3
> org.apache.maven:maven-model .. 2.2.1 -> 3.5.3
> org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3
> org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2
> org.apache.maven:maven-repository-metadata 2.2.1 -> 3.5.3
> org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3
> org.apache.maven.doxia:doxia-core . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-integration-tools 1.6 -> 1.8
> org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-site-renderer 1.6 -> 1.8
> org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 3.3.0
> org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0
> org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1
> org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1
> org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0
> org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 1.7.1
> org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0
> The following dependencies in pluginManagement of plugins have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.apache.maven.shared:maven-shared-resources 1 -> 2
> The following dependencies in Plugin Dependencies have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPIR-363) Upgrade dependencies to latest versions
[
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-363:
Affects Version/s: 3.0.0
> Upgrade dependencies to latest versions
> ---
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Sylwester Lachiewicz
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> {code}
> The following plugin updates are available:
> maven-changes-plugin ... 2.11 -> 2.12.1
> maven-jarsigner-plugin ... 1.3.2 -> 1.4
> org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5
> The following dependencies in Dependency Management have newer versions:
> org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1
> org.codehaus.plexus:plexus-component-annotations 1.6 -> 1.7.1
> The following dependencies in Dependencies have newer versions:
> commons-validator:commons-validator . 1.5.1 -> 1.6
> httpunit:httpunit ... 1.6 -> 1.6.1
> junit:junit 3.8.2 -> 4.12
> org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3
> org.apache.maven:maven-model .. 2.2.1 -> 3.5.3
> org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3
> org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2
> org.apache.maven:maven-repository-metadata 2.2.1 -> 3.5.3
> org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3
> org.apache.maven.doxia:doxia-core . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-integration-tools 1.6 -> 1.8
> org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-site-renderer 1.6 -> 1.8
> org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 3.3.0
> org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0
> org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1
> org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1
> org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0
> org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 1.7.1
> org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0
> The following dependencies in pluginManagement of plugins have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.apache.maven.shared:maven-shared-resources 1 -> 2
> The following dependencies in Plugin Dependencies have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPIR-363) Upgrade dependencies to latest versions
[
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-363:
Fix Version/s: 3.0.0
> Upgrade dependencies to latest versions
> ---
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Sylwester Lachiewicz
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> {code}
> The following plugin updates are available:
> maven-changes-plugin ... 2.11 -> 2.12.1
> maven-jarsigner-plugin ... 1.3.2 -> 1.4
> org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5
> The following dependencies in Dependency Management have newer versions:
> org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1
> org.codehaus.plexus:plexus-component-annotations 1.6 -> 1.7.1
> The following dependencies in Dependencies have newer versions:
> commons-validator:commons-validator . 1.5.1 -> 1.6
> httpunit:httpunit ... 1.6 -> 1.6.1
> junit:junit 3.8.2 -> 4.12
> org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3
> org.apache.maven:maven-model .. 2.2.1 -> 3.5.3
> org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3
> org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2
> org.apache.maven:maven-repository-metadata 2.2.1 -> 3.5.3
> org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3
> org.apache.maven.doxia:doxia-core . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-integration-tools 1.6 -> 1.8
> org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-site-renderer 1.6 -> 1.8
> org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 3.3.0
> org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0
> org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1
> org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1
> org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0
> org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 1.7.1
> org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0
> The following dependencies in pluginManagement of plugins have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.apache.maven.shared:maven-shared-resources 1 -> 2
> The following dependencies in Plugin Dependencies have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MPIR-363) Update dependences to latest versions (before 3.x)
[
https://issues.apache.org/jira/browse/MPIR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPIR-363:
---
Assignee: Michael Osipov
> Update dependences to latest versions (before 3.x)
> --
>
> Key: MPIR-363
> URL: https://issues.apache.org/jira/browse/MPIR-363
> Project: Maven Project Info Reports Plugin
> Issue Type: Dependency upgrade
>Reporter: Sylwester Lachiewicz
>Assignee: Michael Osipov
>Priority: Major
>
> {code}
> The following plugin updates are available:
> maven-changes-plugin ... 2.11 -> 2.12.1
> maven-jarsigner-plugin ... 1.3.2 -> 1.4
> org.codehaus.mojo:keytool-maven-plugin . 1.0 -> 1.5
> The following dependencies in Dependency Management have newer versions:
> org.apache.maven.plugin-tools:maven-plugin-annotations ... 3.4 -> 3.5.1
> org.codehaus.plexus:plexus-component-annotations 1.6 -> 1.7.1
> The following dependencies in Dependencies have newer versions:
> commons-validator:commons-validator . 1.5.1 -> 1.6
> httpunit:httpunit ... 1.6 -> 1.6.1
> junit:junit 3.8.2 -> 4.12
> org.apache.maven:maven-artifact ... 2.2.1 -> 3.5.3
> org.apache.maven:maven-model .. 2.2.1 -> 3.5.3
> org.apache.maven:maven-plugin-api . 2.2.1 -> 3.5.3
> org.apache.maven:maven-project .. 2.2.1 -> 3.0-alpha-2
> org.apache.maven:maven-repository-metadata 2.2.1 -> 3.5.3
> org.apache.maven:maven-settings ... 2.2.1 -> 3.5.3
> org.apache.maven.doxia:doxia-core . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-decoration-model . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-integration-tools 1.6 -> 1.8
> org.apache.maven.doxia:doxia-sink-api . 1.6 -> 1.8
> org.apache.maven.doxia:doxia-site-renderer 1.6 -> 1.8
> org.apache.maven.plugin-testing:maven-plugin-testing-harness ... 1.3 -> 3.3.0
> org.apache.maven.reporting:maven-reporting-impl . 2.4 -> 3.0.0
> org.apache.maven.shared:maven-common-artifact-filters ... 1.4 -> 3.0.1
> org.apache.maven.shared:maven-dependency-tree ... 2.2 -> 3.0.1
> org.apache.maven.wagon:wagon-file .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-http-lightweight .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-provider-api .. 2.10 -> 3.0.0
> org.apache.maven.wagon:wagon-ssh ... 2.10 -> 3.0.0
> org.codehaus.plexus:plexus-container-default ... 1.0-alpha-9-stable-1 -> 1.7.1
> org.codehaus.plexus:plexus-utils . 3.0.24 -> 3.1.0
> The following dependencies in pluginManagement of plugins have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.apache.maven.shared:maven-shared-resources 1 -> 2
> The following dependencies in Plugin Dependencies have newer versions:
> org.apache.maven.doxia:doxia-core . 1.2 -> 1.8
> org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-3 -> 1.0-beta-7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-369) Drop Commons Lang for System builtins
[ https://issues.apache.org/jira/browse/MPIR-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459179#comment-16459179 ] Hudson commented on MPIR-369: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #15 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/15/ > Drop Commons Lang for System builtins > - > > Key: MPIR-369 > URL: https://issues.apache.org/jira/browse/MPIR-369 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPIR-369) Drop Commons Lang for System builtins
[ https://issues.apache.org/jira/browse/MPIR-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-369. --- Resolution: Fixed Fixed with [43871130bff656b5afbfe3d90a558114df7ac9ed|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=43871130bff656b5afbfe3d90a558114df7ac9ed]. > Drop Commons Lang for System builtins > - > > Key: MPIR-369 > URL: https://issues.apache.org/jira/browse/MPIR-369 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-345) Upgrade to Doxia 1.8
[ https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459160#comment-16459160 ] Hudson commented on MPIR-345: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #14 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/14/ > Upgrade to Doxia 1.8 > > > Key: MPIR-345 > URL: https://issues.apache.org/jira/browse/MPIR-345 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > Attachments: 1.7.log, MPIR-345.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-346) Upgrade to Doxia Sitetools 1.8.1
[ https://issues.apache.org/jira/browse/MPIR-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459161#comment-16459161 ] Hudson commented on MPIR-346: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #14 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/14/ > Upgrade to Doxia Sitetools 1.8.1 > > > Key: MPIR-346 > URL: https://issues.apache.org/jira/browse/MPIR-346 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPIR-369) Drop Commons Lang for System builtins
Michael Osipov created MPIR-369: --- Summary: Drop Commons Lang for System builtins Key: MPIR-369 URL: https://issues.apache.org/jira/browse/MPIR-369 Project: Maven Project Info Reports Plugin Issue Type: Task Affects Versions: 3.0.0 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPIR-345) Upgrade to Doxia 1.8
[ https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-345. --- Resolution: Fixed Fixed with [0c46e3f8212a34d513409a1ab26bc9d57e5c2cbe|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=0c46e3f8212a34d513409a1ab26bc9d57e5c2cbe]. > Upgrade to Doxia 1.8 > > > Key: MPIR-345 > URL: https://issues.apache.org/jira/browse/MPIR-345 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > Attachments: 1.7.log, MPIR-345.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-345) Upgrade to Doxia 1.8
[
https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459135#comment-16459135
]
ASF GitHub Bot commented on MPIR-345:
-
asfgit closed pull request #4: MPIR-345 Update Doxia and Doxia Tools to latest
version 1.8
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/4
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/pom.xml b/pom.xml
index b1de515..f001b91 100644
--- a/pom.xml
+++ b/pom.xml
@@ -117,8 +117,8 @@ under the License.
-1.6
-1.6
+1.8
+1.8
3.0
1.9.5
3.7
@@ -184,7 +184,7 @@ under the License.
org.apache.maven.doxia
doxia-integration-tools
- 1.6
+ 1.8
org.apache.maven.shared
diff --git
a/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
b/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
index b027415..dabdcae 100644
---
a/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
+++
b/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
@@ -230,10 +230,11 @@ public void execute()
Artifact defaultSkin =
siteTool.getDefaultSkinArtifact( localRepository,
project.getRemoteArtifactRepositories() );
-SiteRenderingContext siteContext =
siteRenderer.createContextForSkin( defaultSkin.getFile(), attributes,
+SiteRenderingContext siteContext =
siteRenderer.createContextForSkin( defaultSkin, attributes,
model, getName( locale ), locale );
-RenderingContext context = new RenderingContext( outputDirectory,
filename );
+RenderingContext context = new RenderingContext(
+outputDirectory, null, filename, null, null, false, null );
SiteRendererSink sink = new SiteRendererSink( context );
@@ -243,10 +244,9 @@ public void execute()
writer = new OutputStreamWriter( new FileOutputStream( new File(
outputDirectory, filename ) ), "UTF-8" );
-siteRenderer.generateDocument( writer, sink, siteContext );
+siteRenderer.mergeDocumentIntoSite( writer, sink, siteContext );
-siteRenderer.copyResources( siteContext, new File(
project.getBasedir(), "src/site/resources" ),
-outputDirectory );
+siteRenderer.copyResources( siteContext, outputDirectory );
writer.close();
writer = null;
diff --git
a/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
b/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
index f6738b4..e99087c 100644
---
a/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
+++
b/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
@@ -35,8 +35,8 @@
import org.apache.maven.artifact.Artifact;
import org.apache.maven.artifact.resolver.filter.ArtifactFilter;
import org.apache.maven.doxia.sink.Sink;
-import org.apache.maven.doxia.sink.SinkEventAttributeSet;
import org.apache.maven.doxia.sink.SinkEventAttributes;
+import org.apache.maven.doxia.sink.impl.SinkEventAttributeSet;
import org.apache.maven.model.Dependency;
import org.apache.maven.plugins.annotations.Component;
import org.apache.maven.plugins.annotations.Mojo;
@@ -237,7 +237,7 @@ protected void executeReport( Locale locale )
*
* @param locale
* @param sink
- * @param conflictingDependencyMap
+ * @param result
*/
private void generateConvergence( Locale locale, Sink sink,
DependencyAnalyzeResult result )
{
@@ -320,7 +320,7 @@ private void generateDependencyDetails( Locale locale, Sink
sink, List Upgrade to Doxia 1.8
>
>
> Key: MPIR-345
> URL: https://issues.apache.org/jira/browse/MPIR-345
> Project: Maven Project Info Reports Plugin
> Issue Type: Task
>Affects Versions: 2.9
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 1.7.log, MPIR-345.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPIR-346) Upgrade to Doxia Sitetools 1.8.1
[ https://issues.apache.org/jira/browse/MPIR-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-346. --- Resolution: Fixed Fixed with [c4a9120d76981b69b20075784f70312d74cf29b9|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=c4a9120d76981b69b20075784f70312d74cf29b9]. > Upgrade to Doxia Sitetools 1.8.1 > > > Key: MPIR-346 > URL: https://issues.apache.org/jira/browse/MPIR-346 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] asfgit closed pull request #4: MPIR-345 Update Doxia and Doxia Tools to latest version 1.8
asfgit closed pull request #4: MPIR-345 Update Doxia and Doxia Tools to latest
version 1.8
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/4
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/pom.xml b/pom.xml
index b1de515..f001b91 100644
--- a/pom.xml
+++ b/pom.xml
@@ -117,8 +117,8 @@ under the License.
-1.6
-1.6
+1.8
+1.8
3.0
1.9.5
3.7
@@ -184,7 +184,7 @@ under the License.
org.apache.maven.doxia
doxia-integration-tools
- 1.6
+ 1.8
org.apache.maven.shared
diff --git
a/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
b/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
index b027415..dabdcae 100644
---
a/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
+++
b/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java
@@ -230,10 +230,11 @@ public void execute()
Artifact defaultSkin =
siteTool.getDefaultSkinArtifact( localRepository,
project.getRemoteArtifactRepositories() );
-SiteRenderingContext siteContext =
siteRenderer.createContextForSkin( defaultSkin.getFile(), attributes,
+SiteRenderingContext siteContext =
siteRenderer.createContextForSkin( defaultSkin, attributes,
model, getName( locale ), locale );
-RenderingContext context = new RenderingContext( outputDirectory,
filename );
+RenderingContext context = new RenderingContext(
+outputDirectory, null, filename, null, null, false, null );
SiteRendererSink sink = new SiteRendererSink( context );
@@ -243,10 +244,9 @@ public void execute()
writer = new OutputStreamWriter( new FileOutputStream( new File(
outputDirectory, filename ) ), "UTF-8" );
-siteRenderer.generateDocument( writer, sink, siteContext );
+siteRenderer.mergeDocumentIntoSite( writer, sink, siteContext );
-siteRenderer.copyResources( siteContext, new File(
project.getBasedir(), "src/site/resources" ),
-outputDirectory );
+siteRenderer.copyResources( siteContext, outputDirectory );
writer.close();
writer = null;
diff --git
a/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
b/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
index f6738b4..e99087c 100644
---
a/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
+++
b/src/main/java/org/apache/maven/report/projectinfo/DependencyConvergenceReport.java
@@ -35,8 +35,8 @@
import org.apache.maven.artifact.Artifact;
import org.apache.maven.artifact.resolver.filter.ArtifactFilter;
import org.apache.maven.doxia.sink.Sink;
-import org.apache.maven.doxia.sink.SinkEventAttributeSet;
import org.apache.maven.doxia.sink.SinkEventAttributes;
+import org.apache.maven.doxia.sink.impl.SinkEventAttributeSet;
import org.apache.maven.model.Dependency;
import org.apache.maven.plugins.annotations.Component;
import org.apache.maven.plugins.annotations.Mojo;
@@ -237,7 +237,7 @@ protected void executeReport( Locale locale )
*
* @param locale
* @param sink
- * @param conflictingDependencyMap
+ * @param result
*/
private void generateConvergence( Locale locale, Sink sink,
DependencyAnalyzeResult result )
{
@@ -320,7 +320,7 @@ private void generateDependencyDetails( Locale locale, Sink
sink, List
[jira] [Commented] (MPIR-362) Dependency Management report doesn't exclude system scoped dependencies
[
https://issues.apache.org/jira/browse/MPIR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459132#comment-16459132
]
Michael Osipov commented on MPIR-362:
-
I have updated a fix branch which addresses the issue. The scope is lost in
midway. I see no reason by those dependencies should excluded at all. It
shouldn't fail at least. [~rfscholte], can you have a look at my fix. Does it
make sense?
> Dependency Management report doesn't exclude system scoped dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.9
> Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161
>Reporter: Roberto Benedetti
>Assignee: Michael Osipov
>Priority: Major
>
> I have the same issue that was closed as "Cannot Reproduce". With this pom.xml
> {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/xsd/maven-4.0.0.xsd;>
> 4.0.0
> free.test
> system-scope-test
> 0.0.1-SNAPSHOT
> jar
> http://test.free/
>
> 1.8
>
> UTF-8
>
>
>
>
> netscape
> plugin
> ${java.version}
> system
>
> ${java.home}/lib/plugin.jar
>
>
>
>
>
>
>
>
> maven-compiler-plugin
> 3.3
>
> ${java.version}
> ${java.version}
>
>
>
>
>
>
>
>
>
> maven-project-info-reports-plugin
> 2.9
>
>
>
>
> dependency-management
>
>
>
>
>
>
>
> {code}
> running {{mvn site}} will give the following warning:
> {noformat}
> [INFO] Generating "Dependency Management" report---
> maven-project-info-reports-plugin:2.9
> [WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project
> artifact: Failure to find netscape:plugin:pom:1.8 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced for project netscape:plugin:pom:1.8
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:314)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:236)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:251)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:298)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
> (DependencyManagementRenderer.java:260)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
> (DependencyManagementRenderer.java:208)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
> (DependencyManagementRenderer.java:161)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
> (DependencyManagementRenderer.java:150)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
> (DependencyManagementRenderer.java:136)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:83)
> at
>
[jira] [Assigned] (MPIR-362) Dependency Management report doesn't exclude system scoped dependencies
[
https://issues.apache.org/jira/browse/MPIR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPIR-362:
---
Assignee: Michael Osipov
> Dependency Management report doesn't exclude system scoped dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.9
> Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161
>Reporter: Roberto Benedetti
>Assignee: Michael Osipov
>Priority: Major
>
> I have the same issue that was closed as "Cannot Reproduce". With this pom.xml
> {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/xsd/maven-4.0.0.xsd;>
> 4.0.0
> free.test
> system-scope-test
> 0.0.1-SNAPSHOT
> jar
> http://test.free/
>
> 1.8
>
> UTF-8
>
>
>
>
> netscape
> plugin
> ${java.version}
> system
>
> ${java.home}/lib/plugin.jar
>
>
>
>
>
>
>
>
> maven-compiler-plugin
> 3.3
>
> ${java.version}
> ${java.version}
>
>
>
>
>
>
>
>
>
> maven-project-info-reports-plugin
> 2.9
>
>
>
>
> dependency-management
>
>
>
>
>
>
>
> {code}
> running {{mvn site}} will give the following warning:
> {noformat}
> [INFO] Generating "Dependency Management" report---
> maven-project-info-reports-plugin:2.9
> [WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project
> artifact: Failure to find netscape:plugin:pom:1.8 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced for project netscape:plugin:pom:1.8
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:314)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:236)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:251)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:298)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
> (DependencyManagementRenderer.java:260)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
> (DependencyManagementRenderer.java:208)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
> (DependencyManagementRenderer.java:161)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
> (DependencyManagementRenderer.java:150)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
> (DependencyManagementRenderer.java:136)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:83)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport
> (DependencyManagementReport.java:124)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:255)
> at
[jira] [Updated] (MPIR-362) Dependency Management report doesn't exclude system scoped dependencies
[
https://issues.apache.org/jira/browse/MPIR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-362:
Summary: Dependency Management report doesn't exclude system scoped
dependencies (was: CLONE - Dependency Management report doesn't exclude system
scoped dependencies)
> Dependency Management report doesn't exclude system scoped dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
>Affects Versions: 2.9
> Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161
>Reporter: Roberto Benedetti
>Priority: Major
>
> I have the same issue that was closed as "Cannot Reproduce". With this pom.xml
> {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/xsd/maven-4.0.0.xsd;>
> 4.0.0
> free.test
> system-scope-test
> 0.0.1-SNAPSHOT
> jar
> http://test.free/
>
> 1.8
>
> UTF-8
>
>
>
>
> netscape
> plugin
> ${java.version}
> system
>
> ${java.home}/lib/plugin.jar
>
>
>
>
>
>
>
>
> maven-compiler-plugin
> 3.3
>
> ${java.version}
> ${java.version}
>
>
>
>
>
>
>
>
>
> maven-project-info-reports-plugin
> 2.9
>
>
>
>
> dependency-management
>
>
>
>
>
>
>
> {code}
> running {{mvn site}} will give the following warning:
> {noformat}
> [INFO] Generating "Dependency Management" report---
> maven-project-info-reports-plugin:2.9
> [WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from
> repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project
> artifact: Failure to find netscape:plugin:pom:1.8 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced for project netscape:plugin:pom:1.8
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:314)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:236)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository
> (DefaultMavenProjectBuilder.java:251)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:298)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
> (DependencyManagementRenderer.java:260)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
> (DependencyManagementRenderer.java:208)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
> (DependencyManagementRenderer.java:161)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
> (DependencyManagementRenderer.java:150)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
> (DependencyManagementRenderer.java:136)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:83)
> at
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport
> (DependencyManagementReport.java:124)
> at org.apache.maven.reporting.AbstractMavenReport.generate
>
[GitHub] slachiewicz opened a new pull request #5: Java 7 code update and IDE hints fixed
slachiewicz opened a new pull request #5: Java 7 code update and IDE hints fixed URL: https://github.com/apache/maven-project-info-reports-plugin/pull/5 Please check and use code fragments if you find it helpful. - some variables was already defined in parent class - local variables has the same name as in class - small perf improvements to search for one char String vs char - unused variables removed - small javadoc fixes This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MPIR-360) Artifact IDs of managed plugins without project URL prefixed with http://
[
https://issues.apache.org/jira/browse/MPIR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459074#comment-16459074
]
Michael Osipov commented on MPIR-360:
-
Works for me with 3.0.0-SNAPSHOT from master. Can you confirm?
> Artifact IDs of managed plugins without project URL prefixed with http://
> -
>
> Key: MPIR-360
> URL: https://issues.apache.org/jira/browse/MPIR-360
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: plugin-management
>Affects Versions: 2.9
> Environment: Apache Maven 3.5.2
> (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T09:58:13+02:00)
>Reporter: Andreas Sewe
>Priority: Minor
> Attachments: project-plugin-management.png
>
>
> The attached screenshot best illustrates the problem. The managed plugin
> {{org.jacoco:jacoco-maven-plugin:0.7.9}} doesn’t define a {{project/url}} in
> its POM. Hence, the artifact ID is not rendered as a link (correct), but
> still prefixed with {{http://}} (wrong).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCM-714) mvn release:prepare fails if the command line is too long on windows
[ https://issues.apache.org/jira/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459001#comment-16459001 ] ASF GitHub Bot commented on SCM-714: michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-385517570 @rfscholte I don't see any one commit per file, but one file per add to avoid a huge add. This is how I read the patch. @murinrad Can you confirm 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 > mvn release:prepare fails if the command line is too long on windows > > > Key: SCM-714 > URL: https://issues.apache.org/jira/browse/SCM-714 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-gitexe >Affects Versions: 1.8.1 >Reporter: Felix Simmendinger >Assignee: Robert Scholte >Priority: Blocker > > The issue from SCM-697 does not solve the issue as the gitprovider is not > using the add command but the checkin command during a release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6360) Maven doesn't export org.slf4j.event.Level
[ https://issues.apache.org/jira/browse/MNG-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459002#comment-16459002 ] Michael Osipov commented on MNG-6360: - [~romain.manni-bucau], that's fine with me. > Maven doesn't export org.slf4j.event.Level > -- > > Key: MNG-6360 > URL: https://issues.apache.org/jira/browse/MNG-6360 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Blocker > > Hi > maven doesn't export org.slf4j.event package in > maven-core/src/main/resources/META-INF/maven/extension.xml so this package > from slf4j is not usable in mojos/extensions which lead to a weird > classloading for slf4j users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows
michael-o commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-385517570 @rfscholte I don't see any one commit per file, but one file per add to avoid a huge add. This is how I read the patch. @murinrad Can you confirm 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] (MSITE-822) JDK 10: Null Pointer Exception
[
https://issues.apache.org/jira/browse/MSITE-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458920#comment-16458920
]
Robert Scholte commented on MSITE-822:
--
Take a closer look
{noformat}
Caused by: java.lang.NullPointerException
at org.apache.commons.lang3.SystemUtils.isJavaVersionAtLeast
(SystemUtils.java:1626)
at
org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getJavadocExecutable
(AbstractJavadocMojo.java:3683)
{noformat}
So the most recent maven-javadoc-plugin isn't used here...
> JDK 10: Null Pointer Exception
> --
>
> Key: MSITE-822
> URL: https://issues.apache.org/jira/browse/MSITE-822
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.7
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.7
>
>
> Currently facing the following NPE while using JDK 10:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on project
> maven-acr-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> project maven-acr-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.7:site
> failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:148)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at
[jira] [Commented] (MPIR-345) Upgrade to Doxia 1.8
[ https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458912#comment-16458912 ] ASF GitHub Bot commented on MPIR-345: - slachiewicz opened a new pull request #4: MPIR-345 Update Doxia and Doxia Tools to latest version 1.8 URL: https://github.com/apache/maven-project-info-reports-plugin/pull/4 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Doxia 1.8 > > > Key: MPIR-345 > URL: https://issues.apache.org/jira/browse/MPIR-345 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > Attachments: 1.7.log, MPIR-345.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] slachiewicz opened a new pull request #4: MPIR-345 Update Doxia and Doxia Tools to latest version 1.8
slachiewicz opened a new pull request #4: MPIR-345 Update Doxia and Doxia Tools to latest version 1.8 URL: https://github.com/apache/maven-project-info-reports-plugin/pull/4 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] (SCM-714) mvn release:prepare fails if the command line is too long on windows
[ https://issues.apache.org/jira/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458873#comment-16458873 ] ASF GitHub Bot commented on SCM-714: rfscholte commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-385492915 I don't like the idea to commit per file *by default*, this would make the logging unnecessary long and therefore hard to read. If there's no other way to pass these files, we should think of a flag to allow "n files per commit", default "all". I really hope we don't need such flag. 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 > mvn release:prepare fails if the command line is too long on windows > > > Key: SCM-714 > URL: https://issues.apache.org/jira/browse/SCM-714 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-gitexe >Affects Versions: 1.8.1 >Reporter: Felix Simmendinger >Assignee: Robert Scholte >Priority: Blocker > > The issue from SCM-697 does not solve the issue as the gitprovider is not > using the add command but the checkin command during a release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] rfscholte commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows
rfscholte commented on issue #30: Fix for SCM-714: mvn release:prepare fails if the command line is too long on windows URL: https://github.com/apache/maven-scm/pull/30#issuecomment-385492915 I don't like the idea to commit per file *by default*, this would make the logging unnecessary long and therefore hard to read. If there's no other way to pass these files, we should think of a flag to allow "n files per commit", default "all". I really hope we don't need such flag. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MPIR-368) Upgrade to Java 7
[ https://issues.apache.org/jira/browse/MPIR-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458871#comment-16458871 ] Hudson commented on MPIR-368: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #13 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/13/ > Upgrade to Java 7 > - > > Key: MPIR-368 > URL: https://issues.apache.org/jira/browse/MPIR-368 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6360) Maven doesn't export org.slf4j.event.Level
[ https://issues.apache.org/jira/browse/MNG-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458862#comment-16458862 ] Romain Manni-Bucau commented on MNG-6360: - Not sure before the 15th (holidays time here ;)) but sure, should be quite trivial. > Maven doesn't export org.slf4j.event.Level > -- > > Key: MNG-6360 > URL: https://issues.apache.org/jira/browse/MNG-6360 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Blocker > > Hi > maven doesn't export org.slf4j.event package in > maven-core/src/main/resources/META-INF/maven/extension.xml so this package > from slf4j is not usable in mojos/extensions which lead to a weird > classloading for slf4j users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-361) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MPIR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458849#comment-16458849 ] Hudson commented on MPIR-361: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #12 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/12/ > Upgrade parent to 31 > > > Key: MPIR-361 > URL: https://issues.apache.org/jira/browse/MPIR-361 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSTAGE-21) Upgrade parent to 31
Karl Heinz Marbaise created MSTAGE-21: - Summary: Upgrade parent to 31 Key: MSTAGE-21 URL: https://issues.apache.org/jira/browse/MSTAGE-21 Project: Maven Stage Plugin Issue Type: Dependency upgrade Affects Versions: 3.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSTAGE-20) No implementation for org.apache.maven.plugins.stage.RepositoryCopier was bound
[
https://issues.apache.org/jira/browse/MSTAGE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458797#comment-16458797
]
Mirko Raner commented on MSTAGE-20:
---
Same problem here when running on Maven 3.5.2 :(
> No implementation for org.apache.maven.plugins.stage.RepositoryCopier was
> bound
> ---
>
> Key: MSTAGE-20
> URL: https://issues.apache.org/jira/browse/MSTAGE-20
> Project: Maven Stage Plugin
> Issue Type: Bug
>Reporter: Christian Schulz
>Priority: Major
>
> {code}
> mvn org.apache.maven.plugins:maven-stage-plugin:1.0:copy
> -Dsource=http://localhost:8084/nexus/content/repositories/releases/
> -Dtarget=http://localhost:8084/nexus/content/repositories/Test/
> {code}
> fails with
> {code}
> [INFO] --- maven-stage-plugin:1.0:copy (default-cli) @ standalone-pom ---
> [WARNING] Error injecting: org.apache.maven.plugins.stage.CopyRepositoryMojo
> com.google.inject.ProvisionException: Unable to provision, see the following
> errors:
> 1) No implementation for org.apache.maven.plugins.stage.RepositoryCopier was
> bound.
> while locating org.apache.maven.plugins.stage.CopyRepositoryMojo
> 1 error
> at
> com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1018)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1044)
> at
> org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
> at
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:54)
> at
> com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:113)
> at
> org.eclipse.sisu.bean.BeanScheduler$Activator.onProvision(BeanScheduler.java:176)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:122)
> at
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
> at
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:46)
> at
> com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1009)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1059)
> at
> com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1005)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at
> org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:82)
> at
> org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:464)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:119)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
>
[jira] [Created] (ARCHETYPE-548) Resource files without extensions are not included in archetype
Jay Guidos created ARCHETYPE-548: Summary: Resource files without extensions are not included in archetype Key: ARCHETYPE-548 URL: https://issues.apache.org/jira/browse/ARCHETYPE-548 Project: Maven Archetype Issue Type: Bug Components: Archetypes Reporter: Jay Guidos Similar to the problem resolved in ARCHETYPE-499, but the patch for that Jira only addresses source files without extensions. Resource files without extensions are still not included There are are two implementations of getUnpackagedFileSet() in FileArchesetTypeCreator, and only one of them (the one called when a file is considered a source file) has the ARCHETYPE-499 patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1255) Surefire 2.19.1 hangs before starting test execution
[
https://issues.apache.org/jira/browse/SUREFIRE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458724#comment-16458724
]
Abel Salgado Romero commented on SUREFIRE-1255:
---
I don't think so.
Setting {{threadCount}} to 4 didn't help and in our case, the issue only
happens in Windows (7, 8.1 and Appveyor).
We just use the plugin as-is, the only special thing I can think of is that we
run spock tests using {{gmaven-plugin}}.
{code:xml}
org.apache.maven.plugins
maven-surefire-plugin
2.21.0
{code}
Maybe it's a different issue from that and this?
btw, thanks a lot for your attention :)
> Surefire 2.19.1 hangs before starting test execution
>
>
> Key: SUREFIRE-1255
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1255
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.19.1
>Reporter: Maximilian Michels
>Assignee: Tibor Digana
>Priority: Critical
>
> Seeing the same error as SUREFIRE-1193 in Apache Flink builds after upgrading
> from 2.18.1 to 2.19.1. No errors, builds just gets stuck at the beginning of
> tests with no log output from the test itself, e.g.
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/137118454/log.txt
> After a couple of minutes Surefire reports
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test
> (integration-tests) on project flink-scala-shell_2.10: ExecutionException The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was /bin/sh -c cd
> /home/travis/build/mxm/flink/flink-scala-shell/target &&
> /usr/lib/jvm/java-8-oracle/jre/bin/java -Xms256m -Xmx800m -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -jar
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefirebooter372520169616801479.jar
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire8229439069544382018tmp
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire_26373613144387982724tmp
> [ERROR] -> [Help 1]
> {noformat}
> We have a a couple of test classes that suffer from this problem. Tests don't
> read from STDIN or replace it. Switching back to 2.18.1 eliminates the
> problem (Ran over 100 builds). It seems to be a race condition because it
> only occurs every once in a while, i.e. ~ 2 out of 10 builds on Travis. I
> haven't been able to reproduce the problem locally.
> More logs:
> https://s3.amazonaws.com/flink-logs-us/travis-artifacts/mxm/flink/849/849.1.tar.gz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6360) Maven doesn't export org.slf4j.event.Level
[ https://issues.apache.org/jira/browse/MNG-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458680#comment-16458680 ] Michael Osipov commented on MNG-6360: - Do you think you can create an IT for that? I would pull both. > Maven doesn't export org.slf4j.event.Level > -- > > Key: MNG-6360 > URL: https://issues.apache.org/jira/browse/MNG-6360 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Blocker > > Hi > maven doesn't export org.slf4j.event package in > maven-core/src/main/resources/META-INF/maven/extension.xml so this package > from slf4j is not usable in mojos/extensions which lead to a weird > classloading for slf4j users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MPIR-346) Upgrade to Doxia Sitetools 1.8.1
[ https://issues.apache.org/jira/browse/MPIR-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPIR-346: --- Assignee: Michael Osipov > Upgrade to Doxia Sitetools 1.8.1 > > > Key: MPIR-346 > URL: https://issues.apache.org/jira/browse/MPIR-346 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPIR-346) Upgrade to Doxia Sitetools 1.8.1
[ https://issues.apache.org/jira/browse/MPIR-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-346: Summary: Upgrade to Doxia Sitetools 1.8.1 (was: Upgrade to Doxia Sitetools 1.7) > Upgrade to Doxia Sitetools 1.8.1 > > > Key: MPIR-346 > URL: https://issues.apache.org/jira/browse/MPIR-346 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPIR-345) Upgrade to Doxia 1.8
[ https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-345: Summary: Upgrade to Doxia 1.8 (was: Upgrade to Doxia 1.7) > Upgrade to Doxia 1.8 > > > Key: MPIR-345 > URL: https://issues.apache.org/jira/browse/MPIR-345 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > Attachments: 1.7.log, MPIR-345.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MPIR-345) Upgrade to Doxia 1.8
[ https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPIR-345: --- Assignee: Michael Osipov > Upgrade to Doxia 1.8 > > > Key: MPIR-345 > URL: https://issues.apache.org/jira/browse/MPIR-345 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > Attachments: 1.7.log, MPIR-345.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6360) Maven doesn't export org.slf4j.event.Level
[ https://issues.apache.org/jira/browse/MNG-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458677#comment-16458677 ] Romain Manni-Bucau commented on MNG-6360: - Plugins dont use that package but any code using slf4j and embedded in a mojo can and would fail due to maven current setup. In such cases it is either export all or export nothing ;). > Maven doesn't export org.slf4j.event.Level > -- > > Key: MNG-6360 > URL: https://issues.apache.org/jira/browse/MNG-6360 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Blocker > > Hi > maven doesn't export org.slf4j.event package in > maven-core/src/main/resources/META-INF/maven/extension.xml so this package > from slf4j is not usable in mojos/extensions which lead to a weird > classloading for slf4j users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPIR-368) Upgrade to Java 7
[ https://issues.apache.org/jira/browse/MPIR-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-368. --- Resolution: Fixed Fixed with [c10048d12e28932294cf7cb7f8ce065b4d624182|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=c10048d12e28932294cf7cb7f8ce065b4d624182]. > Upgrade to Java 7 > - > > Key: MPIR-368 > URL: https://issues.apache.org/jira/browse/MPIR-368 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPIR-368) Upgrade to Java 7
Michael Osipov created MPIR-368: --- Summary: Upgrade to Java 7 Key: MPIR-368 URL: https://issues.apache.org/jira/browse/MPIR-368 Project: Maven Project Info Reports Plugin Issue Type: Task Affects Versions: 3.0.0 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPIR-364) Update plexus-container-default to 1.7.1 causes tests with maven-plugin-testing-harness 1.3 to fail
[
https://issues.apache.org/jira/browse/MPIR-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-364.
---
Resolution: Not A Problem
> Update plexus-container-default to 1.7.1 causes tests with
> maven-plugin-testing-harness 1.3 to fail
> ---
>
> Key: MPIR-364
> URL: https://issues.apache.org/jira/browse/MPIR-364
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Priority: Major
>
> When testing update to Doxia 1.7/1.8 i got issue.with Plexus
> To reproduce error - change version of _plexus-container-default_ to 1.7.1
> {code}
> Running org.apache.maven.report.projectinfo.CiManagementReportTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.955 sec <<<
> FAILURE! - in org.apache.maven.report.projectinfo.CiManagementReportTest
> testReport(org.apache.maven.report.projectinfo.CiManagementReportTest) Time
> elapsed: 0.684 sec <<< ERROR!
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository
> role: org.apache.maven.plugin.Mojo
> roleHint:
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.10-SNAPSHOT:cim
> classRealm: none specified
> at
> org.codehaus.plexus.DefaultComponentRegistry.getComponentManager(DefaultComponentRegistry.java:435)
> at
> org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:353)
> at
> org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:378)
> at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:205)
> at
> org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:203)
> at
> org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:133)
> at
> org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.createReportMojo(AbstractProjectInfoTestCase.java:188)
> at
> org.apache.maven.report.projectinfo.AbstractProjectInfoTestCase.generateReport(AbstractProjectInfoTestCase.java:181)
> at
> org.apache.maven.report.projectinfo.CiManagementReportTest.testReport(CiManagementReportTest.java:51)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPIR-361) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MPIR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPIR-361. --- Resolution: Fixed Fixed with [e4651da1a359b16e8c0abd40be011bd88b88bdc7|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=e4651da1a359b16e8c0abd40be011bd88b88bdc7]. > Upgrade parent to 31 > > > Key: MPIR-361 > URL: https://issues.apache.org/jira/browse/MPIR-361 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-361) Upgrade parent to 31
[
https://issues.apache.org/jira/browse/MPIR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458646#comment-16458646
]
ASF GitHub Bot commented on MPIR-361:
-
asfgit closed pull request #1: [MPIR-361] Fix checkstyle errors after chekstyle
update
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/1
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/Jenkinsfile b/Jenkinsfile
index 09ac70f..244b345 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -17,4 +17,4 @@
* under the License.
*/
-asfMavenTlpStdBuild()
+asfMavenTlpStdBuild( [ 'failFast' : false ] )
diff --git a/pom.xml b/pom.xml
index 9b7ff0e..450a0db 100644
--- a/pom.xml
+++ b/pom.xml
@@ -25,12 +25,12 @@ under the License.
maven-plugins
org.apache.maven.plugins
-30
+31
../../pom/maven/maven-plugins/pom.xml
maven-project-info-reports-plugin
- 2.10-SNAPSHOT
+ 3.0.0-SNAPSHOT
maven-plugin
Apache Maven Project Info Reports Plugin
@@ -119,10 +119,10 @@ under the License.
1.6
1.6
-2.2.1
-2.10
+3.0
1.9.5
-3.5.1
+3.7
+2.21.0
@@ -134,33 +134,35 @@ under the License.
org.apache.maven.reporting
maven-reporting-impl
- 2.4
+ 3.0.0
org.apache.maven
- maven-artifact
+ maven-compat
${mavenVersion}
+ test
+
org.apache.maven
- maven-artifact-manager
+ maven-artifact
${mavenVersion}
org.apache.maven
- maven-model
+ maven-core
${mavenVersion}
org.apache.maven
- maven-plugin-api
+ maven-model
${mavenVersion}
org.apache.maven
- maven-project
+ maven-plugin-api
${mavenVersion}
@@ -197,32 +199,12 @@ under the License.
org.apache.maven.shared
maven-common-artifact-filters
- 1.4
-
-
-
-
- org.apache.maven.wagon
- wagon-provider-api
- ${wagonVersion}
-
-
- org.apache.maven.wagon
- wagon-ssh
- ${wagonVersion}
- runtime
-
-
- org.apache.maven.wagon
- wagon-file
- ${wagonVersion}
- runtime
+ 3.0.1
- org.apache.maven.wagon
- wagon-http-lightweight
- ${wagonVersion}
- runtime
+ org.apache.maven.shared
+ maven-artifact-transfer
+ 0.9.1
@@ -348,11 +330,6 @@ under the License.
plexus-interpolation
1.24
-
- org.codehaus.plexus
- plexus-container-default
- 1.0-alpha-9-stable-1
-
@@ -364,13 +341,19 @@ under the License.
org.apache.maven.plugin-testing
maven-plugin-testing-harness
- 1.3
+ 2.1
test
junit
junit
- 3.8.2
+ 4.12
+ test
+
+
+ org.mockito
+ mockito-core
+ 2.12.0
test
@@ -385,6 +368,18 @@ under the License.
6.1.26
test
+
+ org.sonatype.aether
+ aether-connector-wagon
+ 1.7
+ test
+
+
+ org.apache.maven.wagon
+ wagon-http-lightweight
+ 2.10
+ runtime
+
@@ -428,7 +423,7 @@ under the License.
org.codehaus.mojo
keytool-maven-plugin
- 1.0
+ 1.5
${basedir}/target/jetty.jks
cn=jetty, ou=jetty, L=Unknown, ST=Unknown, o=Apache,
c=Unknown
@@ -478,7 +473,7 @@ under the License.
initialize
clean
- genkey
+ generateKeyPair
@@ -556,12 +551,16 @@ under the License.
run-its
+
+false
+
org.apache.maven.plugins
maven-invoker-plugin
+ ${maven.invoker.failure.ignore}
${project.build.directory}/it
*/pom.xml
diff --git a/src/it/full-pom/src/site/custom/project-info-reports.properties
b/src/it/full-pom/src/site/custom/project-info-reports.properties
new file mode 100644
index 000..644d0b9
--- /dev/null
+++ b/src/it/full-pom/src/site/custom/project-info-reports.properties
@@ -0,0 +1,18 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with
[GitHub] asfgit closed pull request #1: [MPIR-361] Fix checkstyle errors after chekstyle update
asfgit closed pull request #1: [MPIR-361] Fix checkstyle errors after chekstyle
update
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/1
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/Jenkinsfile b/Jenkinsfile
index 09ac70f..244b345 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -17,4 +17,4 @@
* under the License.
*/
-asfMavenTlpStdBuild()
+asfMavenTlpStdBuild( [ 'failFast' : false ] )
diff --git a/pom.xml b/pom.xml
index 9b7ff0e..450a0db 100644
--- a/pom.xml
+++ b/pom.xml
@@ -25,12 +25,12 @@ under the License.
maven-plugins
org.apache.maven.plugins
-30
+31
../../pom/maven/maven-plugins/pom.xml
maven-project-info-reports-plugin
- 2.10-SNAPSHOT
+ 3.0.0-SNAPSHOT
maven-plugin
Apache Maven Project Info Reports Plugin
@@ -119,10 +119,10 @@ under the License.
1.6
1.6
-2.2.1
-2.10
+3.0
1.9.5
-3.5.1
+3.7
+2.21.0
@@ -134,33 +134,35 @@ under the License.
org.apache.maven.reporting
maven-reporting-impl
- 2.4
+ 3.0.0
org.apache.maven
- maven-artifact
+ maven-compat
${mavenVersion}
+ test
+
org.apache.maven
- maven-artifact-manager
+ maven-artifact
${mavenVersion}
org.apache.maven
- maven-model
+ maven-core
${mavenVersion}
org.apache.maven
- maven-plugin-api
+ maven-model
${mavenVersion}
org.apache.maven
- maven-project
+ maven-plugin-api
${mavenVersion}
@@ -197,32 +199,12 @@ under the License.
org.apache.maven.shared
maven-common-artifact-filters
- 1.4
-
-
-
-
- org.apache.maven.wagon
- wagon-provider-api
- ${wagonVersion}
-
-
- org.apache.maven.wagon
- wagon-ssh
- ${wagonVersion}
- runtime
-
-
- org.apache.maven.wagon
- wagon-file
- ${wagonVersion}
- runtime
+ 3.0.1
- org.apache.maven.wagon
- wagon-http-lightweight
- ${wagonVersion}
- runtime
+ org.apache.maven.shared
+ maven-artifact-transfer
+ 0.9.1
@@ -348,11 +330,6 @@ under the License.
plexus-interpolation
1.24
-
- org.codehaus.plexus
- plexus-container-default
- 1.0-alpha-9-stable-1
-
@@ -364,13 +341,19 @@ under the License.
org.apache.maven.plugin-testing
maven-plugin-testing-harness
- 1.3
+ 2.1
test
junit
junit
- 3.8.2
+ 4.12
+ test
+
+
+ org.mockito
+ mockito-core
+ 2.12.0
test
@@ -385,6 +368,18 @@ under the License.
6.1.26
test
+
+ org.sonatype.aether
+ aether-connector-wagon
+ 1.7
+ test
+
+
+ org.apache.maven.wagon
+ wagon-http-lightweight
+ 2.10
+ runtime
+
@@ -428,7 +423,7 @@ under the License.
org.codehaus.mojo
keytool-maven-plugin
- 1.0
+ 1.5
${basedir}/target/jetty.jks
cn=jetty, ou=jetty, L=Unknown, ST=Unknown, o=Apache,
c=Unknown
@@ -478,7 +473,7 @@ under the License.
initialize
clean
- genkey
+ generateKeyPair
@@ -556,12 +551,16 @@ under the License.
run-its
+
+false
+
org.apache.maven.plugins
maven-invoker-plugin
+ ${maven.invoker.failure.ignore}
${project.build.directory}/it
*/pom.xml
diff --git a/src/it/full-pom/src/site/custom/project-info-reports.properties
b/src/it/full-pom/src/site/custom/project-info-reports.properties
new file mode 100644
index 000..644d0b9
--- /dev/null
+++ b/src/it/full-pom/src/site/custom/project-info-reports.properties
@@ -0,0 +1,18 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
[jira] [Commented] (MNG-6360) Maven doesn't export org.slf4j.event.Level
[ https://issues.apache.org/jira/browse/MNG-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458641#comment-16458641 ] Michael Osipov commented on MNG-6360: - Why do our plugins work? What do I miss, can you show an example? > Maven doesn't export org.slf4j.event.Level > -- > > Key: MNG-6360 > URL: https://issues.apache.org/jira/browse/MNG-6360 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Blocker > > Hi > maven doesn't export org.slf4j.event package in > maven-core/src/main/resources/META-INF/maven/extension.xml so this package > from slf4j is not usable in mojos/extensions which lead to a weird > classloading for slf4j users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SUREFIRE-1502) Forking fails on OS/X
[
https://issues.apache.org/jira/browse/SUREFIRE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1502.
--
Resolution: Duplicate
> Forking fails on OS/X
> -
>
> Key: SUREFIRE-1502
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1502
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
>Affects Versions: 2.20.1, 2.21.0
> Environment: OS/X 10.13.3
> Java 1.8.0_162
>Reporter: Larry West
>Assignee: Tibor Digana
>Priority: Major
> Attachments: surefire3972773662020453876tmp,
> surefire_06790995305937656848tmp
>
>
> This is very similar to SUREFIRE-1422, but is still present _intermittently_
> on version 2.21.0 as well as 2.20.1. It was not present on 2.19.1.
> The symptom is that all tests run fine (the reports are there), but as soon
> as they do, there is an error:
> {noformat}
> The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> ...
> Process Exit Code: 0
> {noformat}
> This of course fails the build.
> This occurs on roughly half the builds (with 2.21.0, at least).
> Maven version 3.5.3. Java 1.8.0_162. OS/X 10.13.3.
> h5. Selected output from mvn -X
> {noformat}
> [DEBUG] Forking command line: /bin/sh -c cd /Users/lwest/git/caas/jsk-cc &&
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java
> -jar
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
> /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> {noformat}
> ... then, after all the tests have run, successfully, it reports failure:
> {noformat}
> Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> Command was /bin/sh -c cd /Users/lwest/git/caas/jsk-cc &&
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java
> -jar
> /Users/lwest/git/caas/jsk-cc/target/surefire/surefirebooter4496843559994461722.jar
> /Users/lwest/git/caas/jsk-cc/target/surefire 2018-03-16T16-08-09_300-jvmRun1
> surefire3972773662020453876tmp surefire_06790995305937656848tmp
> Process Exit Code: 0
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork
> (ForkStarter.java:671)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork
> (ForkStarter.java:533)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run
> (ForkStarter.java:278)
> at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run
> (ForkStarter.java:244)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider
> (AbstractSurefireMojo.java:1148)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked
> (AbstractSurefireMojo.java:977)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute
> (AbstractSurefireMojo.java:853)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
>
[jira] [Closed] (SUREFIRE-1503) Forked JVM immediately crashed on Unix/Linux due to new shutdown mechanism does not turn to the old shutdown mechanism
[ https://issues.apache.org/jira/browse/SUREFIRE-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1503. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=e66c64e57871ca9756fdcd9fa6fc313bf72e2e7f > Forked JVM immediately crashed on Unix/Linux due to new shutdown mechanism > does not turn to the old shutdown mechanism > -- > > Key: SUREFIRE-1503 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1503 > Project: Maven Surefire > Issue Type: Bug >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 3.0.0-M1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MNG-6400) can not work with a system dependency on a unix / mac / windows project
[
https://issues.apache.org/jira/browse/MNG-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458616#comment-16458616
]
Michael Osipov edited comment on MNG-6400 at 4/30/18 2:22 PM:
--
There are two issues here, please don't mix them. The first issue is that some
idiot at SAP decided to go against the entire ecosystem. It takes a serious
amount of work to comply with the JAR name. We suffer from the same. I'd fire
that idiot. For the second issue: the native library is not properly
registered, but this something we cannot fix. You need to populate
java.library.path. Also consider that the native lib is loaded from inside the
JCo JAR and not from your client code. Thus entire SAP crap is not portable.
The entire system scope will be removed because it is not portable
was (Author: michael-o):
There are two issues here, please don't mix them. The first issue is that some
idiot at SAP decided to go against the entire ecosystem. It takes a serious
amount of work to comply with the JAR name. We suffer from the same. I'd fire
that idiot. For the second issue: the native library is not properly
registered, but this something we cannot fix. You need to populate
java.library.path. Also consider that the native lib is loaded from inside the
JCo JAR and not from your client code. Thus entire SAP crap is not portable.
> can not work with a system dependency on a unix / mac / windows project
> ---
>
> Key: MNG-6400
> URL: https://issues.apache.org/jira/browse/MNG-6400
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.3
> Environment: Windows 07
>Reporter: Terrien Jean-Yves
>Priority: Blocker
>
> the sapjco3.jar and sapIdoc3.jar jars can not be renamed.
> to work with you have to use an addiction system
> however, a unix / windows project can not have an identical absolute path on
> both systems.
> in previous versions of maven you can set properties in .m2 / settings.xml
> and and use system
> $ \{sapidoc3}
> a warnning will be displayed.
> on version 3.5.3 it is an error.
> But that's not all because even putting the system dependency with an
> absolute path the jar is not found with the correct name
>
> de.sap
> sapjco3
> 3.0.0
> system
> D:/project-ati/libs/libsap/sapjco3.jar
>
> JCO3 code
> protected boolean registerNativeMethods(Class clazz){
> if(!initializedDLL){
> try{
> JCoRuntime.nativeLibraryPath = loadLibrary("sapjco3");
> initializedDLL = true;
> }catch(UnsatisfiedLinkError arg2){
> JCoRuntime.nativeLibraryPath = "not loaded, caused by " + arg2.toString();
> arg2.printStackTrace();
> throw arg2;
> }
> }
> return true;
> }
> java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1865)
> at java.lang.Runtime.loadLibrary0(Runtime.java:870)
> at java.lang.System.loadLibrary(System.java:1122)
> at
> com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:444)
>
> The first sap-schema-plugin is a project with sap dependencies defined by an
> absolute path or property. it compiles well.
> the second project use this plugin.
> if the plugin project is compiled whith properties
> => error absolute pah is ${sapjco3}
> if the plugin project is compiled with absolute path
> => java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
>
> the same project without change with maven 3.3.9 works perfectly
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6400) can not work with a system dependency on a unix / mac / windows project
[
https://issues.apache.org/jira/browse/MNG-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458616#comment-16458616
]
Michael Osipov commented on MNG-6400:
-
There are two issues here, please don't mix them. The first issue is that some
idiot at SAP decided to go against the entire ecosystem. It takes a serious
amount of work to comply with the JAR name. We suffer from the same. I'd fire
that idiot. For the second issue: the native library is not properly
registered, but this something we cannot fix. You need to populate
java.library.path. Also consider that the native lib is loaded from inside the
JCo JAR and not from your client code. Thus entire SAP crap is not portable.
> can not work with a system dependency on a unix / mac / windows project
> ---
>
> Key: MNG-6400
> URL: https://issues.apache.org/jira/browse/MNG-6400
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.5.3
> Environment: Windows 07
>Reporter: Terrien Jean-Yves
>Priority: Blocker
>
> the sapjco3.jar and sapIdoc3.jar jars can not be renamed.
> to work with you have to use an addiction system
> however, a unix / windows project can not have an identical absolute path on
> both systems.
> in previous versions of maven you can set properties in .m2 / settings.xml
> and and use system
> $ \{sapidoc3}
> a warnning will be displayed.
> on version 3.5.3 it is an error.
> But that's not all because even putting the system dependency with an
> absolute path the jar is not found with the correct name
>
> de.sap
> sapjco3
> 3.0.0
> system
> D:/project-ati/libs/libsap/sapjco3.jar
>
> JCO3 code
> protected boolean registerNativeMethods(Class clazz){
> if(!initializedDLL){
> try{
> JCoRuntime.nativeLibraryPath = loadLibrary("sapjco3");
> initializedDLL = true;
> }catch(UnsatisfiedLinkError arg2){
> JCoRuntime.nativeLibraryPath = "not loaded, caused by " + arg2.toString();
> arg2.printStackTrace();
> throw arg2;
> }
> }
> return true;
> }
> java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1865)
> at java.lang.Runtime.loadLibrary0(Runtime.java:870)
> at java.lang.System.loadLibrary(System.java:1122)
> at
> com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:444)
>
> The first sap-schema-plugin is a project with sap dependencies defined by an
> absolute path or property. it compiles well.
> the second project use this plugin.
> if the plugin project is compiled whith properties
> => error absolute pah is ${sapjco3}
> if the plugin project is compiled with absolute path
> => java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
>
> the same project without change with maven 3.3.9 works perfectly
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MASSEMBLY-845) MASSEMBLY-817 makes some usecases very inconvenient
[ https://issues.apache.org/jira/browse/MASSEMBLY-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458589#comment-16458589 ] Robin Björklin edited comment on MASSEMBLY-845 at 4/30/18 1:59 PM: --- I have to redact my previous statement. After a deeper dive I found the solution here: [https://maven.apache.org/plugins/maven-assembly-plugin/assembly.html] where lines 103-112 solve my problem thanks to "destName". From my perspective this issue can be closed. EDIT: I don't seem to have had the same issue as the other people in this thread. Sorry about the confusion. was (Author: rbjorklin): I have to redact my previous statement. After a deeper dive I found the solution here: [https://maven.apache.org/plugins/maven-assembly-plugin/assembly.html] where lines 103-112 solve my problem thanks to "destName". From my perspective this issue can be closed. > MASSEMBLY-817 makes some usecases very inconvenient > --- > > Key: MASSEMBLY-845 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-845 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Ulf Dreyer >Priority: Major > > The "improvement" done in MASSEMBLY-817 makes some usecases very inconvenient: > We need to create an archive with one stable name (independent of e.g. > version) so we don't have to propagate these information to a bunch of > scripts. > The general solution (i.e. Stack-overflow) refers exactly to the finalName: > [http://stackoverflow.com/questions/20697144/can-not-set-the-final-jar-name-with-maven-assembly-plugin] > *Please change finalName back to a settable property.* > It being settable does not hurt anyone satisfied with the default naming > convention but makes some usecases vastly simpler (otherwise you have to > rename the artifact using yet another plugin or propagate version info > possibly through a chain of scripts) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MASSEMBLY-845) MASSEMBLY-817 makes some usecases very inconvenient
[ https://issues.apache.org/jira/browse/MASSEMBLY-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458589#comment-16458589 ] Robin Björklin commented on MASSEMBLY-845: -- I have to redact my previous statement. After a deeper dive I found the solution here: [https://maven.apache.org/plugins/maven-assembly-plugin/assembly.html] where lines 103-112 solve my problem thanks to "destName". From my perspective this issue can be closed. > MASSEMBLY-817 makes some usecases very inconvenient > --- > > Key: MASSEMBLY-845 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-845 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Ulf Dreyer >Priority: Major > > The "improvement" done in MASSEMBLY-817 makes some usecases very inconvenient: > We need to create an archive with one stable name (independent of e.g. > version) so we don't have to propagate these information to a bunch of > scripts. > The general solution (i.e. Stack-overflow) refers exactly to the finalName: > [http://stackoverflow.com/questions/20697144/can-not-set-the-final-jar-name-with-maven-assembly-plugin] > *Please change finalName back to a settable property.* > It being settable does not hurt anyone satisfied with the default naming > convention but makes some usecases vastly simpler (otherwise you have to > rename the artifact using yet another plugin or propagate version info > possibly through a chain of scripts) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] asfgit closed pull request #3: Small link corrections
asfgit closed pull request #3: Small link corrections
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/3
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm
index c09ab8f..e47439a 100644
--- a/src/site/apt/index.apt.vm
+++ b/src/site/apt/index.apt.vm
@@ -108,9 +108,7 @@ ${project.name}
* Usage
General instructions on how to use the Project Info Reports Plugin can be
found on the {{{./usage.html}usage page}}. Some more
- specific use cases are described in the examples given below. Last but not
least, users occasionally contribute
- additional examples, tips or errata to the
-
{{{http://docs.codehaus.org/display/MAVENUSER/Project+Info+Reports+Plugin}plugin's
wiki page}}.
+ specific use cases are described in the examples given below.
In case you still have questions regarding the plugin's usage, please have a
look at the {{{./faq.html}FAQ}} and feel
free to contact the {{{./mail-lists.html}user mailing list}}. The posts to
the mailing list are archived and could
@@ -142,7 +140,7 @@ ${project.name}
* Related Links
- *
{{{http://maven.apache.org/plugins/maven-site-plugin/i18n.html}Internationalization}}
+ * {{{http://maven.apache.org/plugins/localization.html}Localization of
Plugins}}
*
{{{http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html}Skinning}}
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] (SUREFIRE-1255) Surefire 2.19.1 hangs before starting test execution
[
https://issues.apache.org/jira/browse/SUREFIRE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458386#comment-16458386
]
Tibor Digana commented on SUREFIRE-1255:
[~Abel S.Romero]
Is your problem related to this of parallel execution of tests (not forked jvms)
https://issues.apache.org/jira/browse/SUREFIRE-1430
> Surefire 2.19.1 hangs before starting test execution
>
>
> Key: SUREFIRE-1255
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1255
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.19.1
>Reporter: Maximilian Michels
>Assignee: Tibor Digana
>Priority: Critical
>
> Seeing the same error as SUREFIRE-1193 in Apache Flink builds after upgrading
> from 2.18.1 to 2.19.1. No errors, builds just gets stuck at the beginning of
> tests with no log output from the test itself, e.g.
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/137118454/log.txt
> After a couple of minutes Surefire reports
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test
> (integration-tests) on project flink-scala-shell_2.10: ExecutionException The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was /bin/sh -c cd
> /home/travis/build/mxm/flink/flink-scala-shell/target &&
> /usr/lib/jvm/java-8-oracle/jre/bin/java -Xms256m -Xmx800m -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -jar
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefirebooter372520169616801479.jar
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire8229439069544382018tmp
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire_26373613144387982724tmp
> [ERROR] -> [Help 1]
> {noformat}
> We have a a couple of test classes that suffer from this problem. Tests don't
> read from STDIN or replace it. Switching back to 2.18.1 eliminates the
> problem (Ran over 100 builds). It seems to be a race condition because it
> only occurs every once in a while, i.e. ~ 2 out of 10 builds on Travis. I
> haven't been able to reproduce the problem locally.
> More logs:
> https://s3.amazonaws.com/flink-logs-us/travis-artifacts/mxm/flink/849/849.1.tar.gz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1255) Surefire 2.19.1 hangs before starting test execution
[
https://issues.apache.org/jira/browse/SUREFIRE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458358#comment-16458358
]
Abel Salgado Romero commented on SUREFIRE-1255:
---
We are experiencing similar problems with {{asciidoctor-maven-plugin,}} an any
version above 2.19 (inclusive) makes the tests hang.
We are using the plugin as-is, with no fork or additional options
[https://github.com/asciidoctor/asciidoctor-maven-plugin/blob/master/pom.xml#L343.]
Tests eventually run, but they hang and take hours when normally they take a
few minutes. Running with \{{-X}} doesn't show anything other than a big pause
before every test.
> Surefire 2.19.1 hangs before starting test execution
>
>
> Key: SUREFIRE-1255
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1255
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.19.1
>Reporter: Maximilian Michels
>Assignee: Tibor Digana
>Priority: Critical
>
> Seeing the same error as SUREFIRE-1193 in Apache Flink builds after upgrading
> from 2.18.1 to 2.19.1. No errors, builds just gets stuck at the beginning of
> tests with no log output from the test itself, e.g.
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/137118454/log.txt
> After a couple of minutes Surefire reports
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test
> (integration-tests) on project flink-scala-shell_2.10: ExecutionException The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was /bin/sh -c cd
> /home/travis/build/mxm/flink/flink-scala-shell/target &&
> /usr/lib/jvm/java-8-oracle/jre/bin/java -Xms256m -Xmx800m -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -jar
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefirebooter372520169616801479.jar
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire8229439069544382018tmp
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire_26373613144387982724tmp
> [ERROR] -> [Help 1]
> {noformat}
> We have a a couple of test classes that suffer from this problem. Tests don't
> read from STDIN or replace it. Switching back to 2.18.1 eliminates the
> problem (Ran over 100 builds). It seems to be a race condition because it
> only occurs every once in a while, i.e. ~ 2 out of 10 builds on Travis. I
> haven't been able to reproduce the problem locally.
> More logs:
> https://s3.amazonaws.com/flink-logs-us/travis-artifacts/mxm/flink/849/849.1.tar.gz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCM-800) scm connection, developerConnection and url add artifactId at the end when they are inherited.
[ https://issues.apache.org/jira/browse/SCM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458339#comment-16458339 ] Hervé Boutemy commented on SCM-800: --- it's probably time to rework on MNG-5951 and merge it for Maven 3.6 (was dropped with 3.4 and chosen to not include in 3.5 but postpone a little bit) > scm connection, developerConnection and url add artifactId at the end when > they are inherited. > -- > > Key: SCM-800 > URL: https://issues.apache.org/jira/browse/SCM-800 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin >Affects Versions: 1.9.4 > Environment: All environments >Reporter: Rami Ojares >Priority: Major > > This issue is pretty much explained in the summary. > scm fragment can not be inherited in most cases because the system adds > child's artifactId always at the end of the project. Adding it automatically > is of course nice for those few project's where the parent pom happens to be > in the parent folder. But for everyone else it's a showstopper. > This seems to affect also some other urls/paths and this issue has been > reported in one way or another numerous times since 2006. It's about time to > fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
