Home » Newcomers » Newcomers » Cannot debug javaeditor - was plug-in / manifest conversion
| Cannot debug javaeditor - was plug-in / manifest conversion [message #186278] |
Mon, 01 January 2007 16:38  |
Eclipse User |
|
|
|
Originally posted by: bernardd173.yahoo.com
I'm incredibly frustrated with the sample java editor and looking for help
with one last attempt before I trash Eclipse.
I'm a novice to Eclipse and have been frustrated by many things but I've
tried to go back to basics and start again. I deleted the entire project
directory tree in my workspace and started again. When I go to the
"welcome" page and select "samples" -> "Java Editor" it downloads and I
have the source. The build reports no errors and generates a lot of
class files at:
C:\my_path\my_workspace\org.eclipse.ui.examples.javaeditor\b in\org\eclipse\ui\examples\javaeditor
and in a couple of standard directories below this.
I can apparently run the sample java editor (I have the expected icon in
the new Eclipse application) but I can't debug the same editor plugin.
Every time I try it fails to get the declared constructor for the
activatorClassName
"org.eclipse.ui.examples.javaeditor.JavaEditorExamplePlugin"
I've tried with both the downloaded plugin.xml file, and also after
converting this to a combination of a plugin.xml and a manifest.mf file
using the button on the Overview page.
The obvious question is, "if Eclipse knows where the source is, and
generates the class files, why the heck can't it pass the correct
information along to the new application"?
Or is there something else that's going wrong here? A version problem
perhaps?
Or is there something else I need to do to prepare for debug that isn't
obvious?
Does someone else have the time to start a new workspace with 3.2.1, get
the sample editor using the welcome page and confirm that they can or
cannot debug this code?
Thanks in advance,
Bernard
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186295 is a reply to message #186278] |
Tue, 02 January 2007 08:57  |
 Asaf Yaffe
Messages: 333
Registered: July 2009 |
Senior Member |
|
|
Bernard wrote:
>
> I'm incredibly frustrated with the sample java editor and looking for
> help with one last attempt before I trash Eclipse.
>
> I'm a novice to Eclipse and have been frustrated by many things but I've
> tried to go back to basics and start again. I deleted the entire
> project directory tree in my workspace and started again. When I go to
> the "welcome" page and select "samples" -> "Java Editor" it downloads
> and I have the source. The build reports no errors and generates a lot
> of class files at:
>
> C:\my_path\my_workspace\org.eclipse.ui.examples.javaeditor\b in\org\eclipse\ui\examples\javaeditor
>
>
> and in a couple of standard directories below this.
>
>
> I can apparently run the sample java editor (I have the expected icon in
> the new Eclipse application) but I can't debug the same editor plugin.
> Every time I try it fails to get the declared constructor for the
> activatorClassName
> "org.eclipse.ui.examples.javaeditor.JavaEditorExamplePlugin"
>
> I've tried with both the downloaded plugin.xml file, and also after
> converting this to a combination of a plugin.xml and a manifest.mf file
> using the button on the Overview page.
>
> The obvious question is, "if Eclipse knows where the source is, and
> generates the class files, why the heck can't it pass the correct
> information along to the new application"?
>
> Or is there something else that's going wrong here? A version problem
> perhaps?
>
> Or is there something else I need to do to prepare for debug that isn't
> obvious?
>
> Does someone else have the time to start a new workspace with 3.2.1, get
> the sample editor using the welcome page and confirm that they can or
> cannot debug this code?
>
> Thanks in advance,
>
> Bernard
>
>
Bernard,
Sorry to hear that you have such a bad experience with Eclipse. I have
used the Welcome screen to obtain the Java Editor example, and was then
able to compile, launch and debug the plugin "out-of-the-box" without
any problems (I just used the links in the help Cheat-Sheet to do all of
this). I am using Eclipse 3.2.1 (the basic Eclipse-SDK bundle) on
Windows XP SP2, with Sun HotSpot VM 1.5.0_10.
It seems to me that you have some kind of a configuration problem.
Unfortunately, there is not enough information in your mail to
understand what's happening. Did you check the Eclipse Error Log (in
<Workspace dir>\.metadata\.log)? Do you see anything interesting there?
HTH,
Asaf
--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186328 is a reply to message #186295] |
Tue, 02 January 2007 15:06 |
| Eclipse User |
|
|
|
Originally posted by: bernardd173.yahoo.com
Asaf Yaffe wrote:
> Bernard,
> Sorry to hear that you have such a bad experience with Eclipse. I have
> used the Welcome screen to obtain the Java Editor example, and was then
> able to compile, launch and debug the plugin "out-of-the-box" without
> any problems (I just used the links in the help Cheat-Sheet to do all of
> this). I am using Eclipse 3.2.1 (the basic Eclipse-SDK bundle) on
> Windows XP SP2, with Sun HotSpot VM 1.5.0_10.
> It seems to me that you have some kind of a configuration problem.
> Unfortunately, there is not enough information in your mail to
> understand what's happening. Did you check the Eclipse Error Log (in
> <Workspace dir>.metadata.log)? Do you see anything interesting there?
> HTH,
> Asaf
Hi Asaf,
Thanks for your comments. I've just learned something else about the
problem - it's related to use of the class load breakpoints. With these
on the spawned Eclipse instance dies and doesn't write its log file.
Without them I can invoke the new instance but of course I can't do
anything of value. Did you try to add breakpoints?
FYI : the only difference between your environment and mine is I have a
Sun 1.4.2 VM. Curiously one of the .log files contains entries that seem
related:
~~~~~~~~~~~
!SESSION 2007-01-02 08:34:44.843
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.4.2_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application org.eclipse.ui.ide.workbench -pdelaunch
Command-line arguments: -application org.eclipse.ui.ide.workbench -data
C:\TransactorWizard\IDE\workspace_321/../runtime-EclipseAppl ication4 -dev
file:C:/TransactorWizard/IDE/workspace_321/.metadata/.plugin s/org.eclipse.pde.core/Eclipse
Application/dev.properties -pdelaunch -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
!MESSAGE The following is a complete list of bundles which are not
resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
!MESSAGE Bundle
update@plugins/org.eclipse.jdt.apt.core_3.2.1.R32x_v20060822-2100.jar [39]
was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.core 2 0 2007-01-02 08:34:47.265
!MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: J2SE-1.5
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
!MESSAGE Bundle
update@plugins/org.eclipse.jdt.apt.ui_3.2.1.R32x_v20060822-2100.jar [40]
was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.ui 2 0 2007-01-02 08:34:47.265
!MESSAGE Missing required bundle org.eclipse.jdt.apt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
!MESSAGE Bundle
update@plugins/org.eclipse.jdt.junit4.runtime_1.0.1.r321_v20060905.jar
[49] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.junit4.runtime 2 0 2007-01-02 08:34:47.265
!MESSAGE Missing required bundle org.junit4_[4.1.0,4.2.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
!MESSAGE Bundle update@plugins/org.junit4_4.1.0.1 [115] was not resolved.
!SUBENTRY 2 org.junit4 2 0 2007-01-02 08:34:47.265
!MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: J2SE-1.5
~~~~~~~~~~~
though I can't repeat the exact circumstances under which this was
generated. My understanding was Eclipse required 1.4.2 therefore my
choice would be to develop with the lowest possible requirement to avopid
version problems in the users machines.
Thanks,
Bernard
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186344 is a reply to message #186328] |
Tue, 02 January 2007 15:39 |
Asaf Yaffe
Messages: 333
Registered: July 2009 |
Senior Member |
|
|
Bernard,
>
> ~~~~~~~~~~~
>
> !SESSION 2007-01-02 08:34:44.843
> -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.4.2_13
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments: -application org.eclipse.ui.ide.workbench -pdelaunch
> Command-line arguments: -application org.eclipse.ui.ide.workbench -data
> C:\TransactorWizard\IDE\workspace_321/../runtime-EclipseAppl ication4
> -dev
> file:C:/TransactorWizard/IDE/workspace_321/.metadata/.plugin s/org.eclipse.pde.core/Eclipse
> Application/dev.properties -pdelaunch -os win32 -ws win32 -arch x86
>
> !ENTRY org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
> !MESSAGE The following is a complete list of bundles which are not
> resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
> !MESSAGE Bundle
> update@plugins/org.eclipse.jdt.apt.core_3.2.1.R32x_v20060822-2100.jar
> [39] was not resolved.
> !SUBENTRY 2 org.eclipse.jdt.apt.core 2 0 2007-01-02 08:34:47.265
> !MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: J2SE-1.5
I'll take a wild guess here: looking at the log (above), it seems that
the execution environment expects a Java 5 VM. I suggest to try any of
the following:
1. Switch the "runtime" Java environment (Launch configuration "Main"
page, "Java Runtime Environment" section) to a Java 5 VM and try
launching the plugin again.
2. In the Launch configuration "Plug-ins" page, select the "Choose
plug-ins and fragments to launch from the list" option, click the
"Deselect All" button, select only the
"org.eclipse.ui.examples.javaeditor" item and then click the "Add
Required Plug-ins" button. Then try to launch your application in a Java
1.4.2 environment. If this works, it means that one of the plugins
currently in your Eclipse installation requires Java 5. BTW - which VM
are you using to launch your Eclipse development environment?
HTH,
Asaf
--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186350 is a reply to message #186344] |
Tue, 02 January 2007 16:03 |
| Eclipse User |
|
|
|
Originally posted by: bernardd173.yahoo.com
Asaf Yaffe wrote:
> I'll take a wild guess here: looking at the log (above), it seems that
> the execution environment expects a Java 5 VM. I suggest to try any of
> the following:
> 1. Switch the "runtime" Java environment (Launch configuration "Main"
> page, "Java Runtime Environment" section) to a Java 5 VM and try
> launching the plugin again.
> 2. In the Launch configuration "Plug-ins" page, select the "Choose
> plug-ins and fragments to launch from the list" option, click the
> "Deselect All" button, select only the
> "org.eclipse.ui.examples.javaeditor" item and then click the "Add
> Required Plug-ins" button. Then try to launch your application in a Java
> 1.4.2 environment. If this works, it means that one of the plugins
> currently in your Eclipse installation requires Java 5.
Thanks for the suggestion - I'll try that though it will take a little
time to set up, because....
> BTW - which VM are you using to launch your Eclipse development environment?
... I deliberately only have 1.4.2_13 installed on my machine - that way
I'm reasonably sure I don't accidentaly introduce requirements for vesions
my users may not have.
I confess I'm a C/C++ guy so it's going to take me a while to figure out
how to get both VM's on my machine, but before I start I wonder if there's
a way to get a clean set of packages that don't require Java 5? I've
grepped the manifests in the Eclipse installation and have found:
/org.apache.ant_1.6.5/META-INF/MANIFEST.MF:Bundle-RequiredEx ecutionEnvironment:
J2SE-1.2
/org.apache.lucene_1.4.103.v20060601/META-INF/MANIFEST.MF:Bu ndle-RequiredExecutionEnvironment:
J2SE-1.3
/org.eclipse.core.runtime.compatibility.registry_3.2.1.R32x_ v20060907/META-INF/MANIFEST.MF:Bundle-RequiredExecutionEnvir onment:
CDC-1.0/Foundation-1.0,J2SE-1.3
/org.eclipse.help.webapp_3.2.1.R321_v20060803/META-INF/MANIF EST.MF:Bundle-RequiredExecutionEnvironment:
J2SE-1.4
/org.eclipse.jdt.debug_3.2.1.r321_v20060731/META-INF/MANIFES T.MF:Bundle-RequiredExecutionEnvironment:
J2SE-1.4
/org.eclipse.jdt.junit.runtime_3.2.1.r321_v20060721/META-INF /MANIFEST.MF:Bundle-RequiredExecutionEnvironment:
J2SE-1.3
/org.eclipse.jdt.junit_3.2.1.r321_v20060810/META-INF/MANIFES T.MF:Bundle-RequiredExecutionEnvironment:
J2SE-1.4
/org.eclipse.pde.build_3.2.1.r321_v20060823/META-INF/MANIFES T.MF:Bundle-RequiredExecutionEnvironment:
J2SE-1.4
/org.eclipse.platform_3.2.0.v20060601/META-INF/MANIFEST.MF:B undle-RequiredExecutionEnvironment:
J2SE-1.4,CDC-1.0/Foundation-1.0,J
/org.eclipse.tomcat_4.1.130.v20060601/META-INF/MANIFEST.MF:B undle-RequiredExecutionEnvironment:
J2SE-1.4
/org.eclipse.ui.intro.universal_3.2.1.R321_v20060905/META-IN F/MANIFEST.MF:Bundle-RequiredExecutionEnvironment:
J2SE-1.4,CDC-1.0/Foundation-1.0,J
/org.eclipse.ui.workbench.compatibility_3.2.0.I20060605-1400 /META-INF/MANIFEST.MF:Bundle-RequiredExecutionEnvironment:
J2SE-1.4
/org.junit4_4.1.0.1/META-INF/MANIFEST.MF:Bundle-RequiredExec utionEnvironment:
J2SE-1.5
/org.junit_3.8.1/META-INF/MANIFEST.MF:Bundle-RequiredExecuti onEnvironment:
J2SE-1.3
so it looks to me like org.junit4_4.1.0.1 is the obvious candidate. I'm
in way over my head here, but does anyone know what this does and how I
can get back to something that meets the stated Eclipse requirement of
1.4.2?
Thanks,
Bernard
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186363 is a reply to message #186350] |
Tue, 02 January 2007 16:24 |
| Eclipse User |
|
|
|
Originally posted by: bernardd173.yahoo.com
Sorry, but I've just realized I have the same problem with the editor in
Eclipse 3.1, though that doesn't have junit4_4.1.0.1 though the
installation is different so I haven't been able to check for anything
else that requires Java 5.
Also, does anyone know how to switch off the class entry breakpoints in
3.1? I don't seem to be able to do that so I can't conclusively prove the
problem is related to the breakpoints.
Thanks,
Bernard
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186385 is a reply to message #186328] |
Tue, 02 January 2007 18:25 |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Bernard" <bernardd173@yahoo.com> wrote in message
news:328d03ac5fb2a42b675c419c8de4df9e$1@www.eclipse.org...
> [...]
> !ENTRY org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
> !MESSAGE The following is a complete list of bundles which are not
> resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-02 08:34:47.265
> !MESSAGE Bundle
> update@plugins/org.eclipse.jdt.apt.core_3.2.1.R32x_v20060822-2100.jar [39]
> was not resolved. (etc.)
The APT and JUnit 4 plug-ins that are not being resolved are not the source
of your problem. They do all require a 1.5 VM, which is why they're failing
to load, but that failure is normal (in a 1.4 VM) and should not be
interfering with your ability to run other 1.4 code.
Respectfully, I think part of the problem here is that, as you say, you're a
complete newbie to Eclipse and even to Java, and yet you're trying to start
by diving into the deep end (extending Eclipse itself by creating a new
Java-like editor). Speaking as someone who's been there, that's biting off
a lot at once. In my experience, the same is true with any sufficiently
powerful application framework: none of them are easy or painless to get
started on. The Eclipse IDE is a powerful application development tool, and
the Eclipse platform is a powerful application framework; you don't need to
fight both of those learning curves at the same time.
If you want to start a little smaller in order to limit your frustration,
here are some things I'd suggest:
1. Start by developing an ordinary Java project, rather than an Eclipse
plug-in. From there move to developing a very simple "hello world" plug-in,
perhaps the "simple plug-in example" from the Platform Plug-in Developer's
Guide in the online help. Only then move on to trying to write an editor.
2. Get a book on Eclipse. The one I'd recommend is "Eclipse: Building
Commercial-Quality Plug-ins (2nd Edition)" (ISBN 978-0321426727, $42 at
Amazon). There's a lot of good information on Eclipse available free and
online, but if you want it gathered together and presented in orderly
fashion, there's nothing like having a book. This book saved me a
tremendous amount of time as I was learning the Eclipse platform.
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186393 is a reply to message #186385] |
Tue, 02 January 2007 19:43 |
| Eclipse User |
|
|
|
Originally posted by: bernardd173.yahoo.com
Walter Harley wrote:
> 1. Start by developing an ordinary Java project, rather than an Eclipse
> plug-in. From there move to developing a very simple "hello world" plug-in,
> perhaps the "simple plug-in example" from the Platform Plug-in Developer's
> Guide in the online help. Only then move on to trying to write an editor.
Walter,
Thanks for the advice, but I know I haven't got to the hard stuff yet -
FYI I've been writing software since college days when I started with
punched cards and Fortran. I've been working with GUI's, particularly
Tcl/Tk since the mid-90's and C++ for more time than I care to remember,
and somewhere in there I've written a few bits of Java. As it happens I
started out with the Hello World plug-in and got that to work. There's a
different posting, but the instructions are missing in 3.2.1 and I had to
go back to 3.1.2 to even be able to complete that. So, Hello World works
and we downloaded the editor example, read the code and changed a lot of
names to our own, but didn't need to change the functionality and were
going to start with that as a basis for our editor. Then I found I
couldn't debug it and went off on a wild goose chase because Eclipse gave
me a "helpful hint" that it was a naming problem.
Days later I've finally figured out what the real issue is by going back
to Hello World. FYI : even in 3.1.2 that only has run instructions and no
debug guideline in the tutorial, despite which I can insert a breakpoint
on the call that opens the message box.
The problem is, the spawned instance dies as soon as I select any "Add
Class Load Breakpoint" in any of my examples - "Hello World", the Sample
Java Editor and my own editor.
It seemed to me that was an attractive feature to use so that I could
check what the code was doing, but it's apparently totally U/S so now I
guess I can manually place breakpoints one line into all the methods and
get the same result.
So, yes, I've been trying to do pretty much as you suggested, but:
1) the quality of the distribution is below what I would have expected in
the vital new user area (missing tutorial instructions, old samples that
don't conform to the current way of doing things, lack of documentation
for the Class Load breakpoint, etc etc)
2) the diagnostic information when something does go wrong is weak to the
point of being misleading
So now I can start on the difficult stuff - there's a bunch of Tcl/Tk
stuff that has to be ported after the Editor is done!
Bernard
|
|
| |
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186526 is a reply to message #186518] |
Wed, 03 January 2007 16:49 |
| Eclipse User |
|
|
|
Originally posted by: bernardd173.yahoo.com
Daniel Megert wrote:
> Simply remove it from the Breakpoints view (Window > Show View).
Thanks - I didn't find that - I intuitively expected the capability to
remove breakpoints in the same place you set them.
> Just FYI: I tried these steps which - even for a newcomer - seem pretty
> simple to me:
> 1. download 3.2.1
> 2. start fresh workspace
> 3. click on the samples button
> 4. click on the Java editor sample to install the sample
> 5. press Finish to create the sample Java editor sample project
> 6. add a class load breakpoint to JavaEditorExamplePlugin
> 7. start debugging a new Eclipse application (click the bug in the tool bar)
> ==> launches new workbench without any problem
> 8. in the new workbench: create a project and a file which ends with ".jav"
> ==> breakpoint is triggered
> From your other postings it looks as if you have steps to reproduce the
> problem when debugging HelloWorld (or Java editor) sample with a class
> load breakpoint. If so, please file a bug report with steps to reproduce
> so that we can take a closer look.
Thanks for trying that. It's exactly the steps I took to confirm the
problem and, of course, it fails every time on my system but never
apparently on yours. I'm running Eclipse 3.1.2 or 3.2.1 on Windows XP SP2
and a Sun 1.4.2_13 VM. Can you think of anything else that might
influence this?
Bernard
|
|
|
| Re: Cannot debug javaeditor - was plug-in / manifest conversion [message #186584 is a reply to message #186393] |
Wed, 03 January 2007 21:48 |
| Eclipse User |
|
|
|
Originally posted by: nedflthngs.gmail.com
http://java.sun.com/products/archive/
This is where you can get older JRE's and all other java toys. Have you
tried reproducing this problem on a different machine?
I think you have some valid points about the getting started and newbie
help topics...I got quite lost in trying to get started with the IDE also,
but give it time. It has a lot of depth to it if you get past some of the
unintuitive dialogs and menus. I'm sure it can do what you want it to, but
it's a question of the time you want to spend on the learning curve.
Good luck.
|
|
| |
Goto Forum:
Current Time: Fri Apr 26 19:47:37 GMT 2024
Powered by FUDForum. Page generated in 0.09797 seconds |
] 
Search
Help
Register
Login
Home
