Exactly, that's why i'm wondering if there's a third alternative... And keep in mind i'm mostly talking about the (possible) new subprojects like osgi and not the existing ones that people expect to be in sync
On Mon, Jul 14, 2008 at 10:00 PM, Robert Zeigler <[EMAIL PROTECTED]> wrote: > Yes and no. > On the one hand, it's nice for each sub-project to have its own release > lifecycle, etc. > On the other hand, it makes it really easy to know what is compatible with > what. > Consider a scenario like: > tapestry-core 5.0.14 requires: > tapestry-ioc 5.0.7 > tapestry-annotations 5.0.3 > Since it's a hibernate-based app, we'll be using: > tapestry-hibernate 5.0.9 > > Hm... what are the dependencies of tapestry-hibernate 5.0.9? Is it on > tapestry-core 5.0.9? Or later? Or 5.0.14? Or...? > Keeping the version numbers and the releases in-sync makes it easier for a > person to wrap his/her head around what goes with what. > > Robert > > On Jul 14, 2008, at 7/141:19 PM , Andreas Andreou wrote: > >> Wouldn't it make sense to consider subprojects having different lifecycle >> that >> the master project? >> >> So that you could have a release as soon as a major issue in that >> specific project >> is fixed - instead of having to do a global release and update version >> numbers of >> everything else? >> >> On Mon, Jul 14, 2008 at 8:59 PM, Robert Zeigler <[EMAIL PROTECTED]> >> wrote: >>> >>> +1 on keeping "integration" code in separate modules from core. >>> >>> Robert >>> >>> On Jul 13, 2008, at 7/134:32 PM , Howard Lewis Ship wrote: >>> >>>> It's very late in the 5.0 cycle to introduce something new. I'd >>>> prefer to see this as part of 5.1 ... it may be time to start thinking >>>> about cutting a branch for 5.1 work that we can merge into trunk once >>>> 5.0 is GA. My gut feeling is that this could be a tapestry-osgi >>>> add-on library. >>>> >>>> On Sun, Jul 13, 2008 at 8:41 AM, Igor Drobiazko >>>> <[EMAIL PROTECTED]> wrote: >>>>> >>>>> Hello Howard, >>>>> >>>>> as already mentioned in the tapestry user list I'm working on embedding >>>>> Tapestry into an OSGi application. >>>>> We already solved the problems mentioned in this thread >>>>> >>>>> >>>>> http://www.nabble.com/ClassNameLocatorImpl-in-OSGi-td18204202.html#a18204202 >>>>> >>>>> I would like to make the OSGi support available for all. Do you think >>>>> we >>>>> can >>>>> add it to tapestry-core? Shall we maybe start a new module >>>>> tapestry-osgi? >>>>> This OSGi integration doesn't require new dependencies and consists of >>>>> 4-6 >>>>> classes (most of them are decorators of the Servlet API). It allows you >>>>> to >>>>> start Tapestry within OSGi environment. Furthermore it allows you to >>>>> inject >>>>> OSGi services into Tapestry pages in the same way we inject Spring >>>>> beans. >>>>> >>>>> Shall I add a jira issue for it and assign it to me? >>>>> >>>>> >>>>> May I also ask you to comment this issue? >>>>> https://issues.apache.org/jira/browse/TAPESTRY-2519 >>>>> >>>>> -- >>>>> Best regards, >>>>> >>>>> Igor Drobiazko >>>> >>>> >>>> >>>> -- >>>> Howard M. Lewis Ship >>>> >>>> Creator Apache Tapestry and Apache HiveMind >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >> >> >> >> -- >> Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr >> Tapestry / Tacos developer >> Open Source / JEE Consulting >> >> --------------------------------------------------------------------- >> 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] > > -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
