You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Robert Zeigler <ro...@roxanemy.com> on 2011/01/21 00:40:53 UTC
tapestry-cayenne library
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: tapestry-cayenne library
Posted by Robert Zeigler <ro...@roxanemy.com>.
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
> <ro...@roxanemy.com> 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: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: tapestry-cayenne library
Posted by Josh Canfield <jo...@gmail.com>.
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
<ro...@roxanemy.com> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: tapestry-cayenne library
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
+1 to an official Tapestry-Cayenne module (as long as its code has the
quality the Tapestry project requires, but this will not be a problem to
Robert and Kevin at all). People tend to trust official modules more than
third-party ones.
On Thu, 20 Jan 2011 21:40:53 -0200, Robert Zeigler
<ro...@roxanemy.com> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
Coordenador e professor da Especialização em Engenharia de Software com
Ênfase em Java da Faculdade Pitágoras
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: tapestry-cayenne library
Posted by Igor Drobiazko <ig...@gmail.com>.
Adding new modules to Apache SVN we need to have at least one committer
responsible for this module. Will you have time in the future to maintain
it? If so, I have no concerns.
On Fri, Jan 21, 2011 at 12:40 AM, Robert Zeigler <
robert.zeigler@roxanemy.com> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Best regards,
Igor Drobiazko
http://tapestry5.de