On Fri, 10 Oct 2014 11:57:55 -0300, Kalle Korhonen
kalle.o.korho...@gmail.com wrote:
No reason to vote yet as we don't know how the end result would look
like. I think it'd be far better to create a remote branch for all to
see, and
once you know how it's gonna turn out, we can vote on
Yes... It would be a dependency rather than the same package. Either way
it's the same net result (tapestry-ioc on the classpath when all you wanted
was a bean mapper). That's the bloatware I was speaking of.
On 9 Oct 2014 22:19, Thiago H de Paula Figueiredo thiag...@gmail.com
wrote:
On Thu, 09
On Fri, 10 Oct 2014 03:28:52 -0300, Lance Java lance.j...@googlemail.com
wrote:
Yes... It would be a dependency rather than the same package. Either way
it's the same net result (tapestry-ioc on the classpath when all you
wanted was a bean mapper). That's the bloatware I was speaking of.
Git mv
-Original Message-
From: Thiago H de Paula Figueiredo thiag...@gmail.com
Sent: 10/10/2014 16:20
To: Tapestry development dev@tapestry.apache.org
Subject: Re: BeanModel classes as a separate project and/or JAR?
On Fri, 10 Oct 2014 03:28:52 -0300, Lance Java
On Fri, 10 Oct 2014 10:21:34 -0300, Dimitris Zenios
dimitris.zen...@gmail.com wrote:
Git mv
Thanks!
Do you guys think this change should have a vote before it's done?
-Original Message-
From: Thiago H de Paula Figueiredo thiag...@gmail.com
Sent: 10/10/2014 16:20
To: Tapestry
On Fri, Oct 10, 2014 at 6:58 AM, Thiago H de Paula Figueiredo
thiag...@gmail.com wrote:
On Fri, 10 Oct 2014 10:21:34 -0300, Dimitris Zenios
dimitris.zen...@gmail.com wrote:
Git mv
Thanks!
Do you guys think this change should have a vote before it's done?
No reason to vote yet as we
For a BeanModel framework to come packaged with tapestry-ioc feels like
bloatware to me.
On Thu, 09 Oct 2014 10:42:48 -0300, Lance Java lance.j...@googlemail.com
wrote:
For a BeanModel framework to come packaged with tapestry-ioc feels like
bloatware to me.
I suggested a BeanModel JAR with a dependency on Tapestry-IoC, not
including Tapestry-IoC, in case we cannot really make
Hi!
Taking a look at a problem I'm having at my day job right now, I noticed
the BeanModel classes (including PropertyModel, PropertyConduit,
BeanModelSource, etc) could be hugely useful for projects and code that
need to deal with class properties: discovery, reading and writing
Sounds useful. I'm assuming plastic would need to be on the classpath but
tapestry-ioc would not?
On Wed, 08 Oct 2014 13:40:48 -0300, Lance Java lance.j...@googlemail.com
wrote:
Sounds useful. I'm assuming plastic would need to be on the classpath but
tapestry-ioc would not?
I haven't investigated much yet, but it would need a dependency on Plastic
for sure and probably Tapestry-IoC
11 matches
Mail list logo
