No, not necessarily.  But I wanted to see what the general feeling was (better 
to leave as 3rd party vs. better to bring under the tapestry umbrella) before 
committing resources to making the switch.

Robert

On Jan 20, 2011, at 1/206:07 PM , Josh Canfield wrote:

> Do we usually vote before creating new sub-modules? Or is it a better
> to ask forgiveness than permission thing?
> 
> I'm for having more modules, in case that wasn't obvious before.
> Possibly for experimental modules we could have a incubator project...
> 
> 
> On Thu, Jan 20, 2011 at 3:40 PM, Robert Zeigler
> <[email protected]> wrote:
>> The thread on tapestry modules got me thinking a bit...
>> 
>> Awhile back, Kevin Menard and I started an integration library between 
>> tapestry and cayenne (http://cayenne.apache.org).  I know Kevin was hoping 
>> this would eventually move to be an "official" tapestry module (rather than 
>> 3rd party), but I've been reluctant.  What are your thoughts? We have an 
>> "official" hibernate integration module; should we have an "official" 
>> cayenne one? If so, I can move the code into a new tapestry sub-module.  I 
>> use the integration in several of my own projects and keep it compatible 
>> with the current version of tapestry; I would take responsibility for 
>> continuing to maintain the module under the tapestry umbrella.  This isn't 
>> meant to be an official vote, and I'm not set on moving it into tapestry.   
>> I'm just trying to gauge how much interest there would be in having a better 
>> supported cayenne integration module.
>> 
>> Robert
>> ---------------------------------------------------------------------
>> 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]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to