Wendy Smoak wrote:
On 10/4/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
There is now (in v9) some config in the plugin parent for staging
sites under maven-whatever-plugin-x.y-SNAPSHOT and I would like to get
that trend started for plugin docs.
Or at least see if there are objections and we need to talk about it
more. Here's what it looks like:
plugins/maven-whatever-plugin <-- latest release
plugins/maven-whatever-plugin-1.1.6 <-- archived release docs
plugins/maven-whatever-plugin-1.2.3 <-- latest release, for archives
plugins/maven-whatever-plugin-1.2.4-SNAPSHOT
How does it move a site from the latest release to an archived one? Are
you doing some rewrite rules or something?
This is not currently in place, so it's not happening at all yet. :)
I'd say we just publish to the staging area from the tag when the
release vote is called (for review) and then do a normal 'mvn
site-deploy' to the un-versioned/latest url once the vote passes (when
you merge the staging repo artifacts).
It could be done with symlinks on the server or rewrite rules in
.htaccess also-- of the two I'd prefer .htaccess because it can be
kept in svn. (It's also very easy to break the site with a typo. Not
that I'd know...)
The implementation doesn't matter too much to me, people who have been
doing plugin releases probably have a better idea of the easiest way
to do it.
Wendy,
I agree that having versioned deployments of plugins docs. If we go down this road, we could simply
have the unversioned url (eg plugins/maven-whatever-plugin) point to the versioned deployment,
rather than redeploying.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
