Eclipse Community Forums: Eclipse Platform » java.lang.Error: Unresolved compilation problem (AFTER export!)

Help

Home

Home » Eclipse Projects » Eclipse Platform » java.lang.Error: Unresolved compilation problem (AFTER export!)

Show: Today's Messages :: Show Polls :: Message Navigator

java.lang.Error: Unresolved compilation problem (AFTER export!) [message #661517]

Fri, 25 March 2011 04:02

Marco Lopes

Messages: 61
Registered: September 2010

Member

I'm having a nasty problem that i cannot get rid of:

1) I have a MAIN plugin called "rcpcolibri"

2) I have a child plugin called "org.dma.utils" that's used by rcpcolibri (this plugin uses the following jars on the classpath:
bcprov-jdk16-145.jar
commons-codec-1.4.jar
commons-email-1.2.jar
iText-5.0.4.jar
mail.jar

3) Everything works like a charm INSIDE the eclipse IDE. No errors on my project. Runs perfectly.

- After i EXPORT my project (RCP Plugin) i get "java.lang.Error: Unresolved compilation problem" after the fisrt access to "org.dma.utils" Plugin.

!SESSION 2011-03-25 03:52:04.703 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_PT
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2011-03-25 03:52:12.062
!MESSAGE Application error
!STACK 1
java.lang.Error: Unresolved compilation problem:

at org.dma.utils.array.ArrayUtils.toList(ArrayUtils.java:37)
at org.dma.utils.file.FileImport.openFile(FileImport.java:45)
at rcpcolibri.ui.shells.login.LoginShell.actionCarregar(LoginSh ell.java:708)
at rcpcolibri.ui.shells.login.LoginShell.access$13(LoginShell.j ava:704)
at rcpcolibri.ui.shells.login.LoginShell$3.widgetSelected(Login Shell.java:571)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3657)
at rcpcolibri.Application.login(Application.java:115)
at rcpcolibri.Application.start(Application.java:45)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

Any ideas?? :-\

Report message to a moderator

Re: java.lang.Error: Unresolved compilation problem (AFTER export!) [message #661523 is a reply to message #661517]

Fri, 25 March 2011 05:04

Prakash G.R.

Messages: 621
Registered: July 2009

Senior Member

On 25/03/11 9:32 AM, Marco Lopes wrote:
> 3) Everything works like a charm INSIDE the eclipse IDE. No errors on my
> project. Runs perfectly.
>
> - After i EXPORT my project (RCP Plugin) i get "java.lang.Error:
> Unresolved compilation problem" after the fisrt access to
> "org.dma.utils" Plugin.

Did you add the jar files by editing Java build path? You need to do it
via Classpaths in the Run tab of your plugin manifest editor.

--
- Prakash
Platform UI Team, IBM

www.eclipse-tips.com

Report message to a moderator

Re: java.lang.Error: Unresolved compilation problem (AFTER export!) [message #661541 is a reply to message #661523]

Fri, 25 March 2011 08:34

Marco Lopes

Messages: 61
Registered: September 2010

Member

Yes... that's basic configuration. I develop with Eclipse for 3 years now :-\

I'm debugging and i moved all the "org.dma.utils" code and libraries to the main Plugin...

Still having problems!!!

What can be so different from running inside the IDE and making an export? The code does not pass the same compiler mechanism?

I will keep you posted of my findings...

Report message to a moderator

Re: java.lang.Error: Unresolved compilation problem (AFTER export!) [message #661824 is a reply to message #661541]

Mon, 28 March 2011 07:00

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

On 25.03.2011 09:34, Marco Lopes wrote:
> Yes... that's basic configuration. I develop with Eclipse for 3 years
> now :-\
>
> I'm debugging and i moved all the "org.dma.utils" code and libraries
> to the main Plugin...
>
> Still having problems!!!
>
> What can be so different from running inside the IDE and making an
> export? The code does not pass the same compiler mechanism?
It look like you chose to re-compile during export. If so, take a closer
look to the Console when doing the export. It should report the compile
errors there.

Dani
>
> I will keep you posted of my findings...
>

Report message to a moderator

Re: java.lang.Error: Unresolved compilation problem (AFTER export!) [message #661856 is a reply to message #661824]

Mon, 28 March 2011 10:04

Marco Lopes

Messages: 61
Registered: September 2010

Member

I use the automated "Product Export Wizard", and yes, there is a error ZIP file created, that points out a very strange set of errors, just like eclipse cannot interpret one of the source code files.

By the way, how can i choose NOT to recompile at export time?

Thanks.

Report message to a moderator

Re: java.lang.Error: Unresolved compilation problem (AFTER export!) [message #661951 is a reply to message #661856]

Mon, 28 March 2011 14:58

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

On 28.03.2011 12:04, Marco Lopes wrote:
> I use the automated "Product Export Wizard", and yes, there is a error
> ZIP file created, that points out a very strange set of errors, just
> like eclipse cannot interpret one of the source code files.
>
> By the way, how can i choose NOT to recompile at export time?
I don't know how you do it with that wizard. If you use the 'Deployable
plug-ins and fragments' wizard you can set it on the 'Options' page.

Dani
>
> Thanks.
>

Report message to a moderator

Re: java.lang.Error: Unresolved compilation problem (AFTER export!) [message #662206 is a reply to message #661951]

Tue, 29 March 2011 18:07

Marco Lopes

Messages: 61
Registered: September 2010

Member

RESOLVED....

Here is what happened:

1) Project Properties -> Text File Encoding -> Changed from default CP1252 to UTF-8

2) Eclipse encoded all classes well, except for ONE - Encoded with UCS2-Big Endian.

3) At EXPORT-COMPILE time, eclipse could not process the "Big Endian" encoded class. The export was made but was not runnable (caused error).

So, here we have 2 Bugs / problems:

a) Eclipse wrongly encoded one class file
b) Eclipse cannot cope with certain text files encoding at EXPORT-Compile time.

Report message to a moderator

Re: java.lang.Error: Unresolved compilation problem (AFTER export!) [message #1517143 is a reply to message #662206]

Fri, 19 December 2014 09:33

Umair Iqbal

Messages: 1
Registered: December 2014

Junior Member

So what was your solution?
I changed the Text File encoding of my plugin under properties to Cp1252 and after exporting the product I get the same error. I am using one external jar file in my plugin under manifest of the plugin I have

Bundle-ClassPath: .,
external:$eaapi_location$/eaapi.jar

Report message to a moderator

Previous Topic:	Console view loses output from previous builder
Next Topic:	Eclipse start error

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 22:27:39 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter