Here's a dumb question...

Will this automatically pick up the latest user's guide, javadocs etc for
the engine for the "devel" directory?

WILL

On 4/9/07, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:

[ This is tagged [COMMITTERS] because if you are not one, this mail is
boring. It is about some Velocity internal house keeping and only
tangential to Velocity development ]

The following sites can be built running a script from
velocity.zones.apache.org. I've rebuilt all of the sites a few times
yesterday and today and it works satisfactory for me:

Velocity main site (velocity.apache.org)
Velocity DocBook Framework site (velocity.apache.org/docbook)
Velocity Site Tools site (velocity.apache.org/site/tools)
Velocity Engine site (velocity.apache.org/engine/devel)

All of these get built the same way:

* log onto velocity.zones.apache.org
* newgrp velocity
* run the appropriate script from /export/homes/velocity/bin

    build_velocity_site.sh
    build_velocity_docbook_site.sh
    build_velocity_site_tools_site.sh
    build_velocity_engine_site.sh

each of these updates the corresponding site into the
/export/home/velocity/deploy folder, then runs "mvn clean site
site:deploy" on the site.

These updates use an offlined maven (mvn -o) to make sure that the
builds stay reproducible.

As the maven installed on velocity.zones has a few patches that
separate it from the "out of the box" maven, offlining is the easiest
way to make sure that these do not get overwritten. The patches are to
Doxia, Doxia-Sitetools and the site and changes plugins and mainly
cosmetic in nature. I expect most of them to be rolled into Maven, if
the glacial pace of the Doxia development ever picks them up.

For the main site, the whole process is also documented on
http://velocity.apache.org/site-building.html (as soon as the mirrors
have picked up the changes).

These scripts are intended to reduce the fear of rebuilding the
sites. We do rebuild by far not often enough, especially the engine
site should be updated as often as possible so that it reflects our
development process.

Please test.

        Best regards
                Henning


--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE,
Linux,               |gls
91054 Buckenhof, Germany   -- +49 9131 506540  | Apache
person              |eau
Open Source Consulting, Development, Design    | Velocity - Turbine
guy     |rwc
                                                                            |m
k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB
7350     |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning
Schmiedehausen |n

               "Save the cheerleader. Save the world."

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Forio Business Simulations

Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com

Reply via email to