This all came back to the beginning. The tests(Falcon, etal) were a nightmare, I'm talking 2012.
When I started writing the FalconJX compiler and created falcon.jx and falcon.jx.tests Eclipse projects, I needed something that worked, so I created the template file so it would work in the two projects I was developing. I didn't need to run the falcon tests all the time. Anyway, it's just one of those legacy hacks that can be corrected by somebody that knows how to fix it. :) Mike On Mon, Feb 15, 2016 at 12:16 PM, Josh Tynjala <joshtynj...@gmail.com> wrote: > I think I found that you need to add unittest.properties in both compiler > and compiler.jx. The readme file has details about what properties should > be defined. It's near the bottom, as I recall, which means it's easy to > miss. > > I agree with Harbs that we should probably make this simpler. Instead of a > separate properties file for tests, why not use env.properties? > > - Josh > On Feb 15, 2016 8:01 AM, "Harbs" <harbs.li...@gmail.com> wrote: > > > Where do I need to set the unittest.properties file? > > > > I’m happy to do so, but I think it would be great if we could at least > get > > some instructions on everything needed to build from source. > > > > Every time I come back to this, I have trouble. Maybe it’s just me, but > it > > seems like it raises the bar needed to contribute. > > > > On Feb 15, 2016, at 5:01 PM, Alex Harui <aha...@adobe.com> wrote: > > > > > > > > > > > On 2/14/16, 11:52 PM, "Harbs" <harbs.li...@gmail.com> wrote: > > > > > >> Cleaning the repo seemed to have helped somewhat, but I still could > not > > >> compile, and I’m assuming because I need to build falcon: > > >> Buildfile: > > >> > > > /Users/harbs/Documents/ApacheFlex/flex-asjs/frameworks/projects/XML/build. > > >> xml > > >> > > >> clean: > > >> > > >> check-falcon-home: > > >> [echo] FALCON_HOME is > > >> /Users/harbs/Documents/ApacheFlex/flex-falcon/compiler > > >> > > >> check-falconjx-home: > > >> [echo] FALCONJX_HOME is > > >> /Users/harbs/Documents/ApacheFlex/flex-falcon/compiler.jx > > > > > > This implies you still have environment variables set somehow. The > > > defaults would use relative paths with ../ in them. > > > Do you have an env.properties file or local.properties file? > > > > > > > > >> > > >> unit.tests: > > >> [junit] unittest.properties not found > > >> [junit] environment property - FLEX_HOME = > > >> > > /Users/harbs/Documents/ApacheFlex/flex-falcon/compiler/generated/dist/sdk > > >> [junit] environment property - PLAYERGLOBAL_HOME = > > >> > > > /Users/harbs/Documents/ApacheFlex/flex-falcon/compiler/generated/dist/sdk/ > > >> frameworks/libs/player > > >> [junit] environment property - PLAYERGLOBAL_VERSION = 11.1 > > >> [junit] environment property - TLF_HOME = null > > >> [junit] environment property - AIR_HOME = null > > >> [junit] environment property - FLASHPLAYER_DEBUGGER = null > > > > > > I will spend time today trying to get the build to work without > > > unittest.properties files, but I think it will still require setting > > > PLAYERGLOBAL_HOME, AIR_HOME, FLASHPLAYER_DEBUGGER and maybe > > > PLAYERGLOBAL_VERSION in the environment. I have spent several hours > > > already trying to make sure folks don't have to specify relative paths > to > > > other Apache Flex repos, but right now we don't have a good way to > guess > > > where folks put the Adobe stuff. > > > > > > -Alex > > > > >
