commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: CMS/SvnPubSub for site live ?
Date Wed, 30 Jan 2013 20:56:51 GMT

On Jan 30, 2013, at 12:16 PM, Olivier Lamy wrote:

> Agree for mapping proper/commons-attributes -> proper/commons-attributes-2.2
> Why not with modifying .htaccess ?
> (
> RedirectMatch ^(.*)/attributes/(.*) $1/proper/commons-attributes-2.2/$2

If it works that is fine too.  I know when we were doing the logging site Christian had problems
getting that to work properly.

> symlink means:
> * probably won't work for windauze folks.

It does. On Windows svn creates a file that you can edit.

> * you will need to checkout locally all the content from
> (which will be really bigger if versioned site documentation) whereas
> it's not needed as the scm pub plugin help you to not have to do that.

See the instructions on publishing the logging site. You can checkout and ignore most of the
subdirectories you don't want.

> In case of versioned documentation a new parent release will be needed
> because parent has the subpub url defined with
> <commons.scmPubUrl>${project.artifactId}</commons.scmPubUrl>
> But each component can override that with
> <commons.scmPubUrl>${project.artifactId}-${project.version}</commons.scmPubUrl>

I guess you are assuming the site is actually published to production via Maven.  I never
do that so there is no need to release the parent.  I run mvn site:stage-deploy to a local
directory and then just copy that into the correct svn directory (i.e. something like commons-attributes-2.2)
and then do an svn commit.  With a symlink you don't have to update the CMS site either. With
.htaccess I guess you would.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message