geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sisson (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-2226) Site migration to m2 build
Date Tue, 25 Jul 2006 00:14:14 GMT
Site migration to m2 build
--------------------------

                 Key: GERONIMO-2226
                 URL: http://issues.apache.org/jira/browse/GERONIMO-2226
             Project: Geronimo
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: website
            Reporter: John Sisson
            Priority: Trivial


Currently the Geronimo site is build using Ant.

The Ant build has been recently updated to use Velocity to 1.5-dev (I built from svn rev 386004)
to fix issue where generated html files have inconsistent line endings when building the site
on Windows ( see http://www.mail-archive.com/velocity-dev@jakarta.apache.org/msg11613.html
)

See http://svn.apache.org/viewcvs?rev=386059&view=rev

A conversion to Maven 2 needs to use a version of velocity that has this fix.

You can test whether the version of velocity has the fix by:

    * running touch * in cygwin in the geronimo\site\xdocs directory
    * build the site
    * attempt to check in the generated site files under geronimo\site\docs - if you don't
get any errors about inconsistent line endings then you are using the fixed version of velocity.

For a list of dependencies required by velocity see the doco at http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/xdocs/jar-dependencies.xml
. FYI, the current Ant build loads the jars in the geronimo\site\lib dir onto the classpath.

I don't know if velocity's project.xml file is up to date as they aren't doing builds with
maven yet AFAIK.. http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/project.xml

Looks like we should wait until velocity 1.5 is released as we are currently running from
a velocity 1.5 development build to get around some bugs.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message