There's an Error Log view in Eclipse that is particularly helpful to
check when trying to figure out why the Android plugin is failing to
create the link to the library source code for a particular project.
Usually it is something like having an illegal character, like a
hyphen in the library proje
On Sun, Aug 29, 2010 at 7:04 AM, Mark Carter wrote:
> It would be great if both the following ways of including shared
> Android code/resources were possible:
>
> 1. Adding a library .apk file to the build path (in the same way you
> would add a .jar file)
There are way too many technical issues
Hmm this should be handled by the plugin indeed.
To be honest, the way the current plug-in create the linked folder is
not great. We've made it much more robust in the next version (coming
soon). Hopefully that'll fix your problem.
On Sun, Aug 29, 2010 at 5:37 AM, Günther wrote:
> Xavier,
>
> ye
It would be great if both the following ways of including shared
Android code/resources were possible:
1. Adding a library .apk file to the build path (in the same way you
would add a .jar file)
2. Adding an Android Library Project to the build path as a Project
dependency (in the same way you wou
Xavier,
yes, I'm referencing it through the Android settings, as the R files
and resources seem to be handled correctly.
However, I found a work-around last night, which is adding a linked
source to the app project, which is pointing to the library source
directory. I didn't not think this was ne
Are you sure you're referencing it through the library system and not
in the standard JDT build-path?
On Wed, Aug 25, 2010 at 1:54 AM, Günther wrote:
> Xavier,
>
> sorry to intrude here after a month, but I'm having the problem
> described above that the class files from the library project are n
Xavier,
sorry to intrude here after a month, but I'm having the problem
described above that the class files from the library project are not
included in the apk-file at all. Compiling seems to be working, but I
cannot run the application of course, since the classes are missing. I
have a single l
On Tue, Jul 13, 2010 at 1:33 AM, deg wrote:
> A related question, too: I'm stuck with a few warning messages in one
> of my library files. This is bad enough on it's own (my dev style is
> generally a "zero warnings tolerated") but it's worse because Eclipse
> shows multiple copies of each warning
Thanks Mark!
Your parcels look VERY interesting. I'll check if I can use them in my
admittedly complex app structure.
David
On Jul 12, 9:17 pm, Mark Murphy wrote:
> On Mon, Jul 12, 2010 at 5:16 AM, deg wrote:
> > 2) The key reason I've divided the project into a library and main app
> > is tha
Thanks Xavier,
I'm not sure that I was seeing a refresh problem. Repeated F5
refreshes, on both the library and app project had no effect.
On the other hand, I did not have auto refresh set on that machine (I
was working on two different machines and only set the option on one)
so maybe there's s
On Mon, Jul 12, 2010 at 5:16 AM, deg wrote:
> 2) The key reason I've divided the project into a library and main app
> is that we need to ship the library portion to 3rd-party developers.
> But, it looks like there is no way to ship an Android library, except
> as as source files. How can we ship
On Mon, Jul 12, 2010 at 2:16 AM, deg wrote:
> 1) With both projects open in Eclipse, sometimes I make a change to
> source in the library and rebuild. The .class file gets rebuilt in the
> library project's bin directory, but not in the bin directory of the
> main app. This problem persists across
Hi Xavier,
A bit of followup -- I did see one more weird cases where the .class
files were not in the the bin folder, but hard to track down exactly
what was going wrong. I was working in a complex environment where I
had several applications, each depending on one or both of two Android
Library p
Will do.
I did try to duplicate this on a second machine, but no luck. I think
I've already trained myself in the "right" order of operations.
I'll try to remember what I did differently the first times.
David
On Jun 26, 2:30 am, Xavier Ducrohet wrote:
> that's really strange.
>
> If this happ
that's really strange.
If this happens again, can you check if you have the corresponding
.class files in the bin folder of your project?
Xav
On Fri, Jun 25, 2010 at 2:10 AM, deg wrote:
> I mean that it did not include the library classes at all. Somehow,
> even though all classes were visible
I mean that it did not include the library classes at all. Somehow,
even though all classes were visible at compile time (so the referring
classes in the main app compiled without error), the library classes
were not found at runtime, nor were they present when I spelunked into
the .apk file.
This
What do you mean by "does not include the library classes"?
Does it not include the code at all, or does it seem to include an
older version of it?
If it the later, I think this may be due to how Eclipse handles the
linked folder. For eclipse, the files inside src/ in the library is a
different f
Thanks.
It would be great if you could publish a roadmap of how the library
feature will look in the future.
For example, it would be great if library project could depend on
another library project. (Yes, I know I can use an external jar
instead. I'm doing that now, but the experience is not as s
That's correct.
At the moment the manifest of the library is only used to compile the
resource of the library and figure out its package name, so it doesn't
need to contain permissions, activities, services, etc... used by the
library.
However, all projects using the library must include those in
On Jun 23, 11:06 am, deg wrote:
> Also, what are the rules for AndroidManifest elements?
> - Does the main package or an Android library (or both) need to
> declare a uses-permission for something that happens in library code?
> - If a library implements a BroadcastReceiver should it be declared
Thanks, that makes sense.
Also, what are the rules for AndroidManifest elements?
- Does the main package or an Android library (or both) need to
declare a uses-permission for something that happens in library code?
- If a library implements a BroadcastReceiver should it be declared in
its manifest
Android libraries can include resources. Java libraries can not.
On Jun 22, 8:47 am, deg wrote:
> Managing an Android project in Eclipse, which I need to divide into
> several libraries...
>
> What, exactly, are the differences between "Android Libraries" (made
> with Properties | Android | Libra
22 matches
Mail list logo
