android - Building multiple .apk artifacts for different customers with maven -
i have setup android maven build customer, based on ant.
the base app white label implementation , app distributed several third party customers. each of customer versions uses same source code , set of shared resources. every customer has resources specific company (constants, assets, etc).
the structure of android project looks this. included relevant files/folders , structure remained ant build:
app |--src |--res |--res-customer1 |--res-customer2 |--pom.xml this means have build multiple .apk artifacts same source different resources. best approach this?
the first thing tried use different profiles in main projects pom every customer. wrote shell script execute maven builds (1 per customer).
then came using 1 release profile in main project , passing customer specific properties via command line. properties passed via shell script, similar first approach.
but i'm not happy that, thought using multiple modules. 1 per customer. problem here is, how can build same source without copying source main project on modules? or have setup android project every customer , refer main project apklib? merge shared , customer specific resources?
is there best practice this?
any other approach welcome.
for small differences can sufficient use profiles , few different properties resource filter. profiles bit of bad pattern in maven world , can hard work with.
your hunch use separate modules each customer , have base application apklib correct. know of several people have reported on maven android developers list use , works them. use approach in case well.
in general suggest ask or @ least mention question on mailing list.
Comments
Post a Comment