Tom, yup! Ideally, we'd avoid duplicating any Velocity source or build code, and wrap your build and source files over the rest.
- Dan On Mon, 2004-11-08 at 00:46 -0800, Tom Enderes wrote: > Hi Daniel, > > sounds good to me. > > So, I still need to modify my build in such a way that it > - locates the relevant velocity classes (they must have been > previously build on the local machine in the > the build.dest directory) > - Then compiles the osgi specific sources against these classes > - packages both into an osgi bundle if compilation worked, using > whatever the current velocity version is. > > And to do all this I should assume a directory structure like > /jakarta-velocity/contrib/velocity-osgi, right? > > Thanks > > Daniel L. Rall wrote: > > > Oh, I'm a lot more than two months behind. ;-) > > > > The contrib area is something used by many open source projects to house > > useful code -- like yours -- which is generally not managed by that > > project or its committers, but instead by outside contributors. It > > generally doesn't ship with the project's deliverables (such as would be > > the case here). It's all about increasing the availability of related > > code which is useful to project participants, but not necessarily > > something the maintainers consider core to the project. > > > > You can see the top level of Velocity's contrib area here: > > > > http://cvs.apache.org/viewcvs.cgi/jakarta-velocity/contrib/ > > > > And the tool-specific area here: > > > > http://cvs.apache.org/viewcvs.cgi/jakarta-velocity/contrib/tools/ > > > > ...which contains emacs, intellij, jedit, and ultraedit plug-ins. We'd > > probably start a new area at the same level as "tools" for your > > contribution. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
