On Thu, May 10, 2012 8:09 am, Ron Wheeler wrote: > On 10/05/2012 3:06 AM, Julian Kalinowski wrote: >> Hi, >> I'm currently trying port a Java desktop project to Android using maven. >> It has several modules which have different dependencies. >> As the Android Java Runtime doesn't have packages such as awt or >> swing, i needed to exclude some sources for that build and preprocess >> others, which kind of works using munge-maven-plugin. >> >> However, when it comes to incompatible dependencies, i tried to use >> two different profiles to exclude them from the android build (and >> create jars with different classifiers). >> >> But this doesn't work as profiles are not respected during dependency >> resolution, see this bug: >> http://jira.codehaus.org/browse/MNG-1388 >> >> It seems nobody cares about this, so I'm wondering if there's another >> possible solution besides creating a separate pom.xml for every >> module... > > That is the right way to do it. That is why no one cares. It does not > affect anyone who is using Maven as it is intended to be used.
Just dont use profiles but rather different modules and exclusion right in the android project. A good example how you can deal with all this is the bluebill android app from Fabrizio http://bluebill.tidalwave.it/mobile/development/ It uses components from desktop java and does all sorts of good stuff with respect to using maven. In general I would suggest to ask android maven related questions on the maven android developers mailing list though.. https://groups.google.com/forum/?fromgroups#!forum/maven-android-developers manfred http://simpligility.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
