geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Geronimo Wiki] Update of "EclipseDeployment" by hogstrom
Date Mon, 06 Jun 2005 04:19:41 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by hogstrom:
http://wiki.apache.org/geronimo/EclipseDeployment

New page:
= Developing Geronimo in Eclipse =

This section is written to help someone get Geronimo into the Eclipse workspace as an Eclipse
project and start being able to use Eclipse to make code changes while debugging a server.
 For purposes of this discussion the development OS is Windows and [http://www.cygwin.com
CYGWin] is used for Bash shell support.  Please adjust these instructions for your environment.
----
== Step 1 - Software Pre-requisites. ==

In this section the various tools you'll need are described and suggestions on where to locate
them are made.  The below are suggestions.  You can find these tools on other sites and /
or mirrors.

 * [http://www.cygwin.com CYGWin]
  * '''CVS''' (make sure to include it when installing CYGWin)
 * [http://maven.apache.org Maven]
 * [http://ant.apache.org Ant]
 * [http://subversion.tigris.org/ SubVersion]
 * [http://java.sun.com J2SE 1.4.2] It is important to use the Sun JDK as Geronimo is  currently
using the Sun ORB for RMI.  Using a different JDK or different version of the JDK may result
in compilation errors.
 * [http://www.eclipse.org Eclipse 3.1] You can use earlier versions of Eclipse but 3.1 has
the nify feature of scanning a tree for all projects so if you can do it use the latest version.

The easiest thing to do to make sure these are available on the command line is update your
environment entries after installing Maven and Ant.
----
== Step 2 - Download Geronimo and other Components ==

The instructions for downloading Geronimo can be found here.  I'm including the various commands
here as well so you can avoid page hopping.

Enter the following on your command line.  This will pull Geronimo down on your local harddrive.
 A subdirectory will be created in your current directory called '''geronimo'''.
{{{
$ svn checkout http://svn.apache.org/repos/asf/geronimo/trunk geronimo
}}} 

http://www.hogstrom.org/eclipsedev/eclipsdev01.jpg

The above command will checkout the Geronimo Source and get you ready for the subsequent build
stages. It will run for a bit so get a cup of coffee.

Change to the '''geronimo''' directory.
{{{
$ cd geronimo
}}}

To pull the source for the other packages that make up Geronimo do this:
{{{
$ maven m:fresh-checkout
}}}
The source will be pulled.  I have experienced errors periodically because of intermittent
netowkr problems.  Unfortunately you'll just have to try a couple of times if there are problems.

Next you'll build a server runtime for execution.  This is done by:
{{{
$ maven m:build -Dmaven.test.skip=true -Dmaven.itest.skip=true
}}}
The properties for skipping the tests are pretty much required to reduce time and I have not
seen them run to completion very often.  This will also take a bit of time.  If there are
compilation errors these should be investigated and the '''dev@geronimo.apache.org''' mailing
list should be checked so you don't solve the same problem twice.

Finally you can build the Eclipse projects for Geronimo.  This is done by:
{{{
$ maven -o m:eclipse
}}}
The '''-o''' option will do an offline build and this goes pretty quickly.  
----
== Step 3 - Firing up Eclipse ==
At this point we'll assume that you've already pulled Eclipse and installed it.

You'll open a blank workspace and Import the Geronimo project.  This is done by accessing
teh File -> Import command and selecting the root folder of the Geronimo project.  Once
this is accomplished you should see something like:

http://www.hogstrom.org/eclipsedev/eclipsdev02.jpg

Notice that there are a ton of errors.  To correct these we'll have to setup the environment
a bit.  This includes:

 * Setting the Maven CLASSPATH variables
 * Selecting the right JDK
 * Setting the Java Compiler Options 
 * Fixing problems in the current release (yup, I'll open bug reports unless you beat me to
it :)

===Setting the Maven Classpath variable===
First order of business is to tell Eclipse where the Maven repository is.  To do this select
the settings in Window => Preferences

http://www.hogstrom.org/eclipsedev/eclipsdev03.jpg

Click on ''New'' and a new Pop Up will appear.  Enter the appropriate directory here.

http://www.hogstrom.org/eclipsedev/eclipsdev04.jpg

A number of errors should disappear.  There is still a bit of work to do...

=== Selecting the right JDK and its Options ===
Eclipse allows you to select from any number of installed JDKs.  Assuming that you pulled
a Sun JDK in the beginning setting up the Compiler settings should be pretty straight forward.

Mime
View raw message