Open drivera-armedia opened 1 year ago
Hi all!
I'm also interested in this, but I saw no activity or labelling for this issue. I found this other plugin that does the job for me: https://central.sonatype.com/artifact/com.sap.prd.mobile.ios.maven.plugins/resolve-pom-maven-plugin
but I'd rather rely on the flatten maven plugin, which seems to be the recommended way, and it's open source.
Is there a way to upvote this?
Cheers
i got this problem too,Is there any solution
Hi! I'm using something similar to this:
I'm trying to use the flatten plugin to resolve the ${revision} variable prior to artifact deployment for downstream consumption, as mandated by Maven's CI-Friendly practices. However, the systemPath dependency isn't resolved properly. The environment variable is set correctly, and the build works perfectly when not using the flatten plugin - albeit the artifacts produced aren't consumable from a repository due to the use of
<version>${revision}</version>
to allow easy manipulation of the project's version.This is the exception dump I get from using
mvn -e
:Per other tickets I've found, and the integration test system-scope-dep-variable, variable expansion should work on systemPath dependencies. However, it seems that environment variable expansion isn't working properly.
Is there a workaround that I've not found? Is this a fixable bug?
I'm aware that systemPath dependencies are on their way out and we're trying to grapple with how to properly live in that world when it comes ... for now, however, it makes sense to use it for this specific project given that the dependency in question is a legacy library that isn't and will never be available via a Maven repository (long story, trust me on this).
Thoughts?
Cheers!