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
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]
