You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Vincent Siveton <vi...@gmail.com> on 2006/08/09 19:12:31 UTC
Staging Plugins Documentation but where?
Hi,
During the last month, around 20 plugins documentations have been
succesfully reviewed and some of them have been staged into user space
on apache.org.
Arnaud already proposed to create a new virtual host [1] for staging
site and I think it is a pretty good idea, avoiding some doc issues
(i.e. MPIR-53).
Another idea, from MNG-2472, Allan Ramirez offered his space on apache.
Moreover, regarding plugins's project-summary page, I noticed that
some plugin sites are for snapshot version [2], others released
version. Not really uniform and confusing for users... Special
reasons?
Cheers,
Vincent
[1] http://www.nabble.com/CI-for-M1-%3A-Can-I-use-a-continuum-instance-somewhere---tf2051570.html
[2] changelog, changes, clover, compiler, dependency, eclipse, scm,
surefire-report, war
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Staging Plugins Documentation but where?
Posted by Dennis Lundberg <de...@apache.org>.
Vincent Siveton wrote:
> Hi,
>
> During the last month, around 20 plugins documentations have been
> succesfully reviewed and some of them have been staged into user space
> on apache.org.
> Arnaud already proposed to create a new virtual host [1] for staging
> site and I think it is a pretty good idea, avoiding some doc issues
> (i.e. MPIR-53).
> Another idea, from MNG-2472, Allan Ramirez offered his space on apache.
>
> Moreover, regarding plugins's project-summary page, I noticed that
> some plugin sites are for snapshot version [2], others released
> version. Not really uniform and confusing for users... Special
> reasons?
In the case of changelog and changes, which I have published, the reason
is simple: there has not been a release yet.
I have put some thought into this though, as I'm preparing for a release
of the docck-plugin. One thing that struck me as odd is that if you
publish a site from a tag, take the maven-assembly-plugin-2.1 as an
example, the scm information on the site [3] will look weird. Why?
Because the pom.xml for the tagged release [4] has its own scm element
with version information embedded in it, at the end of the file. I
imagine that the average user would want a link to the latest source,
trunk. Perhaps with an option to find released versions of the source.
Apart from having a uniform place to stage sites, we also need to have a
plan for how and when to make all these sites go live. As we do not yet
have the @since annotations in place for mojos this will, in many cases,
need to be coordinated with releases of plugins.
[3]
http://maven.apache.org/plugins/maven-assembly-plugin/source-repository.html
[4]
http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.1/pom.xml?view=markup
>
> Cheers,
>
> Vincent
>
> [1]
> http://www.nabble.com/CI-for-M1-%3A-Can-I-use-a-continuum-instance-somewhere---tf2051570.html
>
> [2] changelog, changes, clover, compiler, dependency, eclipse, scm,
> surefire-report, war
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org