> -----Original Message----- > From: Trent Rosenbaum [mailto:[EMAIL PROTECTED] > Sent: lundi 4 décembre 2006 18:19 > To: [email protected] > Subject: Re: [mojo-user] Cargo and Tomcat plugin (was RE: [mojo-user] > New snapshot of tomcat-maven-plugin deployed) > > Hi Vincent, > > After my post earlier I started to look into the docs a bit more along > side you example. > I was able to get a tomcat instance running through Cargo and I have > to say that I am pulled more towards this plugin again. I am glad the > feedback was helpful. > > In my earlier email I said that I could be pulled back towards the > tomcat plugin. There is a question that I have and I think it is > because there are not small docs/examples on how to do this/these > things. I have put a location element within the configuration and I > can then use 'mvn compile war:exploded' but I have found that I need > to use the reload link within the deployed manager application. Is > there a configuration element to allow the monitoring of my web > application? (I have just archetyped a simple example and so I have > not got a context file within the META-INF directory).
I've just tried the example I sent you in my previous email. I ran "mvn install cargo:start" on that project and then opened a browser on http://localhost:8082/webapp/index.jsp. Then I modified the content of index.jsp and simply hit reload in my browser and it worked. > Using my last question as an example I think I go back to the > individual plugins because they have less questions. What do you mean by "less questions"? Do you mean that as they have less configuration options you don't have to figure out what each option does? Or do you mean something else? > I felt that the > tomcat plugin was as close to the server and so created more certainty > within my development environment. Now having played with the tomcat > configuration for Cargo I think this plugin has more certainty. The > speed was great for starting the server and I feel that there is a > more complete environment to work within. Cool :-) > I think personally I saw the benefit of Cargo earlier and must have > played with a version that was to early/had issues. Yeah it's possible things were missing. Even now there are lots of things to improve. But we need user's feedback to improve them too. If you have any question/feedback/comment please send them to the cargo list. If you're willing to help, we can open up the cargo web site wiki to you so you can help us improve the doc for example. > Now my experience > with how I want to use maven has grown I can now play around with > Cargo again. Great! Thanks -Vincent > On 04/12/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? > > > > 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. > > > > 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… > > > > 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! > > > > 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 ___________________________________________________________________________ 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
