Re: [I] [MNG-8709] Maven 4.0 erroneously reports it cannot resolve a dependency version from a property [maven]

2026-08-30 Thread via GitHub


gnodet closed issue #10379: [MNG-8709] Maven 4.0 erroneously reports it cannot 
resolve a dependency version from a property
URL: https://github.com/apache/maven/issues/10379


-- 
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] [MNG-8709] Maven 4.0 erroneously reports it cannot resolve a dependency version from a property [maven]

2026-08-30 Thread via GitHub


gnodet commented on issue #10379:
URL: https://github.com/apache/maven/issues/10379#issuecomment-5470636043

   Closed — fix merged in PR #12684.


-- 
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] [MNG-8709] Maven 4.0 erroneously reports it cannot resolve a dependency version from a property [maven]

2026-08-05 Thread via GitHub


goutamadwant commented on issue #10379:
URL: https://github.com/apache/maven/issues/10379#issuecomment-5200599414

   @sparsick I reproduced this with Maven 4.0.0-rc-6 and opened a fix in #12684 
.
   
   The consumer model validation now uses properties from profiles that were 
already active in the built project, while preserving user-property precedence. 
Pls let me know if the fix looks good or have any suggestions. thanks! 


-- 
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] [MNG-8709] Maven 4.0 erroneously reports it cannot resolve a dependency version from a property [maven]

2026-08-05 Thread via GitHub


JackPGreen commented on issue #10379:
URL: https://github.com/apache/maven/issues/10379#issuecomment-5190290370

   > Rechecked my case with rc-6 - the project builds as is without any 
workaround hacks.
   
   I'm glad your issue is fixed, I've retested my original reproducer in RC6 
and unfortunately it still doesn't work.
   
   ```
   % mvnw -V clean install
   Apache Maven 4.0.0-rc-6 (6a8189b24518daa120539fa41ce12f2b48ec09a8)
   {...}
   [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-install-plugin:3.1.3:install (default-install) 
on project maven-4-test: Execution default-install of goal 
org.apache.maven.plugins:maven-install-plugin:3.1.3:install failed: 
org.apache.maven.api.services.ModelBuilderException: 1 problem was  for 
com.me:maven-4-test:jar:0.0.1-SNAPSHOT
   [ERROR] - [ERROR] 'dependencies.dependency.version' for 
groupId='org.springframework', artifactId='spring-context', type='jar' must be 
a valid version but is '${org.springframework.version}'. @ line 1, column 835
   [ERROR] -> [Help 1]
   ```


-- 
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] [MNG-8709] Maven 4.0 erroneously reports it cannot resolve a dependency version from a property [maven]

2026-08-05 Thread via GitHub


estekhin commented on issue #10379:
URL: https://github.com/apache/maven/issues/10379#issuecomment-5190046410

   Rechecked my case with rc-6 - the project builds as is without any 
workaround hacks.


-- 
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] [MNG-8709] Maven 4.0 erroneously reports it cannot resolve a dependency version from a property [maven]

2026-02-12 Thread via GitHub


estekhin commented on issue #10379:
URL: https://github.com/apache/maven/issues/10379#issuecomment-3895468054

   Hitting this problem with 4.0.0-rc-5 too, both as the error and the warning.
   
   With 3.9.12 the project builds without any problems.
   
   With 4.0.0-rc-5 i get a dozen of errors in the form of
   ```
   [ERROR] org.apache.maven.api.services.ModelBuilderException: 1 problem was  
for g1:a1:jar:1.0-SNAPSHOT
   [ERROR] - [ERROR] 'dependencies.dependency.version' for groupId='g2', 
artifactId='a2', type='jar' is missing. @ line 65, column 9
   [ERROR] 
org.apache.maven.internal.transformation.TransformationFailedException: 
org.apache.maven.api.services.ModelBuilderException: 1 problem was  for 
g1:a1:jar:1.0-SNAPSHOT
   [ERROR] - [ERROR] 'dependencies.dependency.version' for groupId='g2', 
artifactId='a2', type='jar' is missing. @ line 65, column 9
   ```
   but g1:a1 module is marked as SUCCESS in build info, the error happens in 
some other module dependent on g1:a1.
   
   The workaround is to add explicit `${g2-a2.version}` for 
all such cases in g1:a1 pom.xml.
   
   After patching every error case the project builds, but logs A LOT OF 
warnings in the form of
   ```
   [WARNING] Failed to notify spy 
org.apache.maven.ReactorReader$ReactorReaderSpy: 
org.apache.maven.api.services.ModelBuilderException: 1 problem was  for 
gX:aX:jar:1.0-SNAPSHOT
   - [ERROR] 'dependencies.dependency.version' for groupId='gY', 
artifactId='aY', type='jar' is missing. @ line 26, column 9
   ```
   


-- 
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]