On Mon, Nov 9, 2009 at 3:43 PM, Ramesh Reddy <rareddy@redhat.com> wrote:

On Mon, 2009-11-09 at 11:16 -0500, Sanjay Chaudhuri wrote:
>   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.

I was thinking about using template variables like in "code" completion
in java editor. Frankly I do not know much about Eclipse JET, I have
written code generators before but always used my own techniques. You
are correct as the number of variables for us would be a small set. So,
use what you think is appropriate.

Sanjay>> For Code Completion, please let me know what all do you want to see with CTRL+SPACE, and I shall look into it. JET is pretty involved; once you come up with your templates, I shall look into it.

>  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.

Having a "lib" directory is just choice on part of the user. What I am
saying is, during a normal Java project setup a user can define a set of
dependent jars that project needs. We need to use this list and package
them in RAR file generation.

Sanjay>> Got it; so the task will be responsible to resolve the jars from the classpath which the user chooses. Good approach; we don't restrict the user to put jars in specific location.