If what you are proposing is a Maven plugin, then it runs as part of a build sequence, right? If not, then its not a Maven plugin and might be better suited to something like Continuum. If it is running as part of a build sequence, then configuring the appropriate plugin (existing ones to deploy the web app in your example) in the appropriate lifecycle phase is the correct general case and requires no additional plugin.
-----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, January 23, 2006 10:50 To: 'Maven Developers List' Subject: RE: [Plugin idea] watchdog plugin Hi Bob, > -----Original Message----- > From: Allison, Bob [mailto:[EMAIL PROTECTED] > Sent: lundi 23 janvier 2006 16:41 > To: Maven Developers List > Subject: RE: [Plugin idea] watchdog plugin > > Just a note: I handle this in my development by "deploying" my war by > means of a symlink to the generated war in the project's target > directory. When I do a build, the redeploy occurs automatically without > any effort from Maven. Hehe... How do you do a symlink on Windows? :-) (actually it's possible but non-trivial and has issues AFAIR). > I think a general case for what you describe is probably the Cargo(?) > plugin dropped into the lifecycle. Cargo is not a general use case. It's limited to container manipulation. The watchdog idea is something generic for running a mini-CI local build whenever some source change. It'd look for changes and then call a goal/phase when it discovers a change. Thanks -Vincent > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, January 23, 2006 07:49 > To: 'Maven Developers List' > Subject: [Plugin idea] watchdog plugin > > > Here's an idea for someone who'd be looking for a plugin to implement... > :-) > > Imagine a watchdog plugin that would monitor source files and/or > dependencies and trigger a goal when they change. This is a bit similar > to a > continuous integration but done locally on developer's machines. > > Here's a typical use case for it: imagine that you have a WAR that you > generate and you have configured your container to point to it. When you > make changes to your source tree you'd like the war goal to be called so > that your container redeploys automatically the WAR. > > This is only an example but I'm sure you could think of lots of other > examples. Actually this a bit similar to the hot folder concept in > AntFlow > (http://onionnetworks.com/products/antflow/). > > Note that Jetty6 plugin has some code that listen for changes. We could > make > this generic in a watchdog/hotgoal plugin. > > WDYT? Any taker? > > Thanks > -Vincent > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
