search

kerasking / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

3.5.0: generated filenames in target/ do not expand custom env variables from finalName #344

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm using buildnumber-maven-plugin to populate a "buildNumber" variable (git 
commit hash) in the validate phase and have defined a 
<finalName>${artifactId}-${version}-${buildNumber}</finalName>.

The generated *.jar has the correctly expanded name.

However, files generated by the maven-android-plugin (*.ap_, *.apk, 
*-unsigned.apk) have only actifactId and version expanded, but still contain 
"${buildNumber}" for buildNumber.

Original issue reported on code.google.com by andreas....@gmail.com on 13 Jan 2013 at 3:09

GoogleCodeExporter commented 9 years ago 
We are no longer using the issue tracking system on Google Code. Please refile 
this issue on https://github.com/jayway/maven-android-plugin/issues if you 
still have this problem with the latest release of the Android Maven Plugin

Original comment by mosa...@gmail.com on 19 May 2014 at 4:19