You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@velocity.apache.org by Daniel Rall <dl...@collab.net> on 2004/11/05 00:53:50 UTC

Re: Fwd: Velocity & OSGi

On Mon, 2004-08-23 at 23:38 -0700, Tom wrote:
> Hello,
> 
> as I think Velocity is not only useful for back-end servers running
> big applications, I have packaged Velocity to run in the OSGi framework 
> (as a velocity-osgi bundle).
> Simplifying it a bit, the OSGi framework can be looked at as an open 
> programming standard for embedded servers (www.osgi.org). Its most 
> successfull applications include deployments in cars (BMW) and the 
> plugin architecture for Eclipse M3.
> 
> What about extending the Velocity build in such a way that it can create 
> the "velocity-osgi" bundle?

Tom, we might be able to find a place for your code in the contrib area.


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org

Re: Velocity & OSGi

Posted by Will Glass-Husain <wg...@forio.com>.

Geir made a mistake - you'll want to use Bugzilla.  (Some Apache projects 
use JIRA, some use Bugzilla).  Use the web client at:

http://issues.apache.org/bugzilla

Thanks again for contributing.

Best, WILL

----- Original Message ----- 
From: "Tom" <ec...@gatewide.com>
To: "Velocity Developers List" <ve...@jakarta.apache.org>
Cc: <dl...@finemaltcoding.com>
Sent: Monday, June 13, 2005 7:36 PM
Subject: Re: Velocity & OSGi


> Hi Geir,
>
> it was done by me, not work for hire and a fairly small contribution in 
> regards to lines of code. It has always had the apache license in it 
> (which states that ASF owns the copyright?).
>
> I am just downloading the JIRA client; could you please point me to a FAQ 
> / Wiki how to use this to submit the code?
>
> Thanks
> --
> Tom Enderes
>
>
>
>
> Geir Magnusson Jr. wrote:
>
>> Hang on.
>>
>> We can't accept this in this way for IP reasons.
>>
>> We will need information about the relationship, and who the  copyright 
>> owner is - was it a work for hire?
>>
>> Also, rather than sending this way, if the contribution is "small" (I 
>> have yet to look) adding via JIRA is best, as you have to confirm  that 
>> this is a contribution under the apache license.
>>
>> If it's large, we'll need a software grant (a very simple form which 
>> says you are the owner of the (c) and have the right to grant the ASF  a 
>> license for it...)
>>
>> geir
>>
>>
>> On Jun 13, 2005, at 5:24 PM, Tom Enderes 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
>>>
>>>
>>> <<ATTACHMENT EXCLUDED>>
>>>
>>> -------------
>>> 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: velocity-dev-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org

Re: Velocity & OSGi

Posted by Tom <ec...@gatewide.com>.

Hi Geir,

it was done by me, not work for hire and a fairly small contribution in 
regards to lines of code. It has always had the apache license in it 
(which states that ASF owns the copyright?).

I am just downloading the JIRA client; could you please point me to a 
FAQ / Wiki how to use this to submit the code?

Thanks
--
Tom Enderes




Geir Magnusson Jr. wrote:

> Hang on.
> 
> We can't accept this in this way for IP reasons.
> 
> We will need information about the relationship, and who the  copyright 
> owner is - was it a work for hire?
> 
> Also, rather than sending this way, if the contribution is "small" (I  
> have yet to look) adding via JIRA is best, as you have to confirm  that 
> this is a contribution under the apache license.
> 
> If it's large, we'll need a software grant (a very simple form which  
> says you are the owner of the (c) and have the right to grant the ASF  a 
> license for it...)
> 
> geir
> 
> 
> On Jun 13, 2005, at 5:24 PM, Tom Enderes 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
>>
>>
>> <<ATTACHMENT EXCLUDED>>
>>
>> -------------
>> 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: velocity-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org

Re: Velocity & OSGi

Posted by jules djilo <ju...@yahoo.fr>.

Hallo 
I have done a Practice work in Germany with Velocity, 
it is about 60 Pages in Germany.


"Daniel L. Rall" <dl...@finemaltcoding.com> a écrit :
On Tue, 2005-06-14 at 09:23 -0700, Tom wrote:
> Hi Will and Geir,
> 
> created bug 35362, as suggested.
> 
> As requested, short info on OSGi:
> Simplifying it a bit, the OSGi framework can be looked at as an open 
> programming standard for embedded servers (www.osgi.org). Its most 
> successfull applications include deployments in cars (BMW) and the 
> plugin architecture for Eclipse M3. It supports dynamic loading and 
> unloading of OSGi components (called BUNDLES), HttpServices, 
> LogServices, User Management a Device Acess Model.
> 
> My contribution just exposes velocity in an osgi-conform way (e.g. it 
> wraps it into the velocity-osgi Bundle) which can easily deployed in any 
> OSGi framework implementation.
> 
> Please let me know once it is in CVS so that I can post it to the OSGi 
> Open Source newsgroups.

I'll take a stab and integrating this if no one else gets around to it
first.

- Dan



---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org


		
---------------------------------
 Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
 Téléchargez le ici !

Re: Velocity & OSGi

Posted by "Daniel L. Rall" <dl...@finemaltcoding.com>.

On Tue, 2005-06-14 at 09:23 -0700, Tom wrote:
> Hi Will and Geir,
> 
> created bug 35362, as suggested.
> 
> As requested, short info on OSGi:
> Simplifying it a bit, the OSGi framework can be looked at as an open 
> programming standard for embedded servers (www.osgi.org). Its most 
> successfull applications include deployments in cars (BMW) and the 
> plugin architecture for Eclipse M3. It supports dynamic loading and 
> unloading of OSGi components (called BUNDLES), HttpServices, 
> LogServices, User Management a Device Acess Model.
> 
> My contribution just exposes velocity in an osgi-conform way (e.g. it 
> wraps it into the velocity-osgi Bundle) which can easily deployed in any 
>   OSGi framework implementation.
> 
> Please let me know once it is in CVS so that I can post it to the OSGi 
> Open Source newsgroups.

I'll take a stab and integrating this if no one else gets around to it
first.

- Dan



---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org

Re: Velocity & OSGi

Posted by Tom <ec...@gatewide.com>.

Hi Will and Geir,

created bug 35362, as suggested.

As requested, short info on OSGi:
Simplifying it a bit, the OSGi framework can be looked at as an open 
programming standard for embedded servers (www.osgi.org). Its most 
successfull applications include deployments in cars (BMW) and the 
plugin architecture for Eclipse M3. It supports dynamic loading and 
unloading of OSGi components (called BUNDLES), HttpServices, 
LogServices, User Management a Device Acess Model.

My contribution just exposes velocity in an osgi-conform way (e.g. it 
wraps it into the velocity-osgi Bundle) which can easily deployed in any 
  OSGi framework implementation.

Please let me know once it is in CVS so that I can post it to the OSGi 
Open Source newsgroups.

Thanks
Tom



---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org

Re: Velocity & OSGi

Posted by "Geir Magnusson Jr." <ge...@apache.org>.

On Jun 13, 2005, at 11:02 PM, Will Glass-Husain wrote:

> Thanks Geir for the comment.  Makes sense.  And Tom - thanks for
> contributing!
>
> As a sidenote, we're still on Bugzilla, not JIRA.  (although there's a
> movement to migrate to JIRA - Geir are you in favor?)

Hell yes :)

>
> By the way, Tom - your zip didn't make it through the mailer.  Use  
> bugzilla
> to attach it.
>
> Best,
> WILL
>
> P.S.  For those of us not familiar with it, maybe you could send a  
> very short summary of OSGi to the list, and what your package  
> accomplishes?
>
> ----- Original Message ----- From: "Geir Magnusson Jr."  
> <ge...@apache.org>
> To: "Velocity Developers List" <ve...@jakarta.apache.org>
> Cc: <dl...@finemaltcoding.com>
> Sent: Monday, June 13, 2005 4:13 PM
> Subject: Re: Velocity & OSGi
>
>
>
>> Hang on.
>>
>> We can't accept this in this way for IP reasons.
>>
>> We will need information about the relationship, and who the   
>> copyright
>> owner is - was it a work for hire?
>>
>> Also, rather than sending this way, if the contribution is "small" (I
>> have yet to look) adding via JIRA is best, as you have to confirm   
>> that
>> this is a contribution under the apache license.
>>
>> If it's large, we'll need a software grant (a very simple form  
>> which  says
>> you are the owner of the (c) and have the right to grant the ASF  a
>> license for it...)
>>
>> geir
>>
>>
>> On Jun 13, 2005, at 5:24 PM, Tom Enderes 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
>>>
>>>
>>> <<ATTACHMENT EXCLUDED>>
>>>
>>> -------------
>>> 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: velocity-dev-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail: velocity-dev- 
>>>> help@jakarta.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: velocity-dev- 
>>> help@jakarta.apache.org
>>>
>>>
>>>
>>
>> -- 
>> Geir Magnusson Jr                                  +1-203-665-6437
>> geirm@apache.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>

-- 
Geir Magnusson Jr                                  +1-203-665-6437
geirm@apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org

Re: Velocity & OSGi

Posted by Will Glass-Husain <wg...@forio.com>.

Thanks Geir for the comment.  Makes sense.  And Tom - thanks for
contributing!

As a sidenote, we're still on Bugzilla, not JIRA.  (although there's a
movement to migrate to JIRA - Geir are you in favor?)

By the way, Tom - your zip didn't make it through the mailer.  Use bugzilla
to attach it.

Best,
WILL

P.S.  For those of us not familiar with it, maybe you could send a very 
short summary of OSGi to the list, and what your package accomplishes?

----- Original Message ----- 
From: "Geir Magnusson Jr." <ge...@apache.org>
To: "Velocity Developers List" <ve...@jakarta.apache.org>
Cc: <dl...@finemaltcoding.com>
Sent: Monday, June 13, 2005 4:13 PM
Subject: Re: Velocity & OSGi


> Hang on.
>
> We can't accept this in this way for IP reasons.
>
> We will need information about the relationship, and who the  copyright
> owner is - was it a work for hire?
>
> Also, rather than sending this way, if the contribution is "small" (I
> have yet to look) adding via JIRA is best, as you have to confirm  that
> this is a contribution under the apache license.
>
> If it's large, we'll need a software grant (a very simple form which  says
> you are the owner of the (c) and have the right to grant the ASF  a
> license for it...)
>
> geir
>
>
> On Jun 13, 2005, at 5:24 PM, Tom Enderes 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
>>
>>
>> <<ATTACHMENT EXCLUDED>>
>>
>> -------------
>> 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: velocity-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>
>>
>
> -- 
> Geir Magnusson Jr                                  +1-203-665-6437
> geirm@apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org

Re: Velocity & OSGi

Posted by "Geir Magnusson Jr." <ge...@apache.org>.

Hang on.

We can't accept this in this way for IP reasons.

We will need information about the relationship, and who the  
copyright owner is - was it a work for hire?

Also, rather than sending this way, if the contribution is "small" (I  
have yet to look) adding via JIRA is best, as you have to confirm  
that this is a contribution under the apache license.

If it's large, we'll need a software grant (a very simple form which  
says you are the owner of the (c) and have the right to grant the ASF  
a license for it...)

geir


On Jun 13, 2005, at 5:24 PM, Tom Enderes 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
>
>
> <<ATTACHMENT EXCLUDED>>
>
> -------------
> 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: velocity-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>

-- 
Geir Magnusson Jr                                  +1-203-665-6437
geirm@apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org