tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Drobiazko <igor.drobia...@gmail.com>
Subject Re: Tapestry subprojects (was: [jira] Commented: (TAP5-1421) Create a standard way to track messages to be presented to the user)
Date Fri, 21 Jan 2011 14:02:08 GMT
Separate releases will be a hell sooner a later. That's why I'm against
them. Hibernate guys used to release their modules with different versions
and it was a nightmare. I think the stoped it and we should not do it.

On Fri, Jan 21, 2011 at 2:53 PM, Andreas Andreou <andyhot@di.uoa.gr> wrote:

> On Fri, Jan 21, 2011 at 13:45, Massimo Lusetti <mlusetti@gmail.com> wrote:
> > On Fri, Jan 21, 2011 at 11:13 AM, Andreas Andreou <andyhot@di.uoa.gr>
> wrote:
> >
> >> On another note, i'm not sure why tapestry-upload needs a separate
> subproject
> >> (one can manually exclude commons-fileupload)
> >
> > That's a good question...
> >
>
> In fact, having separate releases would be the only good justification
> for this. I took a look
> at the commit history [1] and from 5.1.0.0 till 5.3.0-SNAPSHOT,
> tapestry-upload's only
> "real" changes where [2] and [3], the former just before 5.2.0 and the
> latter just before 5.2.1
>
> [1] https://github.com/apache/tapestry5/commits/trunk/tapestry-upload
> [2] end of
> https://github.com/apache/tapestry5/commit/7a521c1185fef67bf24a69ec248164f33d4ae136
> [3]
> https://github.com/apache/tapestry5/commit/614c10ae1809beb13d91123f5573da60db017560
>
> On the minus side, separate releases can result in user frustration &
> make offering help in
> the lists more difficult...
>
> We could tackle that and shield the user by having Tapestry do some
> version checking
> on bootstrap (though it's not obvious how older modules can signal
> that they're compatible with newer tapestry versions, i.e. it could very
> well
> be the case that tapestry-upload 5.2 works as is in tapestry 5.3 but
> its metadata will not
> contain that information )... anyway, i dont have a solution yet, but
> if we don't offer such a
> runtime service to the users, separate releases can quickly become a hell.
>
> ---------------------------------------------------------------------
> 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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message