[jira] [Created] (MCHANGELOG-144) svn and maven-changelog-plugin results in “The filename, directory name, or volume label syntax is incorrect”

Adrian Wyssmann created MCHANGELOG-144: -- Summary: svn and maven-changelog-plugin results in “The filename, directory name, or volume label syntax is incorrect” Key: MCHANGELOG-144 URL: https://issues.apache.o

[jira] [Commented] (MRELEASE-913) Nested properties in versions cause prepare to fail

[ https://issues.apache.org/jira/browse/MRELEASE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382958#comment-16382958 ] Phil Clay commented on MRELEASE-913: Note that I contributed an example project and

[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

[ https://issues.apache.org/jira/browse/MJAVADOC-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382588#comment-16382588 ] Sean Busbey commented on MJAVADOC-444: -- linking a PR I put together that implements

[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

[ https://issues.apache.org/jira/browse/MJAVADOC-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382587#comment-16382587 ] ASF GitHub Bot commented on MJAVADOC-444: - busbey opened a new pull request #2:

[GitHub] busbey opened a new pull request #2: [MJAVADOC-444] add aggregate-no-fork and aggregate-test-no-fork for non-forking versions of aggregate goals.

busbey opened a new pull request #2: [MJAVADOC-444] add aggregate-no-fork and aggregate-test-no-fork for non-forking versions of aggregate goals. URL: https://github.com/apache/maven-javadoc-plugin/pull/2 Follows the same pattern as JavadocNoForkReport with the aggregate goals. T

[jira] [Commented] (MJAVADOC-490) Aggregate goal fails if artifacts not installed

[ https://issues.apache.org/jira/browse/MJAVADOC-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382320#comment-16382320 ] Sean Busbey commented on MJAVADOC-490: -- using maven-site-plugin version 3.4, I stil

[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

[ https://issues.apache.org/jira/browse/MJAVADOC-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382308#comment-16382308 ] Sean Busbey commented on MJAVADOC-444: -- this would help immensely for our builds ov

[GitHub] stevegutz opened a new pull request #2: Enable blazar

stevegutz opened a new pull request #2: Enable blazar URL: https://github.com/apache/maven-checkstyle-plugin/pull/2 This will allow us to publish and use SNAPSHOTs internally @jhaber This is an automated message from th

[GitHub] stevegutz commented on issue #2: Enable blazar

stevegutz commented on issue #2: Enable blazar URL: https://github.com/apache/maven-checkstyle-plugin/pull/2#issuecomment-369657435 Sorry, wrong repo :( This is an automated message from the Apache Git Service. To respond to

[GitHub] stevegutz closed pull request #2: Enable blazar

stevegutz closed pull request #2: Enable blazar URL: https://github.com/apache/maven-checkstyle-plugin/pull/2 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from

[jira] [Updated] (MPIR-362) CLONE - 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 ] Roberto Benedetti updated MPIR-362: --- Description: I have the same issue that was closed as "Cannot Reproduce". With this pom.xml {cod

[jira] [Updated] (MPIR-362) CLONE - 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 ] Roberto Benedetti updated MPIR-362: --- Priority: Major (was: Critical) > CLONE - Dependency Management report doesn't exclude system s

[jira] [Updated] (MPIR-362) CLONE - 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 ] Roberto Benedetti updated MPIR-362: --- Priority: Critical (was: Major) > CLONE - Dependency Management report doesn't exclude system s

[jira] [Updated] (MPIR-362) CLONE - 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 ] Roberto Benedetti updated MPIR-362: --- Description: I have the same issue that was closed as "non reproducible". With this pom.xml {cod

[jira] [Updated] (MPIR-362) CLONE - 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 ] Roberto Benedetti updated MPIR-362: --- Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161 (was: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7

[jira] [Updated] (MPIR-362) CLONE - 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 ] Roberto Benedetti updated MPIR-362: --- Affects Version/s: (was: 2.5.1) 2.9 > CLONE - Dependency Management r

[jira] [Created] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

Roberto Benedetti created MPIR-362: -- Summary: CLONE - Dependency Management report doesn't exclude system scoped dependencies Key: MPIR-362 URL: https://issues.apache.org/jira/browse/MPIR-362 Project

[jira] [Commented] (WAGON-503) Directory is out of date error in putDirectory() to a non-empty svn repo

[ https://issues.apache.org/jira/browse/WAGON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381975#comment-16381975 ] ASF GitHub Bot commented on WAGON-503: -- GitHub user basinilya opened a pull request:

[GitHub] maven-wagon pull request #47: [WAGON-503] fix Directory is out of date error...

GitHub user basinilya opened a pull request: https://github.com/apache/maven-wagon/pull/47 [WAGON-503] fix Directory is out of date error in putDirectory() to a non-empty svn repo You can merge this pull request into a Git repository by running: $ git pull https://github.com/

[jira] [Updated] (WAGON-503) Directory is out of date error in putDirectory() to a non-empty svn repo

[ https://issues.apache.org/jira/browse/WAGON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Basin updated WAGON-503: - Description: ScmWagon checks out target directory non-recursively, calls FileUtils.copyDirectoryStructure(

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381929#comment-16381929 ] Nicolas Zin edited comment on SUREFIRE-1346 at 3/1/18 12:41 PM: -

[jira] [Commented] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381929#comment-16381929 ] Nicolas Zin commented on SUREFIRE-1346: --- Hi guys, I just faced the problem you a

[jira] [Created] (WAGON-503) Directory is out of date error in putDirectory() to a non-empty svn repo

Ilya Basin created WAGON-503: Summary: Directory is out of date error in putDirectory() to a non-empty svn repo Key: WAGON-503 URL: https://issues.apache.org/jira/browse/WAGON-503 Project: Maven Wagon

[jira] [Updated] (SUREFIRE-1492) Failsafe doesn't fail when a TestEngine throws an Error

[ https://issues.apache.org/jira/browse/SUREFIRE-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mateusz Stefek updated SUREFIRE-1492: - Description: My Jupiter engine fails due to some classloader hell. The logs are below.

[jira] [Created] (SUREFIRE-1492) Failsafe doesn't fail when a TestEngine throws an Error

Mateusz Stefek created SUREFIRE-1492: Summary: Failsafe doesn't fail when a TestEngine throws an Error Key: SUREFIRE-1492 URL: https://issues.apache.org/jira/browse/SUREFIRE-1492 Project: Maven Sur

[jira] [Commented] (MNG-5600) Dependency management import should support exclusions.

[ https://issues.apache.org/jira/browse/MNG-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381725#comment-16381725 ] Deepak Abraham commented on MNG-5600: - Has this been fixed and added to the release buil

[jira] [Updated] (MRELEASE-943) be more tolerant with project version

[ https://issues.apache.org/jira/browse/MRELEASE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated MRELEASE-943: Description: Edit/Note: this task has been split in 3 other tickets (linked), plea

[jira] [Commented] (MRELEASE-943) be more tolerant with project version

[ https://issues.apache.org/jira/browse/MRELEASE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381652#comment-16381652 ] Romain Manni-Bucau commented on MRELEASE-943: - [~rfscholte] done > be more

[jira] [Created] (MRELEASE-1003) support multiversions release with autoVersionModules=true

Romain Manni-Bucau created MRELEASE-1003: Summary: support multiversions release with autoVersionModules=true Key: MRELEASE-1003 URL: https://issues.apache.org/jira/browse/MRELEASE-1003 Project