I'm not in favor of generalizing the J2G Eclipse plugin into a super
migrator that grows in complexity as we incorporate new types of
source formats. I think that instead we should look into factoring
out the parts of J2G that could be used for other types migrators
into a separate
I'm with Paul on this. I envision a Migrate2Geronimo Toolkit that will
consist of a suite of individual plugins (for Eclipse and G), each
handling the migration from a specific appserver to G. Of course, all
these may depend on a base or common plugin. But the user will only
deal with the plugin
+1
This is making a -lot- of sense.
There is no reason that we need to build a huge monolithic Eclipse
plugin to allow people to migrate applications to our modular server
platform.
I originally didn't even think about breaking it up into a group of
specific plugins using a common core -
Looking back, I explained what I was intending very poorly in my
previous reply, but Paul has worded it much better. I am in agreement
with this approach 100%.
+1
Jay D. McHugh wrote:
+1
This is making a -lot- of sense.
There is no reason that we need to build a huge monolithic Eclipse
Hi, Does anyone have any thoughts as to how we'll position the J2G plugin in the
future ?? I understand now that in its initial iteration that it is narrowly
scoped to work for JBoss specific migrations only (thus the JBoss in the name).
However, it seems if we want to eventually enhance it as
I worry that giving it a more generic name before the tool can actually be
applied in a
generic way might confuse some users. Although, since it's being moved at
the moment,
it is the most convenient time to make such a change. I think adding some
extra emphasis
in the documentation that it's
On 10/29/07, Tim McConnell [EMAIL PROTECTED] wrote:
Hi, Does anyone have any thoughts as to how we'll position the J2G plugin
in the
future ?? I understand now that in its initial iteration that it is
narrowly
scoped to work for JBoss specific migrations only (thus the JBoss in the
name).
I was trying to come up with something like that myself. I like the idea of
keeping the 2. Somehow, Migrate 2 Geronimo was too obscure for me to
grasp. Thanks for ending my mental struggle, Joe.
~Jason Warner
On 10/29/07, Joe Bohn [EMAIL PROTECTED] wrote:
Kevan Miller wrote:
On
Kevan Miller wrote:
On 10/29/07, *Tim McConnell* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi, Does anyone have any thoughts as to how we'll position the J2G
plugin in the
future ?? I understand now that in its initial iteration that it is
narrowly
scoped to
I think it would be great if it can handle more than jboss to geronimo.
We can have a pluggable migration framework that does most of the
migration work that is needed from server A to geronimo, and allow a
user to build additional plugins to plugin their server specific stuff
in. For
I like a generic Migrator package name under devtools, so it leaves
open the possibility for other app servers to Geronimo and to
upgrade/migrate from previous Geronimo releases if we make major changes.
-Donald
Kevan Miller wrote:
On 10/29/07, *Tim McConnell* [EMAIL PROTECTED]
I'm going more along with Jason's original reply here...
I like the idea of calling it Geronimo Migration Toolkit, keeping the
name slightly ambiguous with the toolkit at the end would allow for us
to potentially 'grow into' it in the future.
-Erik
Tim McConnell wrote:
Hi, Does anyone have
12 matches
Mail list logo
