[jira] [Created] (MDEP-848) Dependency Analysis does not work under Java 20

Mark Derricutt created MDEP-848: --- Summary: Dependency Analysis does not work under Java 20 Key: MDEP-848 URL: https://issues.apache.org/jira/browse/MDEP-848 Project: Maven Dependency Plugin Iss

[jira] [Created] (MNG-6647) NPE in DefaultReportingConverter

Mark Derricutt created MNG-6647: --- Summary: NPE in DefaultReportingConverter Key: MNG-6647 URL: https://issues.apache.org/jira/browse/MNG-6647 Project: Maven Issue Type: Bug Reporter

[jira] [Commented] (MNG-6647) NPE in DefaultReportingConverter

[ https://issues.apache.org/jira/browse/MNG-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826584#comment-16826584 ] Mark Derricutt commented on MNG-6647: - [~hboutemy] - checking out that branch and rebui

[jira] Commented: (MNG-5084) Resolver for plugins failing

[ https://jira.codehaus.org/browse/MNG-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272435#comment-272435 ] Mark Derricutt commented on MNG-5084: - Swapping our aether 1.11 for 1.12 in my maven/lib director

[jira] Created: (MNG-5185) Improve "missing dependency" error message when _maven.repositories conflict

Improve "missing dependency" error message when _maven.repositories conflict Key: MNG-5185 URL: https://jira.codehaus.org/browse/MNG-5185 Project: Maven 2 & 3 Issue

[jira] (MNG-5592) Maven Dependency Resolution Locks up

Mark Derricutt created MNG-5592: --- Summary: Maven Dependency Resolution Locks up Key: MNG-5592 URL: https://jira.codehaus.org/browse/MNG-5592 Project: Maven 2 & 3 Issue Type: Bug Compo

[jira] (MNG-5592) Maven Dependency Resolution Locks up

[ https://jira.codehaus.org/browse/MNG-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Derricutt updated MNG-5592: Description: One one of my larger integration projects that involves A LOT of version ranges across a bro

[jira] (MNG-5592) Maven Dependency Resolution Locks up

[ https://jira.codehaus.org/browse/MNG-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342029#comment-342029 ] Mark Derricutt commented on MNG-5592: - Interesting, I left my build running a {{depenency:tree}}

[jira] (MNG-5592) Maven Dependency Resolution Locks up

[ https://jira.codehaus.org/browse/MNG-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342106#comment-342106 ] Mark Derricutt commented on MNG-5592: - Unfortunately so far no - all of our smaller artefacts see

[jira] (MNG-5592) Maven Dependency Resolution Locks up

[ https://jira.codehaus.org/browse/MNG-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350449#comment-350449 ] Mark Derricutt commented on MNG-5592: - Anyone know if this is still valid in a post 3.2.2 Maven w

[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350881#comment-350881 ] Mark Derricutt commented on MNG-3092: - As mentioned in Aether release notes, since 0.9 ( http://

[jira] Created: (MNG-4779) NullPointerException thrown from Maven 3 nightlies

NullPointerException thrown from Maven 3 nightlies -- Key: MNG-4779 URL: http://jira.codehaus.org/browse/MNG-4779 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Reposi

[jira] (MRRESOURCES-61) processed resources are added to main and test resources

[ https://jira.codehaus.org/browse/MRRESOURCES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312578#comment-312578 ] Mark Derricutt commented on MRRESOURCES-61: --- +1 for this. In my instance I'm only wan

[jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312903#comment-312903 ] Mark Derricutt commented on MNG-3092: - Since it looks like a 3.1 release of Maven is on the horiz

[jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314116#comment-314116 ] Mark Derricutt commented on MNG-3092: - +1 on pushing to 3.1.1 - I'd rather see some good thoughts

[jira] Commented: (SCM-444) Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems

[ http://jira.codehaus.org/browse/SCM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217620#action_217620 ] Mark Derricutt commented on SCM-444: Does anyone have a working example of git + the pushChanges=fal

[jira] Commented: (SCM-444) Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems

[ http://jira.codehaus.org/browse/SCM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217625#action_217625 ] Mark Derricutt commented on SCM-444: Tony - good idea with the git:file://./ - I was assuming it wou

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226525#action_226525 ] Mark Derricutt commented on MNG-3092: - When using the nightly maven 3 builds from https://grid.son

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226592#action_226592 ] Mark Derricutt commented on MNG-3092: - Then somethings seriously broken here - my ranges are [1.0,2

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226769#action_226769 ] Mark Derricutt commented on MNG-3092: - Looks like the nightly SNAPSHOTs are actually broken in resp

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226836#action_226836 ] Mark Derricutt commented on MNG-3092: - Nope. My understanding is that the new behavior is to only

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226839#action_226839 ] Mark Derricutt commented on MNG-3092: - Even using [1.0.0,2.0.0-SNAPSHOT] to include the 2.0.0-SNAPS

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226840#action_226840 ] Mark Derricutt commented on MNG-3092: - Ignore most of that last comment, I just noticed you were co

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226897#action_226897 ] Mark Derricutt commented on MNG-3092: - After getting Maven 3 running again I retried our builds at

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226976#action_226976 ] Mark Derricutt commented on MNG-3092: - I thought I'd come up with a work around by deploying my SNA

[jira] Commented: (SCM-444) Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems

[ http://jira.codehaus.org/browse/SCM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229443#action_229443 ] Mark Derricutt commented on SCM-444: How does this work tho... if the release plugin stops you from

[jira] Commented: (MNG-4751) Snapshot version not resolved for version range

[ http://jira.codehaus.org/browse/MNG-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231114#action_231114 ] Mark Derricutt commented on MNG-4751: - This now seems to be affecting IntelliJ IDEA as well ( at le

[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232184#action_232184 ] Mark Derricutt commented on MNG-3092: - Further to this, as I've mentioned previously this currently

[jira] (SCM-738) GitStatusConsumer fails to correctly parse git 1.8.5 status output

[ https://jira.codehaus.org/browse/SCM-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336962#comment-336962 ] Mark Derricutt commented on SCM-738: It would seem that maven-release-plugin by default ( even the

[jira] Created: (MCHANGES-138) Exception thrown when issueManagement section of pom is missing

Exception thrown when issueManagement section of pom is missing --- Key: MCHANGES-138 URL: http://jira.codehaus.org/browse/MCHANGES-138 Project: Maven 2.x Changes Plugin Issue Type:

[jira] Created: (MCHANGES-139) Add support for a prefix string in Jira version numbers

Add support for a prefix string in Jira version numbers --- Key: MCHANGES-139 URL: http://jira.codehaus.org/browse/MCHANGES-139 Project: Maven 2.x Changes Plugin Issue Type: Improvement

[jira] Closed: (MCHANGES-139) Add support for a prefix string in Jira version numbers

[ http://jira.codehaus.org/browse/MCHANGES-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Derricutt closed MCHANGES-139. --- Resolution: Fixed After looking through the code and experimenting, it seems I can already do th

[jira] Created: (MCHANGES-141) Jira Report fails to pick up issues that contain multiple fix-for elements.

Jira Report fails to pick up issues that contain multiple fix-for elements. --- Key: MCHANGES-141 URL: http://jira.codehaus.org/browse/MCHANGES-141 Project: Maven 2.x Changes Plug

[jira] Commented: (MCHANGES-141) Jira Report fails to pick up issues that contain multiple fix-for elements.

[ http://jira.codehaus.org/browse/MCHANGES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155447#action_155447 ] Mark Derricutt commented on MCHANGES-141: - I've noticed on some of my modules/releases, the

[jira] Commented: (MCHANGES-106) the generated jira-result.xml contains no jira-items

[ http://jira.codehaus.org/browse/MCHANGES-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155089#action_155089 ] Mark Derricutt commented on MCHANGES-106: - This sounds like the same problem I was just not

[jira] Commented: (MCHANGES-141) Jira Report fails to pick up issues that contain multiple fix-for elements.

[ http://jira.codehaus.org/browse/MCHANGES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200526#action_200526 ] Mark Derricutt commented on MCHANGES-141: - Rereading through the patch I still think it wor

[jira] [Created] (MNG-8632) Add JDK 24 to the Full Build Pipeline Job

Mark Derricutt created MNG-8632: --- Summary: Add JDK 24 to the Full Build Pipeline Job Key: MNG-8632 URL: https://issues.apache.org/jira/browse/MNG-8632 Project: Maven Issue Type: Improvement