You know, it just occurred to me that I don't fully understand why Maven is causing the compiler to read a flex-config.xml file. It could have to do with the fact that we simply haven't made a mapping of all compiler options into pom.xml. It should be trivial to have Maven only look for the -config.xml that BaseMojo generates from the POM.
One pain point that would remain is that when you add a new option to the compiler config, you also have to change BaseMojo. That is what I was proposing to solve by teaching the compiler to read the pom, but maybe if BaseMojo can simply pass through all configuration options directly that would eliminate that synchronization step. But then the pom entries would have "-" in them or BaseMojo could insert the dashes as necessary by scanning for capital letters. And that still doesn't solve how Ant, IDE, and command-line users would pick up their configuration options. Food for thought, -Alex On 5/14/17, 7:07 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Btw. If completely remove path-element to typedefs project didn't build >either, but with different stack trace. So removing is not the option. > >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-5-5-git-commit-flex-asjs-refs-hea >ds-release0-8-0-distribution-updated-config-xml-files-used-by-Mae-tp61584p >61588.html&data=02%7C01%7C%7Cbf98b3a329764c987b3608d49ad470cd%7Cfa7b1b5a7b >34438794aed2c178decee1%7C0%7C0%7C636303684602850334&sdata=S2xvKEZMKIivtJ8n >mWaq0NurHvHtUSxKAfV79rLFrQg%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
