Hi Matt,
> -----Original Message-----
> From: Matt Raible [mailto:[EMAIL PROTECTED]
> Sent: samedi 9 décembre 2006 15:56
> To: [email protected]
> Subject: Re: [mojo-user] Cargo and Tomcat plugin (was RE: [mojo-user]
> New snapshot of tomcat-maven-plugin deployed)
>
> On 12/4/06, Vincent Massol <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > Hi Matt,
> >
> >
> >
> >
> >
> >
> > From: Matt Raible [mailto:[EMAIL PROTECTED]
> > Sent: lundi 4 décembre 2006 15:36
> > To: [email protected]
> > Subject: Re: [mojo-user] Cargo and Tomcat plugin (was RE: [mojo-
> user] New
> > snapshot of tomcat-maven-plugin deployed)
> >
> >
> >
> > I like the Tomcat Plugin because it's much less configuration than
> Cargo.
> >
> > This is what I want to figure out. Would you have an example
> configuration
> > and a use case using the Tomcat plugin so that I can compare its
> > configuration with Cargo's?
>
> The Tomcat plugins configuration is:
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>tomcat-maven-plugin</artifactId>
> <configuration>
> <path>/</path>
> </configuration>
> </plugin>
>
> Of course, the <configuration> part isn't required. With this, I can
> run tomcat:run-war and view my project in a browser.
>
> >
> > I continue to use Cargo for testing, but AFAIK, it doesn't do the
> embedded
> > bit like the Tomcat Plugin does.
> >
> > Cargo does support it… it's just not documented yet on the web site.
> See my
> > previous email to Trent on this list.
>
> Is the configuration as simple as the Tomcat plugin though? ;-)
It's a little bit more complex:
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<configuration>
<container>
<containerId>tomcat5x</containerId>
</container>
<configuration>
<deployables>
<deployable>
<location>${basedir}/src/main/webapp</location>
</deployable>
</deployables>
</configuration>
</configuration>
</plugin>
That said it's only more complex because we don't have a special goal in the m2
plugin. It would be very easy to add a new goal like cargo:start-dev and reduce
the configuration to:
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<configuration>
<container>
<containerId>tomcat5x</containerId>
</container>
</configuration>
</plugin>
That would bring it to the same level of configuration complexity I believe. Of
course we could also add aliases for the various containers. For example:
cargo:start-tomcat-dev, which would bring the configuration down to an empty
configuration... :-)
Alternatively we could have several m2 plugin:
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-tomcat-plugin</artifactId>
</plugin>
All in all I don't believe that cargo is more difficult to configure because
it's generic. So far we have focused on being generic which was the necessary
groundwork. We can now focus on usability more and reducing that genericity.
> > Also, for Jetty, the Maven Jetty Plugin works great, whereas Cargo
> has the
> > Log4j issue.
> >
> > Yes, we need to fix that. I need to check how the Jetty plugin has
> done it.
> > This is another example where it would have been great if we were all
> > working on the same version of the code instead of duplicating it…
>
> Agreed.
>
> >
> > One idea: IF we cannot find an easy configuration with cargo for a
> given
> > container, we could have container-specific plugins but using the
> Cargo Java
> > API. That would solve both the code duplication and the simple
> > configuration!
>
> Yes, that would be very cool. If you could get the Jetty and Tomcat
> plugins to depend on Cargo, everyone would likely be much happier.
> These plugins seem like ideal customers for the Cargo project.
Yep I'm all for it. We even have 2 options:
1/ Store these plugins in the cargo project under one umbrella (I believe this
is the best because it allows to quickly modify both the core and the plugin in
case a new feature needs to be added instead of waiting for the core to be
released, coordinating with the cargo project, etc.
2/ Keep these plugins in maven mojo and depend on cargo core. This is also
perfectly fine with me, although I prefer 1/.
Thanks
-Vincent
> > On 12/4/06, Mark Hobson <[EMAIL PROTECTED]> wrote:
> >
> > Hi Vincent,
> >
> > The recent tomcat plugin work has been due to a number of neglected
> > issues and patches that existing users have raised over the last
> year.
> > I always try to direct users onto using cargo, but these updates are
> > for existing users who can't switch over so easily.
> >
> > I agree with the duplication of code between the various container
> > plugins and cargo, and this is also starting to happen with database
> > containers with the hsqldb plugin. Although I do think that the
> site
> > can seem intimidating to new users who just want to deploy a webapp
> to
> > tomcat. I'd also be interested in other peoples reasons too.
> >
> > Cheers,
> >
> > Mark
> >
> > On 04/12/06, Vincent Massol < [EMAIL PROTECTED]> wrote:
> > > Hi everyone,
> > >
> > > I'm curious to understand the differences between the tomcat m2
> plugin
> > and
> > > the cargo m2 plugin. Are they doing the same thing? If not, could
> this be
> > > re-incorporated in the cargo plugin? Also do you know why would
> users
> > pick,
> > > say, the tomcat plugin over the cargo plugin? Is the configuration
> > simpler,
> > > etc?
> > >
> > > This is all driven by a desire to improve Cargo. I'm just curious
> to see
> > how
> > > we could make it even better.
> > >
> > > Also, I see lot of work duplication between what we do in cargo
> and what
> > is
> > > done on the various container specific plugins in m2. That's a
> pity as we
> > > could work together on this I guess.
> > >
> > > Thanks
> > > -Vincent
> > >
> > > PS: The in-place web development stuff is supported for Tomcat in
> Cargo.
> > > Check a working example in http://tinyurl.com/hcmd5 It's not
> documented
> > on
> > > the web site though.
> > >
> > > > -----Original Message-----
> > > > From: Mark Hobson [mailto:[EMAIL PROTECTED]
> > > > Sent: dimanche 3 décembre 2006 22:12
> > > > To: [email protected]
> > > > Subject: Re: [mojo-user] New snapshot of tomcat-maven-plugin
> deployed
> > > >
> > > > On 02/12/06, Matt Raible < [EMAIL PROTECTED]> wrote:
> > > > > This functionality works great - thanks for adding it! How
> hard do
> > > > > you think it'll be to add the run-war functionality? Do you
> need a
> > > > > patch for this?
> > > >
> > > > No worries, I've added tomcat:run-war and deployed a new
> snapshot.
> > > > Give it a go and let me know if you have any probs.
> > > >
> > > > Mark
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> _______________________________________________________________________
> ____
> > > Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
> > questions !
> > > Profitez des connaissances, des opinions et des expériences des
> > internautes sur Yahoo! Questions/Réponses
> > > http://fr.answers.yahoo.com
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > 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
> >
> >
> >
> >
> > --
> > http://raibledesigns.com
>
>
> --
> http://raibledesigns.com
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son
interface r�volutionnaire.
http://fr.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
