----- Original Message ----- From: "Dominique Devienne" <[EMAIL PROTECTED]> To: "'Ant Developers List'" <[EMAIL PROTECTED]> Sent: Monday, August 12, 2002 7:20 AM Subject: RE: jspc fixed up but now broken due to other jasper changes.
> Then embed an optional <mapper> in <jspc> that would allow forward > compatibility... Would probably still need to be a FAQ, but at least there > would be a turn-around in case the mapping changes again in the future. --DD agreed. There is some mapping stuff in the architecture; each compiler adapter has to provide its own mapper, but we only supply a default one. Pulling it out to a mapper gives extra flexibility. The other approach is to have different adapters for different jasper versions, maybe even inside jasper itself. > -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 10, 2002 2:24 AM > To: Ant Developers List > Subject: jspc fixed up but now broken due to other jasper changes. > > ok, jspc is working again. looked like a schroedingbug to me: now that I > look at the code the cat is quite clearly deceased and has been for some > time. > > Bug is fixed, new tests are in there to kill two other issues with jspc. > That leaves the show-stopper of directory handling. > > We are passing gump right now but this is accidental, it is because > tomcat-4.0 is not building, so there is no jasper for the jspc test. The > moment that comes back it may break, but this time with assertion > failures -certainly it does with 4.1beta8. The problem is that the tests are > set up for a version of jasper that maps 'simple.jsp' to 'simple.java'. wierd; it is still breaking with classpath errors. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
