I forgot to check in my last set of changes, including most of usage.apt.vm. I just checked it in.
I didn't name that class 'Abstract' because, well, I couldn't think of any 'abstract' methods to include in it :-) On Wed, Feb 29, 2012 at 5:49 PM, Hervé BOUTEMY <[email protected]> wrote: > sorry, I can't find which doc you're referring to: can you point me to it, > please? > > did you see the comments I added to actual sources? Are they accurate, or did > I miss something? > > Regards, > > Hervé > > Le mercredi 29 février 2012 17:43:03 Benson Margulies a écrit : >> On Wed, Feb 29, 2012 at 5:03 PM, Hervé BOUTEMY <[email protected]> > wrote: >> > wouldn't be following lifecycle more appropriate? >> > svnpubsub:prepare: do an svn checkout >> > site:stage -DstagingDirectory = svn checkout dir >> > svnpusub:publish: do the svn checkins >> >> I think that this is essentially one of the two options described in >> the doc I wrote for the plugin. >> >> > then using "mvn site svnpubsub" would do the job >> > and the site build would be standard, whatever steps are involved in >> > site >> > building >> > >> > >> > >> > or even without specific lifecycle : given there are sufficient phases >> > in the site lifecycle [1], you can bind: >> > - svnpubsub:prepare to pre-site >> > - site:stage to post-site >> > - svnpusub:publish to site-deploy (problem here, since site:deploy is >> > already bound...) >> > >> > >> > WDYT? >> > >> > Hervé >> > >> > [1] http://maven.apache.org/ref/3.0.4/maven- >> > core/lifecycles.html#site_Lifecycle >> > >> > Le samedi 25 février 2012 13:52:48 Benson Margulies a écrit : >> >> On Sat, Feb 25, 2012 at 1:45 PM, Hervé BOUTEMY <[email protected]> >> > >> > wrote: >> >> > why not consider it as a deploy protocol? >> >> > like scp, file, webdav: svnpubsub >> >> >> >> That only handles the last piece. >> >> >> >> Here's the lifecycle: >> >> >> >> svnpubsub:prepare: do an svn checkout >> >> site:site >> >> site:stage -DstagingDirectory = svn checkout dir >> >> svnpusub:publish: do the svn checkins >> >> >> >> otherwise we don't know what's different. I guess that I could make >> >> the publish mojo do the checkout to yet another directory and compare >> >> the two. That still won't work as a protocol. >> >> >> >> > then the existing site-deploy phase of site lifecycle is >> >> > sufficient >> >> > >> >> > Le samedi 25 février 2012 11:58:36 Benson Margulies a écrit : >> >> >> To make the svnpubsub thing easier to use, I'd like to declare a >> >> >> customer lifecycle for it. Perhaps I need to break for lunch, >> >> >> but can >> >> >> I do that without a packaging? I just want to let someone type >> >> >> >> >> >> mvn svnpubsub >> >> >> >> >> >> and watch the fun. >> >> >> >> >> >> ---------------------------------------------------------------- >> >> >> ----- >> >> >> 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] >> >> --------------------------------------------------------------------- >> 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]
