+1
Ultimately, I think site-deploy should do the latter, and the /maven-
site-plugin directory should point to different versions of the
documentation (probably an autogenerated page). This is totally
consistent with the layout you are stting up though, just a next
step. wdyt?
- Brett
On 24/05/2007, at 2:00 AM, Wendy Smoak wrote:
On 4/21/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
New plan.
* Change nothing about the way 'mvn site-deploy' currently
works-- it
will publish to, for example,
http://maven.apache.org/plugins/maven-site-plugin. This will be used
for the docs for the latest release, and avoids breaking everyone's
bookmarks.
* Use the mvn site:stage-deploy to publish to
/plugins/${artifactId}-${version} as desired-- for snapshots and for
staging the docs prior to a release. This automatically archives the
versioned docs in the right place. We can then choose whether to
link
to prior versions.
The release process doesn't chanage-- publish the docs to the
un-versioned "current" site, and edit /plugins/index.html.
I'd like to go forward with this, which means changing the plugins to
point to the latest snapshot of their parent pom, testing, and then
getting the parent pom released.
(If this gets in the way of an imminent plugin release, that one can
go back to v8 of the maven-plugins pom.)
--
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]
