android - Modifying AndroidManifest.xml with build tag causes infinite rebuilding in Eclipse -


i've added tagging / date-stamping system android build system similar thread found here on stack overflow: embed version details in android apk

this worked out great me, post awesome , modified perl put in datestamp thus:

perl -npi -e 's/(build date:)(.+)(dev-mob)/"build date: " . localtime() . " dev-mob"/e;' $manifest 

the issue i'm dealing eclipse wants continue building on , over. sees androidmanifest.xml has changed, starts autobuild, thereby changing androidmanifest.xml , sparking autobuild... rinse, lather, repeat.

i've turned off "build automatically," , result fine me (i.e. build on debugging deployment and/or after clean), not on every single file save and/or change eclipse want do. co-worker wants autobuild functioning normal, , says date stamping defective otherwise.

how "builder" mark tree refreshed and/or up-to-date after modifying androidmanifest.xml, tree doesn't keep looping? looks flag says "refreshed" evaluated , triggers new build after previous build.

thanks, can post more details on date stamping if desired.

dd

check builder comes first in project builders list order.


Comments

Popular posts from this blog

linux - Mailx and Gmail nss config dir -

c# - Is it possible to remove an existing registration from Autofac container builder? -

php - Mysql PK and FK char(36) vs int(10) -