I wish I had known this trick a couple of weeks ago. It would have saved me some time. Thanks for the tip!
Raph > -----Original Message----- > From: Anders Bengtsson [mailto:[EMAIL PROTECTED] > Sent: lundi 20 février 2006 14:01 > To: Tapestry users > Subject: RE: Bug 788 and other troubles > > sön 2006-02-19 klockan 14:05 +0100 skrev Raphaël Jean: > > Anders, > > > > We are in the same situation and I feel your pain... > > > > I don't know if there is going to be a 4.0.1 bugfix release soon but it > seems unlikely. > > > > Regarding your other point, I believe the Hivemind source tree is only > needed because Tapestry uses some Hivemind ant build files. What we've > done is to place the hivemind 1.1.1 source tree on our build machine but > not under source control. That way we only store the Tapestry source in > CVS. > > We "solved" our problems by storing the unmodified Tapestry 4.0 jar plus > the few modified source files we needed in version control. Then we > build just those files, and replace the class files in the jar, creating > our own special jar. > It's not pretty, but very fast, and doesn't require us to dive into the > details of Tapestry's build scripts. > > /Anders > > > > --------------------------------------------------------------------- > 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]
