At this time as its currently implemented, I don't think it would
make a good inside the UI. The context you're working in the IDE is
a "project" under development and J2G currently doesn't operate under
this context. There would be no real advantage to allow it to be
invoked in the UI since it can't be operated on projects in the
workspace.
If any integration into the UI then the proper approach and it would
be fairly trivial is to go ahead with WTP integration...
All J2EE projects in WTP have a notion of a target runtime. Every
application is required to have its target runtime set (JBoss,
WebSphere, Geronimo, etc..). At any point in time you can retarget
an applications runtime to a different one. So if an application's
runtime is set to JBoss, you can currently swap it over to Geronimo.
This operation can be extended to perform any other tasks. In our
case, we would simply process the projects and traverse through the
content running any migrations necessary.
I don't think this would be too hard to do. Its just picking out the
core peices currently inside J2G that actually do the migration on
particular resources and wrapping those in 1 or more WTP operations.
If this approach was taken I would be +1 to integrating this within
the Eclipse Plugin.
hope that helps.
-sachin
On Jun 14, 2007, at 5:54 PM, Jason Warner wrote:
Paul,
Thanks for the feedback!
In regards to integration with the eclipse plugin, I don't believe
that would be an easy task to accomplish. From my understanding,
the eclipse-plugin runs on top of WTP whereas the J2G tool is a
headless plugin. I believe the J2G tool would need to be rewritten
using WTP to allow for integration.
As for a button or other GUI way of launching the tool, I think
that's a great idea. I'm still rather new to working with eclipse
plugins, though, so I'm not quite sure how that could be done. The
tool is launched using a series of scripts, so perhaps a button
that can launch these scripts would be feasible. Anyone know of a
better way?
Jason Warner
On 6/14/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Fantastic
work, thanks for your contributions!
After all this testing and improvement we could consider moving J2G
from sandbox to a more stable location where it can be properly
released and maintained. If our dev community expresses interest in
doing that then maybe the devtools subproject is a good place for
it. Asking for feedback on the users list would help us know how to
proceed as well.
Thinking from the user's perspective, I wonder if J2G can be
integrated with our eclipse plugin somehow? For example could our
eclipse plugin wrapper the J2G functionality in a wizard, button, or
context menu item? Perhaps something simple for starters, just some
way launch the tool from inside the IDE. Since J2G is itself
implemented as an eclipse plugin it would seem strange to provide no
UI controls for it or integration point with our current eclipse
plugin.
Best wishes,
Paul
On Jun 14, 2007, at 2:26 PM, Jason Warner wrote:
> Some of you may have noticed the recent activity on the devlist in
> regards to the J2G conversion tool. Erik Craig and I have been
> making significant improvements in the functionality and usability
> of this tool. Some of these changes include adding new
> documentation on the wiki, fixing scripts to provide more
> functionality, ensuring unix functionality, and general debugging
> for both the code and the unit tests. Now that these changes have
> been made, it might be appropriate to have another look at the tool
> and see if it is ready to be moved out of sandbox and into
> devtools. Any and all comments are welcome.
>
> For those interested, here's a link to the documentation http://
> cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html
