Re: [I] Maven 3.9.10 can't resolve variables in the version field [maven]

2025-06-11 Thread via GitHub


cstamas commented on issue #2466:
URL: https://github.com/apache/maven/issues/2466#issuecomment-2961722467

   See details here https://issues.apache.org/jira/browse/MNG-8211


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Maven 3.9.10 can't resolve variables in the version field [maven]

2025-06-10 Thread via GitHub


SoMuchForSubtlety commented on issue #2466:
URL: https://github.com/apache/maven/issues/2466#issuecomment-2961439391

   Thanks for the explanation. I'll close this issue, but I think it would be 
worth adding this to the "Potentially Breaking Changes" section of the release 
notes.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Maven 3.9.10 can't resolve variables in the version field [maven]

2025-06-10 Thread via GitHub


SoMuchForSubtlety closed issue #2466: Maven 3.9.10 can't resolve variables in 
the version field
URL: https://github.com/apache/maven/issues/2466


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Maven 3.9.10 can't resolve variables in the version field [maven]

2025-06-10 Thread via GitHub


cstamas commented on issue #2466:
URL: https://github.com/apache/maven/issues/2466#issuecomment-2960491826

   That page documents the feature your POM is using. Yes, previous version let 
you build/install/deploy unusable artifacts, by letting `` be 
"unspecified". This is certain invalid, just like having POM with empty version:
   ```xml

   ```


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Maven 3.9.10 can't resolve variables in the version field [maven]

2025-06-10 Thread via GitHub


SoMuchForSubtlety commented on issue #2466:
URL: https://github.com/apache/maven/issues/2466#issuecomment-2960473575

   I'm not entirely sure what part of that article is relevant here.
   
   This exact pom worked with the previous maven version but no longer does.
   
   Was the previous behavior unintended/a bug?


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Maven 3.9.10 can't resolve variables in the version field [maven]

2025-06-10 Thread via GitHub


cstamas commented on issue #2466:
URL: https://github.com/apache/maven/issues/2466#issuecomment-2960021386

   Please read this page carefully: 
https://maven.apache.org/guides/mini/guide-maven-ci-friendly.html


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



[I] Maven 3.9.10 can't resolve variables in the version field [maven]

2025-06-10 Thread via GitHub


SoMuchForSubtlety opened a new issue, #2466:
URL: https://github.com/apache/maven/issues/2466

   ### Affected version
   
   3.9.10
   
   ### Bug description
   
   Maven build fail with the following error message since upgrading from 3.9.9 
to 3.9.10
   
   ```
   [INFO] Scanning for projects...
   [ERROR] [ERROR] Some problems were encountered while processing the POMs:
   [ERROR] 'version' must be a constant version but is 
'${revision}${changelist}'. @ line 9, column 14
@
   [ERROR] The build could not read 1 project -> [Help 1]
   [ERROR]
   [ERROR]   The project example.namespace:project:${revision}${changelist} 
(/my/project/folder/pom.xml) has 1 error
   [ERROR] 'version' must be a constant version but is 
'${revision}${changelist}'. @ line 9, column 14
   [ERROR]
   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
   [ERROR]
   [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
   [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
   ```
   
   This is a simplified pom causing the error.
   
   ```xml
   http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
   4.0.0
   
   example.namespace
   project
   project
   ${revision}${changelist}
   pom
   my project
   
   
   my-module
   
   
   
   ```


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]