On 9/24/05, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > Now that we've SCXML building nightly [1] in Commons Sandbox, I would > ideally like to eliminate the redundant source trees by removing the > o.a.taglibs.rdc.scxml.* packages, and using the o.a.commons.scxml.* > packages out of the nightly commons-scxml jar for the current RDC > nightlies. Indeed, the scxml packages in Taglibs haven't been updated > lately at all, so we're already seeing a fork. > > Any suggestions from similar experiences? At some point, I'll look at > gump for RDC, but for the Taglibs nightly build I'm not sure how best to > proceed.
In the earlier Struts days, we got ourselves in a bit of a pickle because we were dependent upon unreleased Commons components, and ended up having to delay Struts releases for some time until released versions of our dependencies became available. That led us to change our policy so that we depend only upon released versions of our dependencies. In general, I would recommend the same policy for taglibs. In this particular case, however, since you, Rahul, are currently the driving force behind both the SCXML component and the RDC taglib, I think it would be OK to introduce a dependency from RDC to SCXML, since I assume your left hand knows what your right hand is doing. ;-) As for the mechanics, you might want to consider deploying a "snapshot" of SCXML to the ASF Maven repo (even if you're not using Maven) and using Ant's <get> task to download that in order to build RDC itself. -- Martin Cooper Thanks, > -Rahul > > [1] http://cvs.apache.org/builds/jakarta-commons/nightly/commons-scxml/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
