| Problem during packaging: empty jar in \.mtj.tmp\emulation [message #485552] |
Sun, 13 September 2009 07:19  |
Eclipse User |
|
|
|
Hi
After 4 years successfully using EclipseME, today I upgraded to MTJ. I
have encountered a problem generating packaged builds, both obfuscated and
non-obfuscated.
For some reason, the packaging process creates a fresh file in
\.mtj.tmp\emulation\ABC.jar that contains only the mainfest, ie all
classes and resources are missing. Perhaps the PackageBuilderVisitor class
isnt operating correctly?
Another thing: the error is detected late and indirectly by MTJ. The
actual error in the logs is "failed to inflate jar file", and it occurs
much later in the build process. Before that, Proguard had failed, and yet
MTJ just shows a popup and continues on heedless. I had to download and
read the MTJ source code to trace the cause back to the empty jar in the
emulation folder. Fail fast!
In PackageBuilder.updatePackage(), why not validate that the created Jar
has >= 1 classfile, before continuing to the next step, so as to detect
error states closer to where they happen?
|
|
|
|
|
|
|
|
|
| Re: Problem during packaging: empty jar in \.mtj.tmp\emulation [message #671976 is a reply to message #578712] |
Thu, 19 May 2011 09:46  |
| Eclipse User |
|
|
|
I ve got the same problem with packaging after I converted my netbeans mobility project to eclipse pulsar.
In my case the reason of "empty" jar was a missing "build.properties" file in the root of the eclipse project. Looks like MTJ does not bother to notify a user about missing configuration file and does not recreate it.
|
|
|
Powered by
FUDForum. Page generated in 0.11401 seconds
Home