Was this issue fixed in sdk tools r14?
--
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
not yet.
On Wed, Oct 19, 2011 at 12:51 AM, Izhovkin izhov...@gmail.com wrote:
Was this issue fixed in sdk tools r14?
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Hi,
Any chance this has been fixed - or a workaround is available?
Library projects seem to be the best approach to release multiple versions
of an app (ex: free/paid),
and I was really hoping there is a better solution than to duplicate all of
my custom layouts in both apps.
Many thanks,
Hello,
Having custom attribute (in attrs.xml) in library project leads to
compilation fail of the project dependent of that library.
I.e.:
MyLib project (library)
AndroidManifest.xml:
manifest xmlns:android=http://schemas.android.com/apk/res/android;
package=com.mycompany.test.lib
Ah, there's a problem with the namespace.
From aapt's point of view all the resources are compiled for the
package name of the application (com.mycompany.test.app in your case),
so your customValue attribute is defined in that namespace, and not
in the namespace of the library.
At this time, the
5 matches
Mail list logo
