Repository navigation
unlock-snapshots doesn't cover versions defined in properties #1269
Description
It's quite common to not set a literal version directly in a dependency but use a property instead:
<!-- ... -->
<properties>
<mylib.version>6.0.1-20250909.132614-1</mylib.version>
</properties>
<!-- ... -->
<dependencies>
<dependency>
<groupId>someorg</groupId>
<artifactId>mylib</artifactId>
<version>${mylib.version}</version>
</dependency>
</dependencies>unlock-snapshots (and I suppose lock-snapshots) doesn't seem to support such a setup because the respective property stays untouched after executing the goal, whereas the goal works as advertised with very same pom.xml when it's not using a property.
Activity
andrzejj0 commentedon Sep 18, 2025
That's correct, but this is the case for most if not all goals (mojos) which do not explicitly name properties: they do not process properties at all.
github-actions commentedon Sep 18, 2026
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.