Re snapshot sites.
This is exactly what i use the site:stage functionality to try and provide.
In my scheme a project basically has two sites, its released site (deployed
to distrMgmt::site::url) and its snapshot site. The snapshot site is
generated with lots of technical reports usefull for project tracking,
governance checks and developer assistance and is built and deployed by a
nightly build - some kind of offical support for this separation (via a new
distroMgmt:snapshotSite type directive or alike) would be good. Ideally I
would like to be able to support multiple versions of my project sites so
that develoeprs using non latest releases can still surf to the javadocs,
usage info, and ideally appropriately tagged SCM links etc but this would
involve me mucking about with various URLs to include the version info.
Cheers,
John
----- Original Message -----
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List" <dev@maven.apache.org>
Sent: Wednesday, February 08, 2006 5:10 AM
Subject: a little more on site structure
I've had some extra thoughts that I didn't want to throw into the others
which were meant to be definitive plans.
a) how do we deal with the separation of transient (developer)
information from project information in a single module (eg
jakarta-commons-foo) scenario?
Perhaps in this case, there's no harm in including the development
reports for a released version in the site, or we use a profile to turn
them off when we deploy to the live site?
b) what about creating separate deployment locations for snapshot sites?
could be done with a profile, but to align with <distributionManagement>
<snapshotRepository> maybe we should have <distributionManagement>
<snapshotSite>.
This would allow us to just drop the reports straight into the site like
we do now without worrying about the layout issues, and turn it on or
off depending on the deployment target. The snapshot one would be
continuously spat out from CI, and users could go to
http://maven.apache.org/2.1-SNAPSHOT to see the site with reports intact
and totally up to date, while maven.apache.org remains the last release
copy.
c) is there a way to designate informational, permanent reports (mailing
list, scm, plugin reference) from point in time reports (junit,
cobertura, even javadoc)?
Some thinking out loud. Anyone want to add anything?
- Brett
---------------------------------------------------------------------
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]
