well, actually in a Project Library a Manifest is created as well... Don't ask me what for but it's there :P So there *would* be a place to put it in :P which I also did, but I noticed everything got lost within the Project importing the Project Library. But I have resolved my issue by simplyretrieving the versionCode (and versionName) from the importing Project...
On 4 okt, 14:52, Mark Murphy <mmur...@commonsware.com> wrote: > On Mon, Oct 4, 2010 at 8:27 AM, MobDev <developm...@mobilaria.com> wrote: > > /edit : I posted this on stackoverflow as well and someone responded > > with : > > "As far as I know android library project manifest is ignored at the > > moment, manifest is not merged into end application when you reference > > a library. Hence you cant extract any data from the library's > > manifest." > > > So my question now is : > > hhmmm ok, that would explain it I guess... But is there any official > > statement or anyone who knows this for sure ? > > I am fairly certain the quoted passage above is correct. At the > moment, AFAIK, there is no concept of the library's version being > carried forward into the application, simply because there is no place > to put it. > > Use a string resource instead of android:versionName. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android Training...At Your Office:http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
