That separates the core site, but there is still a two issues, and,
unfortunately, I'm not sure if there is an easy way to address it.
First, it is easy to publish specific versions of projects to different
directories. But, the Maven documentation consists of a bunch of related
sites. I think the main challenge is Maven plug-in sites and making sure
that all external links from one version of Maven link to the appropriate
version of another site. Here's where it would be helpful to be able to
provide URL prefixes for outbound links. Instead of linking to a specific
URL.
Second, (and correct me if I'm wrong), a Maven "version" is just a String.
There is no concept in a the POM of a Major vs. a Minor release. So,
although there's seems to be agreement that it doesn't make much sense to
publish a new version of the site for each minor revision, that might not be
possible without adding that concept to Maven (unlikely) or just coding
/ref/2 for a 2.x version instead of using the logic. So while the
replacement logic you have for core is good, it would create a new Maven
site for each minor version release. Maybe that's OK?
On 3/8/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> We already have that in place for the core, the site url is
> maven.apache.org/ref/${project.version}/
> see
> http://svn.apache.org/viewcvs.cgi/maven/components/trunk/pom.xml?rev=382904&view=markup
>
> We're missing the continuous integration part to auto deploy site
> everytime it's changed
>
> On 3/8/06, Tim O'Brien <[EMAIL PROTECTED]> wrote:
> > Having to choose between publishing the latest and greatest docs and
> only
> > the released version is a problem that Maven seems to have created for
> > itself. Same issue comes up in other projects frequently - Commons has
> a
> > problem because some of the sites only publish on a release. Latest and
> > greatest are almost never there.
> >
> > What about publishing the latest and greatest docs to another directory?
> > The Maven site gets pushed to a directory that has a version of a
> > label. http://maven.apache.org/version/1.0
> > , http://maven.apache.org/version/2.0.2, and
> > http://maven.apache.org/version/trunk. This way the Maven site can have
> a
> > nightly publish of the most current Maven site to Trunk every single
> day,
> > but still keep legacy docs around intact for people using older versions
> of
> > the product. The "consumer" site can point to the latest release, and
> the
> > "developer" site can point to "trunk". The Maven site plugin would need
> > some mechanism for adding a skin to a site to clearly identify it as
> > "Development".
> >
> >
> >
> > On 3/7/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > >
> > > On 3/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> > >
> > > > * I'm still a little torn on where plugin docs go. No hurry on this,
> but
> > >
> > > > something to ponder. We definitely need to make the references for
> those
> > > > integrate better. Site/skin inheritance will help
> > >
> > > No matter where they go, I think they need to be updated more often.
> > > Random example... the assembly plugin docs are wrong, and have been
> > > that way for months. (it's descriptorId, not
> > > maven.assembly.descriptorId.)
> > > * http://maven.apache.org/plugins/maven-assembly-plugin/howto.html
> > >
> > > I would like to see the "latest and greatest" docs on the main site.
> > > Yes, they'll be ahead of the released version, but not by much, and
> > > (hopefully) not for long.When the answer to a lot of "X doesn't work"
> > > questions is "It's fixed in the trunk, use a snapshot," it would be
> > > nice to have the snapshot docs available in a centralized place.
> > >
> > > This also makes it more fun to contribute to the documentation,
> > > because you get to see your work "in print" right away.
> > >
> > > Thanks for updating the main site. :)
> > >
> > > --
> > > Wendy
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
