I've been having this problem too on both WinXP and OSX 10.6. The
common issue seems to be referencing a platform-neutral project from
the android project. I had to revert back to the 2.2 SDK since I
haven't been able to find a solution.
On Dec 6, 3:16 pm, Xavier Ducrohet x...@android.com
Thanks! Please let us know when it is ready :-)
On Dec 6, 7:54 pm, Xavier Ducrohet x...@android.com wrote:
hey all, we found the issue. It's related to referencing java project.
We're looking at pushing a fix to ADT asap. In the meantime you can
temporarily change to including your java
Here goes the stack trace from eclipse:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
I have been experiencing the same problem since updating everything
earlier today. I read elsewhere that increasing the amount of memory
to Eclipse could help, but it hasn't for me.
I'm thinking that library projects could be the culprit. I have three
non-library projects that each depend on a
This has been occurring for many people. This happened to me on a
windows 7 box and if you look on stack overflow, no one has solved
this yet. Anything from Google?
On Dec 6, 6:16 pm, Xavier Ducrohet x...@android.com wrote:
gotta love the error message. *sigh*
From what you're saying you have
I'm having the same problem with eclipse 3.5 on both WinXP and OSX
10.6. The common problem seems to be android projects that reference
platform-independent library projects. I couldn't find a fix so I had
to revert to SDK 2.2.
On Dec 6, 3:16 pm, Xavier Ducrohet x...@android.com wrote:
gotta
The export to jar seemed to work for me as well, but I'd rather get
8.0.1 running. Any idea when that will be pushed out?
On Dec 7, 11:32 am, dario dario.nycj...@gmail.com wrote:
Anselm, I couldn't repro with latest build. Xavier, I posted the bug I
described as issue #13010
-Dario
On Dec
I've just updated, but getting same error. My app was compiling fine
before updating to ADT 8.0.0
We've just released ADT 8.0.1 to fix this issue.
You can use the update site or the direct link (dev site not updated
yet):http://dl.google.com/android/ADT-8.0.1.zip
--
You received this
I confirm the fix too
Merci xavier!
On 7 déc, 18:07, JoeyL spellcheck...@gmail.com wrote:
The export to jar seemed to work for me as well, but I'd rather get
8.0.1 running. Any idea when that will be pushed out?
On Dec 7, 11:32 am, dario dario.nycj...@gmail.com wrote:
Anselm, I couldn't
Fix is in master repo (verified) and it seems like 8.0.1 is ready to
go, however I'm seeing a problem with the layout editor and custom
views that have a dependency on a class that is in a referenced Java
project.
At least the error is accurate this time: NoClassDefFound: name of
class
-Dario
Thanks Xavier.
That's definitely the cause of the problem. Eclipse projects, when
stripped of their dependencies on other eclipse projects, build fine.
Tom.
On 7 December 2010 00:54, Xavier Ducrohet x...@android.com wrote:
hey all, we found the issue. It's related to referencing java project.
I also wanted to note, that I see similar problems with Android
Library projects. It appears as if the ADK does not properly include
the Android Library project classes in a APK project (this is at least
true for interface classes that my Android Library project contains).
Can you confirm this?
Anselm, I couldn't repro with latest build. Xavier, I posted the bug I
described as issue #13010
-Dario
On Dec 7, 8:46 am, garbeam garb...@gmail.com wrote:
I also wanted to note, that I see similar problems with Android
Library projects. It appears as if the ADK does not properly include
the
I'm going to investigate this later today but quick looking at the
source, I suspect this never worked.
I'm not holding 8.0.1 for this but we'll certainly fix this for the
next release.
On Tue, Dec 7, 2010 at 5:46 AM, garbeam garb...@gmail.com wrote:
I also wanted to note, that I see similar
We've just released ADT 8.0.1 to fix this issue.
You can use the update site or the direct link (dev site not updated
yet): http://dl.google.com/android/ADT-8.0.1.zip
Xav
On Tue, Dec 7, 2010 at 10:21 AM, Xavier Ducrohet x...@android.com wrote:
I'm going to investigate this later today but
Hi All,
I got the caption problem and quickly update ADT to 8.0.1. It's not
work when including a Project in Build Path (no problem if include
external jars):
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.IllegalArgumentException: already added: Lorg/apache/james/
mime4j/util/StringArrayMap;
I have the exact same issue. I went the exact same route as the
original poster. The verbose output of all the Android tools in
Eclipse is not all that verbose it turns out. However, digging up
the .log file in $workspace/.metadata/.log brought this up:
!ENTRY com.android.ide.eclipse.adt 4 0
Forgot to mention my system specs:
Windows 7 Home Premium 32-bit, JDK 1.6.0_22, Eclipse Helios SR1.
On 7 Dez., 00:16, Xavier Ducrohet x...@android.com wrote:
gotta love the error message. *sigh*
From what you're saying you have all that's needed. Have you tried
using the Sun VM instead of
hey all, we found the issue. It's related to referencing java project.
We're looking at pushing a fix to ADT asap. In the meantime you can
temporarily change to including your java project as a jar file.
On Mon, Dec 6, 2010 at 4:42 PM, Mario Zechner badlogicga...@gmail.com wrote:
I have the
Awesome thanks a bunch :)
On 7 Dez., 01:54, Xavier Ducrohet x...@android.com wrote:
hey all, we found the issue. It's related to referencing java project.
We're looking at pushing a fix to ADT asap. In the meantime you can
temporarily change to including your java project as a jar file.
Is the fix ready yet? :D
-Nate
On Dec 6, 5:00 pm, Mario Zechner badlogicga...@gmail.com wrote:
Awesome thanks a bunch :)
On 7 Dez., 01:54, Xavier Ducrohet x...@android.com wrote:
hey all, we found the issue. It's related to referencing java project.
We're looking at pushing a fix to
21 matches
Mail list logo
