It's kind of complicated and there are inter-team political considerations. This seems to be the cleanest solution we've hit upon so far. Whether or not it's the right solution in the long run we don't know yet, but that isn't what I'm asking about. I just want help with the mechanics of the build.
At the moment I'm letting the Eclipse ADT generate all of my ant build files. This doesn't seem to be quite good enough, though, since it isn't putting the particular projects listed under "Java Build Path -> Projects" into the classpath. I checked the overridable properties that the android sdk's build.xml provides, but saw no indication of classpath manipulation capabilities there. I *did* see an android.package.exclude variable, which might provide another approach to solving my problem....but I suspect that if I go down that route, then ant will work but Eclipse won't. Not an improvement. On Thursday, October 4, 2012 11:49:21 AM UTC-4, Kristopher Micinski wrote: > > You'll have to tell us more about your build process. > > Generally I simply stick them in libs/ or do something more elaborate > with custom rules. > > I'm honestly not seeing what your problem is, and still not seeing why > you need a class loader, in my experience if you can do things > statically it's best to do them that way.. > > kris > > On Thu, Oct 4, 2012 at 11:43 AM, Lindley <lind...@gmail.com <javascript:>> > wrote: > > I'm aware of the security concerns. > > > > Anyway, I've gotten it working in Eclipse by removing the project > dependency > > under "Reference" on the Android tab of the project properties, and just > > setting that the project is required in the Java Build Path tab (not > > exported). > > > > However, even though Eclipse now builds cleaning, ant does not. I'm not > an > > ant expert. Any ideas how to do the same thing there? I need both to > work. > > > > On Tuesday, October 2, 2012 5:02:35 PM UTC-4, Kristopher Micinski wrote: > >> > >> On Tue, Oct 2, 2012 at 4:45 PM, Lindley <lind...@gmail.com> wrote: > >> > I would prefer not to make it statically linked because I am not the > one > >> > writing the plugins. Each plugin is potentially going to be on a > >> > different > >> > branch of a repository, and I would like to code to continue working > >> > without > >> > undue hardship when I switch branches. Different versions of the > project > >> > files specifying static dependencies on each branch is an option, but > >> > not a > >> > good one. > >> > > >> > Where the classes will be loaded from is precisely the issue. > >> > DexClassLoader > >> > can either take a jar containing a classes.dex or an apk. I mentioned > >> > both > >> > options in the original post. I'm fairly certain I can get things > >> > working > >> > using the jar approach, but it is inelegant in some respects. I > prefer > >> > the > >> > paradigm of installing an apk to install a plugin, and therefore I > need > >> > to > >> > figure out how to explicitly exclude certain dependencies from being > >> > included in the apk. > >> > > >> > >> But what you didn't mention is the distribution scheme for these > >> plugins. If they will be distributed along with the APK then perhaps > >> it's fine, but if they're going to be sent over the network you need > >> to be a little more careful, loading and running potentially random > >> code isn't a good idea, though if it's checksummed.. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to > > android-d...@googlegroups.com<javascript:> > > To unsubscribe from this group, send email to > > android-developers+unsubscr...@googlegroups.com <javascript:> > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en > -- 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
