So I've held off on working on "how to build" after checking out the
source until all the project home related stuff gets worked out.
Building these plugins with maven will take some work. As I mentioned
before trying to build purely with maven isn't a good approach as there
are alot of issues to do that. I feel the best best approach is two
simply use the Eclipse integrated PDE builder and then provide maven
plugins to invoke those pde generated ant scripts.
In the meantime, the only way to build the source is within the Eclipse
IDE. The prereqs and procedure to build are the following.
(1) Download and install Eclipse
(2) Download and install WTP the other prereq eclipse projects that are
required for WTP (and this is mentioned on the WTP project site)
EMF-SDO, GEF, and JEM are needed.
(3) Launch eclipse, and launch the "Import Existing Projects into
workspace" wizard.
(4) point to the sandbox/eclipse-plugin directory and select all of the
projects that are displayed.
(5) Now you will have build errors at this point. This is because the
org.apache.geronimo.runtime.v1 project needs to contain a copy the lib/
directory from a geronimo installation. It was not necessary to check
in a copy of the jars in as eventually this plugin can be dynamically
packaged togather during a Maven build.
(6) After dropping in the lib folder into the runtime project, all the
projects should build successfully.
I'll write up a set of detailed instructions on the Wiki on this as well
as how to launch and run for those unfamiler with Eclipse.
Sachin.
Dain Sundstrom wrote:
On Aug 22, 2005, at 5:18 PM, Sachin Patel wrote:
Would one of the committers mind checking in the patches for
884,885, and 888? I'm making changes on source files that already
have existing pending patches in these jiras and don't want to
introduce new patches until their checked to avoid conflicts when
merging. For my knowledge, how is this handled? Are cumulative
patches easily handled? i.e What happens if i have Patch-A based on
revision 1 on File-A. Then I introduce Patch-B on File-A also based
on revision 1 (but includes changes that went into Patch A). Since
both of the patches are based on the same revision # I would assume
that only one of the patches can be applied without errors or
conflicts. What happens when the second patch is applied since the
patch is no longer based on the revision specified in the patch
file? If the second patch cannot be applied, how is one expected to
know which patch to throw out?
I was going to do this last week, but was having build problems. It
looks like Geir is willing to take over for a bit, but please
complain earlier next time :)
On a related note, are their directions on how to build and use this
stuff. Hopefully, we can start to get some community members using
this stuff and giving us feedback.
-dain
