On Sat, 2006-02-04 at 18:55 +0100, Kaare Nilsen wrote: > On 04/02/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > > On Sat, 2006-02-04 at 15:02 +0100, jerome lacoste wrote: > > > You will probably want to deploy both your site and your artifact. > > > > We do not publish sites for unreleased plugins. The site should reflect > > the last *released* version. If there is a real reason to publish the > > site, either publish it under your own homedir on beaver (~/public_html) > > which will be exposed on codehaus.org (www.codehaus.org/~user/) or make > > a special area under mojo.codehaus.org that contains snapshot sites. > > > > -- > > Trygve > > > > > Well.. i must disagree, and also to some extent also agree with you > there trygvis. Since we at the mojo project has given people > instructions of how to use the snapshot repository in their project, I > feel it natural to deploy sites for the plugins in the sandbox that > has snapshot releases. Of course when the plugin matures, and gets out > of the sandbox, the documentation on the mojo site should reflect the > latest release, and not the lates version in the trunk.
Seems like I need to clarify. For a sandboxed plugin it shouldn't be a problem deploy a site as it implicitly haven't done a release. On the other hand for released plugins I would assume the site to reflect the latest release on the site. As an average user I would be surprised if the site was different from the version Maven is magically pulling down. -- Trygve
