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?
Thanks,
Stéphane
On 4/21/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
A while ago I pushed for publishing the plugin docs from svn, because
there was so much good information sitting there, invisible until a
release finally happened.
Now it's causing problems, mainly with the Assembly plugin which
changed quite a bit from 2.1 to 2.2. Also, the changes in the ASF's
release guidelines mean we should keep docs on unreleased stuff
separate from the docs intended for users of official releases.
So... I'm thinking of publishing the plugin docs to
/plugins/${artifact-id}-${version}
For example: http://maven.apache.org/plugins/maven-assembly-plugin-2.1/
We already have to update http://maven.apache.org/plugins/index.html
with the version number, it's just a few more keystrokes to change the
link as well as the text on the page.
That means 'mvn site-deploy' Just Works, we can publish docs for the
snapshots, and it's just as easy to publish the docs for the release
with 'mvn site-deploy' from the tag.
If someone wants to link to the snapshot docs, it could be done under
the Plugin Developers page, but I'd just leave it out-- developers can
figure out what the URL is.
The users will be less confused by docs that don't match the released
plugins they're using, and we'll have some archived docs online which
we can link up or not, depending on how much the plugin has changed.
Assembly, for example, needs both sets of docs online.
Thoughts?
--
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]
