geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sisson (JIRA)" <>
Subject [jira] Closed: (GERONIMO-1748) Site migration to Maven 2
Date Tue, 25 Jul 2006 00:17:14 GMT
     [ ]

John Sisson closed GERONIMO-1748.

    Fix Version/s:     (was: 1.2)
       Resolution: Duplicate
         Assignee: John Sisson

I seem to remember Jacek saying (a while ago..) we should replace the ant code with maven
and this could be done as part of the m2 migration work.  Anyway, it looks like we should
wait until velocity 1.5 is released as we are currently running from a 1.5 development build
to get around some bugs.

Closing this JIRA and have created GERONIMO-2226 .


> Site migration to Maven 2
> -------------------------
>                 Key: GERONIMO-1748
>                 URL:
>             Project: Geronimo
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: website
>    Affects Versions: 1.2
>            Reporter: John Sisson
>         Assigned To: John Sisson
>            Priority: Minor
> 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
> See
> 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
. 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..

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message