Hi Brill,

(i hope this posting is not too late to take notice of...)

Just by scanning through the src code of both plugins, i notice that
the google-code's m2 plugin invokes the GWT compiler using a command
line, spwaning a new os process!
Not a very elegant way...

I'm using the codehaus's gwt plugin and i find it stable enough for an
alpha release and i preffer it implmenetation since it invokes
com.google.gwt.dev.GWTCompiler directly.

Also, from a functionality standpoint, i see that the google's plugin
tries to implement  a pass-par-tout that ends up re-inventing the
wheel (i.e. attaching sources, packaging war, multi-module in a single
maven module), so i preffer Kristian's simpler approach.

Therefore, i would be glad to help porting Kristian's plugin into mojo
as a first class citizen.

Finally, i think we should start using this jira issue for any
subsequent conversations:
http://jira.codehaus.org/browse/MOJO-549

Regards,
 Kostis


On 3/15/07, Brill Pappin <[EMAIL PROTECTED]> wrote:
I've now tried out both...
the google one actually works a bit better so far and they did manage
to come up with something pretty good once you actually get it to
work... it still need a lot of work to be a mainstream plugin (missing
some key features).

I do think the google folks could use some input from the maven guru's
at Codehaus as they do things a bit "funny". Not sure I can pin one
thing down off the top of my head, but I got the "unfinished" feeling
when using it that I usually don't get from codehaus plugins (even the
sandbox plugins).

Frankly I think that what this is really going to take, is a rewrite
of Google's tool wrapper (which should be able to happen without
causing to much in the way of upgrade headaches) to make it more
configurable.

- Brill Pappin

On 3/15/07, kristian <[EMAIL PROTECTED]> wrote:
> Hi Kostis,
>
> I did have a look at the other project and honestly I do not know what
> I should do or can do there. my intension with codehaus was to give
> something back from where I received a lot and I do not have the same
> feelings towards the google camp.
>
> just before you posted that message into the jira ticket, I wanted to
> post something like, whether it would help to get that plugin into the
> sandbox if I add some tests to it.
>
> for me it is quite clear that I would help to maintain the codehaus
> plugin, but if it does not become a codehaus plugin, I just will use
> mine, since it works well enough for my needs.
>
> this is my second plugin I wrote and I learned a lot about plexus,
> maven etc writing it. so whatever the decision will be, I am happy
> with that decision. but I am not the one who decides things here.
>
> with regards
> Kristian
>
>
> On 3/15/07, Kostis Anagnostopoulos <[EMAIL PROTECTED]> wrote:
> > Hi Kristian,
> >
> > There is another maven2 gwt-plugin, this one coming from the Google camp:
> > http://code.google.com/p/gwt-maven/
> > Any ideas for avoiding the double effort?
> >
> > Also, are there any plans to have this plugin added to mojo sandbox?
> >
> > ---
> > I have also cross-posted a similar message to the Google-groups:
> > 
http://groups.google.com/group/gwt-maven/browse_thread/thread/7d3f75a74bf48701/189b8e4a4ab8890e?lnk=st&q=gwt-maven&rnum=9#189b8e4a4ab8890e
> >
> > Regards,
> >   Kostis
> >
> >
> > On 1/31/07, kristian <[EMAIL PROTECTED]> wrote:
> > > hallo Matthew,
> > >
> > > here are a few words about the archetypes. maybe you have to adjust
> > > the version to what you got from the svn. I do appreciate comments on
> > > them.
> > >
> > > gwt-simple-archetype
> > > ===============
> > >
> > > this creates something similar to the GWT-tool 'applicationCreator',
> > > but in a mavenized way.
> > > the created pom.xml has the gwt-plugin, maven-jetty-plugin and the
> > > maven-war-plugin configured. so mvn jetty:run starts an embedded
> > > servlet container and mvn package will pack a ready to deploy
> > > war-file.
> > >
> > > mvn archetype:create                \
> > >   -DgroupId=sample.group.id                        \
> > >   -DartifactId=simple-artifact-id                  \
> > >   -Dversion=1.0-SNAPSHOT                           \
> > >   -DpackageName=sample.group.id                    \
> > >   -DarchetypeGroupId=de.saumya.mojo   \
> > >   -DarchetypeArtifactId=gwt-simple-archetype \
> > >   -DarchetypeVersion=1.4-SNAPSHOT
> > >
> > > gwt-module-archetype
> > > ================
> > >
> > > that just setups a frame for GWT library, i.e. the GWT-module has no
> > > EntryPoint and the
> > > pom.xml is configured to attach the sources on the install goal
> > >
> > > mvn archetype:create                \
> > >   -DgroupId=sample.group.id                        \
> > >   -DartifactId=module-artifact-id                  \
> > >   -Dversion=1.0-SNAPSHOT                           \
> > >   -DpackageName=sample.group.id                    \
> > >   -DarchetypeGroupId=de.saumya.mojo   \
> > >   -DarchetypeArtifactId=gwt-module-archetype \
> > >   -DarchetypeVersion=1.4-SNAPSHOT
> > >
> > > gwt-archetype
> > > ==========
> > >
> > > this is an extension to the gwt-simple-archetype which included an
> > > remote-service and its servlet in the sample application. again mvn
> > > jetty:run starts the embedded servlet container with the application
> > > and mvn package does pack the war-file.
> > >
> > > mvn archetype:create                \
> > >   -DgroupId=sample.group.id                        \
> > >   -DartifactId=artifact-id                  \
> > >   -Dversion=1.0-SNAPSHOT                           \
> > >   -DpackageName=sample.group.id                    \
> > >   -DarchetypeGroupId=de.saumya.mojo   \
> > >   -DarchetypeArtifactId=gwt-archetype \
> > >   -DarchetypeVersion=1.4-SNAPSHOT
> > >
> > > hope that clarifies a bit.
> > >
> > > Kristian
> > >
> > > On 1/31/07, J. Matthew Pryor <[EMAIL PROTECTED]> wrote:
> > > > kristian,
> > > >
> > > > Can you please explain a little more what the archetypes do and why
> > > > they are different?
> > > >
> > > > Thanks,
> > > > Matthew
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe from this list please visit:
> > > >
> > > >     http://xircles.codehaus.org/manage_email
> > > >
> > > >
> > >
> > >
> > > --
> > > Kristian Meier & Saumya Sharma-Meier
> > > Sahyadri School (Krishnamurti Foundation India),
> > > Tiwai Hill,
> > > Rajgurunagar, Pune-410513
> > > Maharashtra, INDIA
> > >
> > > tel: +91 (2135) 321313
> > > pgp: http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x61DB690F
> > > my home: 
http://maps.google.com/maps?hl=en&ie=UTF8&z=18&ll=18.984342,73.772416&spn=0.00209,0.004731&t=k&om=1&mid=1156683744
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe from this list please visit:
> > >
> > >     http://xircles.codehaus.org/manage_email
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> >     http://xircles.codehaus.org/manage_email
> >
> >
>
>
> --
> Kristian Meier & Saumya Sharma-Meier
> Sahyadri School (Krishnamurti Foundation India),
> Tiwai Hill,
> Rajgurunagar, Pune-410513
> Maharashtra, INDIA
>
> tel: +91 (2135) 321313
> pgp: http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x61DB690F
> my home: 
http://maps.google.com/maps?hl=en&ie=UTF8&z=18&ll=18.984342,73.772416&spn=0.00209,0.004731&t=k&om=1&mid=1156683744
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to