Not a problem; I normally try to spend few hours during weekends, so big commits will take some time from my side as well.
 
Please explain more on what you mean by "Eclipse Java code template mechanism". Some of the eclipse core uses the mechanism I used and some uses JET templates. Are you looking forward to have JET templates ? I thought JET templates are over-kill, because we have very few things to replace.
 
For dependent jars like Oracle drivers as you pointed out, will there be a lib directory under /java/main/ ? If I need to use a temp directory, I plan to create it in the workspace itself and then delete it.

 
On Mon, Nov 9, 2009 at 10:46 AM, Ramesh Reddy <rareddy@redhat.com> wrote:
Sanjay,

It will take me another week or little more to give you a copy of the
template that matches with the new 6.3 Connector API. If you want go
ahead with the variable replacement framework for this based on my
previous email with some sample code. Yes, "ra.xml" will also need to be
variable replaced.

I was thinking if there is way you could use the Eclipse Java code
template mechanism. Just a suggestion.

> >>Sanjay: I think having a eclipse menu would be much better to build
> the RAR. What would be these connector-custom.jar, dependencies-1.jar,
> etc ? Won't the jar contain the compiled classes ? Where should be
> this jar kept ? A build directory ?

connector-custom.jar --> will be the jar file of the all the custom
connector classes that user generated using the plug-in + his/her
additions.

dependencies-${n}.jar --> these are any jar file that connector is
dependent upon. So, any runtime dependencies for this connector. Lets
say if user is writing a connector to "Oracle", then the jar file that
contains the JDBC driver for "Oracle" will be a dependent jar for this
connector.

The user will add the dependent jars as part of building the connector,
just like any other Java project. Then as part of building the RAR, we
should build the "connector-custom.jar" and add it to RAR and then also
add all the dependent JARs that are defined in the build. If we need to
use "temp" directory for keeping the intermediate results we should do
that, then delete it once we have the RAR file.

Ramesh..