I missed the other thread (I was on vacation). I think the current mechanism is dangerous because you may start using a higher API than your minSdkVersion without you knowing it. That's why we put the warning in the first place. I do agree though that the warning can be annoying. Also, when we put the warning in place there was little incentive for the developers to up the build target to use newer manifest attributes.
It's trivial to remove the warning. Making it configurable would be better. Fixing the whole issue (by compiling the java code against a different target than the manifest) would be even better but harder, and it's on my list of things to do. Xav On Tue, Aug 17, 2010 at 10:46 AM, TreKing <[email protected]> wrote: > On Tue, Aug 17, 2010 at 11:50 AM, Sheepz <[email protected]> wrote: >> >> well, I guess they had this conversation already... > > Well, a few people did. There was no clarification from any of the Google > engineers. > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered devices > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
