So no help here? This is very frustrating to say the least. I've spent all day trying to hack together a workaround for this, when I need to be working on my product instead. And I'm left with a hard- coded mess instead of a clean build process.
What possible reason could there be for you to release these breaking changes without warning, and without even any workarounds to offer? If you didn't like the fact that people could shoot themselves in the foot with resource ID collisions you could give a warning or something--you don't need to just break all of us who need to build our products from separate Android projects. Can you tell me why this is not a serious problem that warrants an immediate fix? -- Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
