Re: Where to begin?
Alex Karasulu <[email protected]>
| Newsgroups | gmane.comp.jakarta.avalon.user |
|---|---|
| Message-ID | <[email protected]> |
All of Steve's changes have been committed to SVN so please just update svn and you should be good to go. Alex Stephen McConnell wrote: > Stephen McConnell wrote: > >> David Leangen wrote: >> >>> First, I ran "ant clean" from AVALON_HOME. >>> >>> Also deleted my existing ".magic" directory to be sure I start of >>> clean. >>> >>> >>>> I've just redefined my MAGIC_HOME and after running 'ant setup' >>>> I have the following sub-directories under MAGIC_HOME: >>>> >>>> /docs >>>> /themes >>>> /main >>>> /templates >>> >>> >>> >>> >>> Yep. >>> >>> Also have a magic.properties file. >>> >>> >>> >>>> Under /main I have two subdirecories: >>>> >>>> >>>> /avalon >>>> /xavalon >>>> >>> >>> >>> Don't know if that's just a typo or not, but to be precise, I have: >>> >>> /avalon >>> /avalonx >>> >> >> it was a type - your structure is correct. >> >>> >>>> If I cd to runtime/logkit and do the following: >>>> >>>> >>>> $ ant >>>> >>>> >>>> The result of the build is placed in %MAGIC_HOME%\main\avalon\logkit\ >>>> - and everything looks good. Is that the same case for you? >>> >>> >>> >>> >>> In addition to "avalon" and "avalonx", this build also created the >>> following in %MAGIC_HOME%\main: >>> >>> /geronimo-spec >>> /log4j >>> /serletapi >>> >>> Under %MAGIC_HOME%\main\avalon\, in addition to "logkit", it also >>> created >>> a "tools" directory. >>> >>> And, as you said, everything looks good in the logkit dir. >>> >> >> OK - this confirms that the problem is in AbstractMerlinUnitTest when >> its setting up the cache reference. I'm kicking of a build now so in >> principal I should end up with the same error. I'll post some more >> info as soon as I have chassed this one down (which should not take >> long). > > > Bug located. > > In the AbstractMerlinTestCase (an unit test that embeds Merlin) we are > not setting the application repository to the magic cache. I'm just > chatting with Alex about this on ICQ - should have a fix shortly. > > Steve. >