Thanks. I am willing to help out the documentation once I figure out how to do that myself. I did go through a basic Hello plugin development tutorial but I still have the following specific questions:
1) When I imported devtools project into Eclipse, I imported it as a plugin development--plugin project. Then I gave it a project name and pointed the project contents to directory devtools\modules\eclipse-plugin. Selected default of the rest and finished creating the project. However, I noticed the devtools\modules\eclipse-plugin\plugin.xml file is created, which was not there before I imported the devtools project into Eclipse. 2) Also, I'd like to know what should I have on the java build path of the project? I tried to put everything I can think of -- WTP 1.0.1 SDK zip file, Eclipse 3.1.2. zip file, but when I tried to right click on GenericServerBehaviour (inside of GeronimoServerBehavior.java file) and selected "open call hierarchy" I got a "the resource is not on the build path of a Java project" error. I also could not find the java API doc of this file either. Thanks again for your help! Lin -----Original Message----- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 28, 2006 3:42 PM To: dev@geronimo.apache.org Subject: Re: WTP/Eclipse questions/defects Yes I can but it will be a while before I get to it. Most of the information you really need is in Plugin Development Guide in the Eclipse Help and the tutorials on the Eclipse site which is full of information to get started. But before anything, your best bet is to go though one of the tutorials on creating your first plugin to get familiar with the the plugin development environment and how the eclipse framework works. See http://www.eclipse.org/articles/ - sachin On Feb 28, 2006, at 3:24 PM, Lin Sun wrote: > I read your wiki page on how to develop Geronimo within eclipse > which was > very helpful. However, I haven't been able to debug the Geronimo > plugin > within eclipse. Is there any document on how to that, similar as > the wiki > page for developing Geronimo? I think this will be very useful > for anyone > who wants to help out with the Geronimo plugin. > > Thanks, > > Lin > > -----Original Message----- > From: Sachin Patel [mailto:[EMAIL PROTECTED] > Sent: Monday, February 27, 2006 11:12 PM > To: dev@geronimo.apache.org > Subject: Re: WTP/Eclipse questions/defects > > Just like you would hunt down a problem in G or any other project. > Use the debugger. Eclipse/WTP provides sdk distributions so all the > source is available. You can put breakpoints in the geronimo code to > see the method call hierarchy in the debug view in Eclipse to get an > understanding of who calls what. > > Another common practice is to verify problems against other server > adapters. This would be a good indication that the bug is in WTP and > not the implementation of a given adapter. Then you can use the > debugger to evaluate further. > > - sachin > > > > On Feb 27, 2006, at 10:33 PM, Lin Sun wrote: > >> Hi Sachin, >> >> Thanks this information is very useful. I am relatively new to the >> plugin >> development... Could you shed some light on how to tell if a defect >> is in >> WTP or Geronimo devtools? >> >> Thanks, >> >> Lin >> >> -----Original Message----- >> From: Sachin Patel [mailto:[EMAIL PROTECTED] >> Sent: Monday, February 27, 2006 11:24 AM >> To: dev@geronimo.apache.org; user@geronimo.apache.org >> Subject: WTP/Eclipse questions/defects >> >> With the release of the Eclipse plugin, here are a list of helpful >> resources where WTP/Eclipse specific questions can be asked and where >> you'll be able to search for answers to many common questions. >> >> http://www.eclipse.org/newsgroups/index_project.php >> >> The newsgroup URL is news.eclipse.org and the WTP specific list is >> eclipse.webtools. >> >> The bug reporting tool for all Eclipse projects is https:// >> bugs.eclipse.org/bugs/ >> >> If you feel you find a defect in WTP that you feel affects the >> functionality of the Geronimo plugin, for tracking purposes open a >> Jira in Geronimo and link it to the bugzilla number. This way the >> project is aware and thus can ensure that the defect gets added to >> the WTP adopter list and can take a higher priority. >> >> Thanks. >> >> - sachin >> >> >> >
