[jira] [Created] (MSHARED-1256) Add support for Multi-Release jars
Gabriel Belingueres created MSHARED-1256:
Summary: Add support for Multi-Release jars
Key: MSHARED-1256
URL: https://issues.apache.org/jira/browse/MSHARED-1256
Project: Maven Shared Components
Issue Type: New Feature
Components: maven-shared-jar
Affects Versions: maven-shared-jar-3.0.0
Reporter: Gabriel Belingueres
Add support for Multi-Release jars.
Currently the library is reporting wrong information. For example with artifact
org.codehause.plexus:{color:#00}plexus-utils:3.5.1, the
JarData.jdkRevision() method reports 11, but the library targets 8 (with some
classes targeting Java 9 and 11).{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-apache-parent] ctubbsii commented on pull request #92: [MPOM-337] load plugins containing lifecycle mappings with extensions
ctubbsii commented on PR #92: URL: https://github.com/apache/maven-apache-parent/pull/92#issuecomment-1555989215 > For me the decision whether a plugin should be loaded with or without extensions should primarily be driven by the plugin developer (not by the consumer). I agree. > The fact that this needs to be specified during loading and is not yet given by the plugin descriptor I consider a flaw in the design. I agree with that, too. > Do you have a use case where it makes sense that a plugin is loaded without extensions although it provides one? Not off hand, but if it's configurable by a user, I imagine that there's use cases where a plugin's execution is functionally altered by that configuration. Otherwise, why is this even made available for configuration by users? So long as it's configurable by users, I just seems sensible that configuration should be determined by the user in their `` section and not in the parent POM's `` section. But, as I said originally, I don't really understand the need for this flag at all. Right now, my understanding is that it doesn't really do anything. So I'm not even sure why it's being added. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MCHECKSTYLE-437) CheckstyleReportTest.testNoSource does not clean up after itself
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MCHECKSTYLE-437. - > CheckstyleReportTest.testNoSource does not clean up after itself > > > Key: MCHECKSTYLE-437 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-437 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > Run `mvn test` twice in a row on a fresh checkout at master. The first run > passes. The second run fails: > ``` > [ERROR] Failures: > [ERROR] CheckstyleReportTest.testNoSource:39 > [INFO] > [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0 > ``` > `mvn clean test` will pass again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MCHECKSTYLE-437) CheckstyleReportTest.testNoSource does not clean up after itself
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MCHECKSTYLE-437. --- Resolution: Fixed > CheckstyleReportTest.testNoSource does not clean up after itself > > > Key: MCHECKSTYLE-437 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-437 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > Run `mvn test` twice in a row on a fresh checkout at master. The first run > passes. The second run fails: > ``` > [ERROR] Failures: > [ERROR] CheckstyleReportTest.testNoSource:39 > [INFO] > [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0 > ``` > `mvn clean test` will pass again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCHECKSTYLE-437) CheckstyleReportTest.testNoSource does not clean up after itself
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold reassigned MCHECKSTYLE-437: - Assignee: Elliotte Rusty Harold > CheckstyleReportTest.testNoSource does not clean up after itself > > > Key: MCHECKSTYLE-437 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-437 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > Run `mvn test` twice in a row on a fresh checkout at master. The first run > passes. The second run fails: > ``` > [ERROR] Failures: > [ERROR] CheckstyleReportTest.testNoSource:39 > [INFO] > [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0 > ``` > `mvn clean test` will pass again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCHECKSTYLE-437) CheckstyleReportTest.testNoSource does not clean up after itself
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724556#comment-17724556 ] ASF GitHub Bot commented on MCHECKSTYLE-437: elharo merged PR #120: URL: https://github.com/apache/maven-checkstyle-plugin/pull/120 > CheckstyleReportTest.testNoSource does not clean up after itself > > > Key: MCHECKSTYLE-437 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-437 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > Run `mvn test` twice in a row on a fresh checkout at master. The first run > passes. The second run fails: > ``` > [ERROR] Failures: > [ERROR] CheckstyleReportTest.testNoSource:39 > [INFO] > [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0 > ``` > `mvn clean test` will pass again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-plugin] elharo opened a new pull request, #324: [MDEP-869] update commons-collections to 4.4
elharo opened a new pull request, #324: URL: https://github.com/apache/maven-dependency-plugin/pull/324 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-869) commons-collections to 4.4
[ https://issues.apache.org/jira/browse/MDEP-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724546#comment-17724546 ] ASF GitHub Bot commented on MDEP-869: - elharo opened a new pull request, #324: URL: https://github.com/apache/maven-dependency-plugin/pull/324 (no comment) > commons-collections to 4.4 > -- > > Key: MDEP-869 > URL: https://issues.apache.org/jira/browse/MDEP-869 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-869) commons-collections to 4.4
Elliotte Rusty Harold created MDEP-869: -- Summary: commons-collections to 4.4 Key: MDEP-869 URL: https://issues.apache.org/jira/browse/MDEP-869 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Elliotte Rusty Harold -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #311: Bump maven-shared-utils from 3.3.4 to 3.4.1
dependabot[bot] commented on PR #311: URL: https://github.com/apache/maven-dependency-plugin/pull/311#issuecomment-1555934964 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dependency-plugin] elharo closed pull request #311: Bump maven-shared-utils from 3.3.4 to 3.4.1
elharo closed pull request #311: Bump maven-shared-utils from 3.3.4 to 3.4.1 URL: https://github.com/apache/maven-dependency-plugin/pull/311 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MDEP-868) maven-shared-utils to 3.4.2
[ https://issues.apache.org/jira/browse/MDEP-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724542#comment-17724542 ] ASF GitHub Bot commented on MDEP-868: - elharo opened a new pull request, #322: URL: https://github.com/apache/maven-dependency-plugin/pull/322 (no comment) > maven-shared-utils to 3.4.2 > --- > > Key: MDEP-868 > URL: https://issues.apache.org/jira/browse/MDEP-868 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEP-868) maven-shared-utils to 3.4.2
Elliotte Rusty Harold created MDEP-868: -- Summary: maven-shared-utils to 3.4.2 Key: MDEP-868 URL: https://issues.apache.org/jira/browse/MDEP-868 Project: Maven Dependency Plugin Issue Type: Dependency upgrade Reporter: Elliotte Rusty Harold -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-844) Go Offline doesn't honor exclusions.
[
https://issues.apache.org/jira/browse/MDEP-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724541#comment-17724541
]
Elliotte Rusty Harold commented on MDEP-844:
Likely related to, though not quite the same as, MDEP-568:
dependency:go-offline -DexcludeGroupIds= still try to resolve artifacts in
the excluded group
> Go Offline doesn't honor exclusions.
>
>
> Key: MDEP-844
> URL: https://issues.apache.org/jira/browse/MDEP-844
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
>Affects Versions: 3.5.0
> Environment: Linux and Mac
>Reporter: John Patrick
>Priority: Major
>
> Using the example below;
>
> {code:java}
>
>
>
> org.apache.commons
> commons-configuration2
> 2.8.0
>
>
> org.apache.commons
> commons-vfs2
>
>
>
>
> {code}
>
> When executing `./mvnw
> org.apache.maven.plugins:maven-dependency-plugin:3.5.0:go-offline
> -Dmaven.repo.local=new-dir`.
> I wouldn't expect `commons-vfs2` to be attempted to be downloads or appear in
> `new-dir`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-838) "Artifact has not been packaged yet" error message is not very helpful.
[ https://issues.apache.org/jira/browse/MDEP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MDEP-838: --- Summary: "Artifact has not been packaged yet" error message is not very helpful. (was: " Artifact has not been packaged yet" Errro message is not very helpful.) > "Artifact has not been packaged yet" error message is not very helpful. > --- > > Key: MDEP-838 > URL: https://issues.apache.org/jira/browse/MDEP-838 > Project: Maven Dependency Plugin > Issue Type: Bug >Reporter: Christoph Läubrich >Priority: Major > > Today in a build i get the error > > Artifact has not been packaged yet. When used on reactor artifact, copy > > should be executed after packaging: see MDEP-187 > So I know something is wrong but ... > The error message should at best include > # The "not packed artifact" > # The possible location / reactor project > # Probably *why* it is not considered as packed (e.g does it has no artifact > file? Is it a directory? Something else?) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCHECKSTYLE-437) CheckstyleReportTest.testNoSource does not clean up after itself
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724530#comment-17724530 ] ASF GitHub Bot commented on MCHECKSTYLE-437: elharo opened a new pull request, #120: URL: https://github.com/apache/maven-checkstyle-plugin/pull/120 This is necessary to let the test pass on subsequent runs without a clean. > CheckstyleReportTest.testNoSource does not clean up after itself > > > Key: MCHECKSTYLE-437 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-437 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > Run `mvn test` twice in a row on a fresh checkout at master. The first run > passes. The second run fails: > ``` > [ERROR] Failures: > [ERROR] CheckstyleReportTest.testNoSource:39 > [INFO] > [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0 > ``` > `mvn clean test` will pass again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-checkstyle-plugin] elharo opened a new pull request, #120: [MCHECKSTYLE-437] clean up before test
elharo opened a new pull request, #120: URL: https://github.com/apache/maven-checkstyle-plugin/pull/120 This is necessary to let the test pass on subsequent runs without a clean. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MCHECKSTYLE-437) CheckstyleReportTest.testNoSource does not clean up after itself
Elliotte Rusty Harold created MCHECKSTYLE-437: - Summary: CheckstyleReportTest.testNoSource does not clean up after itself Key: MCHECKSTYLE-437 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-437 Project: Maven Checkstyle Plugin Issue Type: Bug Reporter: Elliotte Rusty Harold Run `mvn test` twice in a row on a fresh checkout at master. The first run passes. The second run fails: ``` [ERROR] Failures: [ERROR] CheckstyleReportTest.testNoSource:39 [INFO] [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0 ``` `mvn clean test` will pass again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRELEASE-1077) Add support for prepare-specific profiles
[ https://issues.apache.org/jira/browse/MRELEASE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724527#comment-17724527 ] ASF GitHub Bot commented on MRELEASE-1077: -- nielsbasjes opened a new pull request, #190: URL: https://github.com/apache/maven-release/pull/190 This is the merge request for the missing `@since` tag as mentioned as a comment https://issues.apache.org/jira/browse/MRELEASE-1077 > Add support for prepare-specific profiles > - > > Key: MRELEASE-1077 > URL: https://issues.apache.org/jira/browse/MRELEASE-1077 > Project: Maven Release Plugin > Issue Type: New Feature > Components: prepare >Affects Versions: 3.0.0-M5 >Reporter: Niels Basjes >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.0.0 > > > In my projects I like to have the latest released version of the software > shown on the website (which is also in the source tree). I do this using the > exec plugin which runs a script to write the project version in a few places. > For this purpose I propose having the option to allow specifying one or more > profiles that are activated during the prepare phase. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-release] nielsbasjes opened a new pull request, #190: [MRELEASE-1077] Add the since tag to the documentation
nielsbasjes opened a new pull request, #190: URL: https://github.com/apache/maven-release/pull/190 This is the merge request for the missing `@since` tag as mentioned as a comment https://issues.apache.org/jira/browse/MRELEASE-1077 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MBUILDCACHE-58) save remote not working anymore with Maven 3.9.1
[ https://issues.apache.org/jira/browse/MBUILDCACHE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724519#comment-17724519 ] ASF GitHub Bot commented on MBUILDCACHE-58: --- Yusufsuryanata1999 commented on PR #72: URL: https://github.com/apache/maven-build-cache-extension/pull/72#issuecomment-1555880333 > Following this checklist to help us incorporate your contribution quickly and easily: > > * [√] Make sure there is a [MBUILDCACHE JIRA issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed > for the change (usually before you start working on it). Trivial changes like typos do not > require a JIRA issue. Your pull request should address just this issue, without > pulling in other changes. > * [√] Each commit in the pull request should have a meaningful subject line and body. > * [√] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in ApproximateQuantiles`, > where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue. Best practice > is to use the JIRA issue title in the pull request title and in the first line of the > commit message. > * [√] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. > * [√] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will > be performed on your pull request automatically. > * [√] You have run the [Core IT](https://maven.apache.org/core-its/core-it-suite/) successfully. > > If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. > > To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. > > * [√] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) > * [√] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). > save remote not working anymore with Maven 3.9.1 > > > Key: MBUILDCACHE-58 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-58 > Project: Maven Build Cache Extension > Issue Type: Bug > Components: remote build cache >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-build-cache-extension] Yusufsuryanata1999 commented on pull request #72: [MBUILDCACHE-58] document workaround to save cache with 3.9.1 and 4.0.0-alpha-5 and run IT test with Maven 3.9.
Yusufsuryanata1999 commented on PR #72: URL: https://github.com/apache/maven-build-cache-extension/pull/72#issuecomment-1555880333 > Following this checklist to help us incorporate your contribution quickly and easily: > > * [√] Make sure there is a [MBUILDCACHE JIRA issue](https://issues.apache.org/jira/browse/MBUILDCACHE) filed > for the change (usually before you start working on it). Trivial changes like typos do not > require a JIRA issue. Your pull request should address just this issue, without > pulling in other changes. > * [√] Each commit in the pull request should have a meaningful subject line and body. > * [√] Format the pull request title like `[MBUILDCACHE-XXX] - Fixes bug in ApproximateQuantiles`, > where you replace `MBUILDCACHE-XXX` with the appropriate JIRA issue. Best practice > is to use the JIRA issue title in the pull request title and in the first line of the > commit message. > * [√] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. > * [√] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will > be performed on your pull request automatically. > * [√] You have run the [Core IT](https://maven.apache.org/core-its/core-it-suite/) successfully. > > If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. > > To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. > > * [√] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) > * [√] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MPMD-379) Support PMD 7.0.0
[
https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-379:
Description:
Add support for the new major version of PMD.
This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 most
likely means, that only PMD 7 will be supported onwards (no backwards
compatibility supported).
wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
A snapshot version that is compatible with the current 7.0.0 release candidates
is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
{code:java}
apache.snapshots
Apache Snapshot Repository
https://repository.apache.org/snapshots
false
true
{code}
was:
Add support for the new major version of PMD.
This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 most
likely means, that only PMD 7 will be supported onwards (no backwards
compatibility supported).
wip branch: https://github.com/apache/maven-pmd-plugin/compare/master...pmd7
> Support PMD 7.0.0
> -
>
> Key: MPMD-379
> URL: https://issues.apache.org/jira/browse/MPMD-379
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
> Add support for the new major version of PMD.
> This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7
> most likely means, that only PMD 7 will be supported onwards (no backwards
> compatibility supported).
> wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
>
> A snapshot version that is compatible with the current 7.0.0 release
> candidates is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
> {code:java}
>
> apache.snapshots
> Apache Snapshot Repository
> https://repository.apache.org/snapshots
>
> false
>
>
> true
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPMD-379) Support PMD 7.0.0
[ https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-379: Fix Version/s: (was: 3.21.1) > Support PMD 7.0.0 > - > > Key: MPMD-379 > URL: https://issues.apache.org/jira/browse/MPMD-379 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > Add support for the new major version of PMD. > This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 > most likely means, that only PMD 7 will be supported onwards (no backwards > compatibility supported). > wip branch: https://github.com/apache/maven-pmd-plugin/compare/master...pmd7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-surefire] michael-o opened a new pull request, #636: Fixes
michael-o opened a new pull request, #636: URL: https://github.com/apache/maven-surefire/pull/636 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/SUREFIRE) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `SUREFIRE-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean install` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean install`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
