Erik,
I was under the impression that the copying of the necessary jars was
handle by the j2g-configure script itself. I don't think the
configurator module is required for this script. It might be best,
if the config.ini changes are unnecessary, to remove the configurator
"plugin" component, and redo the script so that it only does the
copying.
Cheers,
Jason Warner
On 10/10/07, *Erik B. Craig* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Lin,
I did some poking around with what it's actually doing now...
It actually looks like this may not be necessary with eclipse
3.3. I am
not 100% sure on this, because I have only touched j2g while using
Eclipse 3.3 milestones and up, never with 3.2, but I think it may
have
been necessary to set some of the things that it is setting with
Eclipse
3.2. At any rate, I think you are correct in that this is no longer
required with what it's doing to the eclipse config.ini, however
it is
copying some of the dependencies (properties files) into the eclipse
plugins directory, along with the actual plugins themselves,
which this
is most certainly a critical part of its functionality.
Thanks,
Erik
Lin Sun wrote:
> Hi,
>
> I'd like to know a bit more as to why we need the configurator
module
> in j2g. From our user doc, we ask our users to run the
j2g-configure
> in the bin dir which at the end would call
> org.apache.geronimo.devtools.j2g.Configurator. Looks like
what it
> does is to make a copy of existing
> eclipse_home\configuration\config.ini and add some config
properties
> to the config.ini file. But I don't really understand why we
need to
> modify the default config.ini file. I don't think our geronimo
> eclipse plugin modifies it either. It can be a prob when we
want to
> enable a user to download j2g from an update site.
>
> I tried to run j2g with the default config.ini and able to run
the
> jdes2g and jsrc2g fine. I haven't been able to find a sample
that
> allows me to run jres2g yet, so if you know any let me know.
>
> Thanks,
> Lin
>