Skip to content

Repackage goal does not lazily resolve "project.build.finalName" anymore #16456

@marcust

Description

@marcust

I'm using git-commit-id-plugin to build my final name on <build> level like

<finalName>${project.name}-${version.number}</finalName>

and version.number is defined as

<version.number>${git.commit.time}-${git.commit.id.describe-short}</version.number>

That used to work up to now, but 2.1.4 does not evaluate these variables anymore, so I get

project-${git.commit.time}-${git.commit.id.describe-short}.jar
project-20190404-115039-0bfd654.jar

in my target directory, where the one with the unevaluated variables is the actuall repackaged jar.
I tried now half an hour to achieve the same thing any other way and didn't find a solution, I guess that has something to do with #16202. Can we get the old behaviour back?

Metadata

Metadata

Assignees

Labels

type: regressionA regression from a previous release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions