What I do is I have a profile with activation on performRelease=true
that change the distribution management to something like
scp://blablablbla/release/${project.version}
So the standard url is used for the dev version and everytime a
release is made, the release of version X.Y.Z is stored in the
release/X.Y.Z subdirectory.
Stéphane
On 4/21/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 4/20/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> Sounds good, except that I would put all stuff of a plugin under
> m.a.o/plugins/${artifactId}. What about the current link with your
> scenario?
A redirect in .htaccess from /plugins/maven-xyz-plugin to
maven-xyz-plugin-1.2? That would mean you have to change two things,
the plugins/index.html page and .htaccess.
Same for ${artifactId}/${version} -- you'd have to update both
plugins/index.html and the per-plugin index page to point to it. Are
there relative links in the menus? They'll break under this option.
The only other thing I can come up with is to point
<distributionManagement><site> to where we want the snapshot docs, and
use the staging url for the released docs. Seems backwards, but I
want 'mvn site-deploy' to just work during development, so you can't
accidentally overwrite a release w/ snapshot docs.
--
Wendy
---------------------------------------------------------------------
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]
