On Thu, 2002-12-12 at 18:14, Lester Ward wrote: > I'm building an application that is based on Jetspeed. For various reasons, > we want to compile three of the key components (Velocity, Turbine and > Jetspeed) from source, so I have set them up as subprojects (I think). > > There is one problem (at least): Velocity does not use Maven
There is a maven descriptor in the velocity repository. I just cleaned it up a bit too and should work. > and Jetspeed's > Maven support won't work until (supposedly) beta 3 (on beta 2 right now). Bug David Taylor :-) I know he's been wanting to get the Maven build working. > Dependency-wise, Turbine relies on Velocity. Jetspeed relies on Turbine. My > app relies on Jetspeed. > > My project directory (itag) looks like so (roughly): > > itag > src > jakarta-jetspeed > src > jakarta-turbine-2 > src > jakarta-velocity > src > maven.xml > project.xml > ... etc. ... > > How would you go about compiling this thing? I have it working with a weird > amalgam of stuff, but it is pretty kludgy. For example, my main maven.xml > file runs an Ant script that: a) compiles velocity by invoking its Ant > script, b) compiles Turbine by calling Exec to run Maven (!) and c) compiles > jetspeed by calling Exec to run it's build.bat file (this is a Win32 > system). I would take a day and help get the Jetspeed POM working and save yourself a lot of grief. Jetspeed is the only project that needs work, then you can use the reactor. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
