On 13 May 2013 14:01, GESCONSULTOR - Óscar Bou <[email protected]>wrote:
> > Hi, Dan. > > Thanks for all the answers. > > Regarding the JUnit, my vote would be for releasing it :-) > > It's really, really useful with current functionalities, validating all > actions, beahviours, etc. from JUnit without effort. > > This "functionality" can give quite points to the framework to anyone > evaluating it. > > That's nice to hear, actually. I suspect you are the first team using it earnest (on Estatio we mostly are just writing integration tests). So I'm glad that - what I wrote as a little experiment a few years back - actually does work. > This one is the only "bug" found until now. And it couldn't be considered > as a bug, but an improvement over current functionality, if "wrapping" an > object would mean only to "wrap" the Domain Object properties, and not the > framework's related ones (such as if it's persisted). > > In which case it's a documentation bug, I suppose. It ought to be possible to fix, though. > The problem is that, as it's not released, it's not present on any maven > repository, and forces to download and compile the current snapshop, and > install the junit viewer jar on the local maven repository. > > Perhaps a compromise might be for me to release it out as a snapshot release for now? (but depending only on the other released code so that you can keep as "official" as possible, > But I understand that you don't want to release it if big changes on its > API are planned. But if finally it's released, an option would be to > "mothball" it when the new Apache Isis testing framework that integrates > JUnit and BDD functionalities will be released. > > Yes, that's a possibility. It's not a very good name, anyway, is it. I shall mull on this. Cheers, > > Oscar > >
