rgladwell/m2e-android — Issue #53: Class files of dependencies that are also in the workspace not included when m2e is set to resolve them
Author: thoutbeckers
Created: 2011-11-05 19:02:13+00:00
State: open

From #45:

When including another project in the workspace as a dependency m2e has the option to resolve this to another project instead of a jar (this is on the Maven option pane as "resolve dependencies from Workspace projects"). This however leads to sources not being included in the dependent project, or at least not most of the time.

But this appears broken in "normal" ADT too, code from referenced projects does not appear to be included, nor their exported libraries. I looks like ADT includes only classed from jars/class-folders on the classpath of the project, not other projects (see BuilderHelper -> handleClasspathEntry(IClasspathEntry e, IWorkspaceRoot wsRoot,
ArrayList oslibraryList, ResourceMarker resMarker) in ADT). So post r14's "dex everything that's on the classpath" is sadly limited to "dex everything on the classpath that I can wrangle a jar file of class folder from".

Though I'm not using them atm it seems to me any Library projects exposed through the Maven classpath container will get the same treatment by ADT.

Not resolving the workspace projects leads to including jars that are in your local maven repo, which at the moment are only updated when you do an external maven build (neither m2e-android nor m2e update the jar there afaik).