Hi Piotr, These flags are only used by TLF, but TLF was building just fine for a while.
I agree that the current failures appear unrelated, but I want to get it to build locally in order to compare working vs not-working. AFAICT, you can't specify more than one option in additionalCompilerOptions. My local changes lets you separate the list with spaces which works for this, but would someday not work for spaces in paths or quoted spaces, but will at least get us past that point. But I'm still trying to understand how TLF ever built in Maven? Did you see it work at one point in time? -Alex On 8/1/17, 8:43 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Hi Alex, > >I don't recall that we have used CONFIG::debug or CONFIG::release >somewhere >earlier. My thought that if we have ever used and it's defined in loaded >config - Maven shouldn't complain. >I think in order to use it we have to put them in >"additionalCompilerOptions" in pom, but maybe there is some options which >I >don't know. I will check later today and let you know. > ><additionalCompilerOptions>-define+=CONFIG::debug,CONFIG::release</additio >nalCompilerOptions> > >We still may need your fix. > >Thanks, >Piotr > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FRe-MAVEN-BUILD-FlexJS-Framework-mave >n-Build-1129-Still-Failing-tp63607p63631.html&data=02%7C01%7C%7Cb972283546 >4c40bcac0708d4d8f43240%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636371 >990702296109&sdata=JT7v4ivFd%2F2IoDEaR9Ag6A5Uzh7cc6AZqPSjwJ%2B%2BxVM%3D&re >served=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
