Thanks Tom. Geir, any remaining legal concerns around this code? (I haven't reviewed its content yet.)
On Mon, 2005-06-13 at 14:16 -0700, Tom wrote: >Hi Daniel, > >thanks for your email. After quite some time I finally got around to do >the velocity-osgi bundle as part of the jakarta-velocity-tools project. >Could you please add it to CVS as I do not have commit rights? > >Notes are below and in OSGI_TODO.txt, please let me know how it goes. > >Cheers >-- >Tom Enderes > >PS: Thanks to Gatewide LLC as velocity-osgi was originaly developed to >be used in this product: http://www.gatewide.com/gw50.html > > >------------- >velocity-osgi >------------- >A build to wrap the current version of velocity into an OSGi bundle. > > >These are the steps performed to add the velocity-osgi build >functionality to the >jakarta-velocity-tools. > > >build.xml >- added property names >- added jar.osgi and compile tasks > >build.properties >- added osgi.jar >- copied osgi.jar (API from OSGi Alliance) into lib folder > >tools/src >- added additional sources for osgi (bundle activator, wrapper for Log etc) >- added properties to start up velocity within OSGi >- added an OSGi manifest for the velocity-osgi bundle > > > > >Daniel L. Rall wrote: > >> 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] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
