Jason and Erik,
Thanks for your feedback! I think Jason is correct, the script
(j2g-configure) is the one that does the copying. I'll work on
allowing the users to install j2g from our eclipse update site (which
should perform similar things as what j2g-configure does). Removing
the
OOps, looks like this reply yesterday only went directly to Jason...
Jason,
Erm, yeah, you are correct, that stuff is in fact handled by the script
itself, and not in the executed Configurator.
-Erik
Lin Sun wrote:
Jason and Erik,
Thanks for your feedback! I think Jason is correct, the
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
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
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
