Well the one is needed at compile & runtime, the rest are code that is only needed at build time. You should never bundle build code with your product. In the Maven world "yet another artifact" usually doesn't matter, cause the tool takes care of managing this.
Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Samstag, 20. Februar 2016 17:45 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: [FALCONJX]Compiling Falcon with externs problems On 2/20/16, 7:32 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Another thing I just noticed: >We have even more tools that are needed during the build: >- AnnotateClass.java >- ProblemEnumGenerator.java >- ProblemLocalizer.java > >So I guess it would be good if I just moved those 3 together with the >UnknownTreePatternInputOutput into a separate falcon-build-tools project >and extend my maven plugin to support 4 goals to trigger all of them via >maven. Of course you can continue to call them all the same way you >always did via Ant with slightly adjusted paths. That's fine with me. I was wondering if even the IASNodeAdapter that Jburg needs can go with all of these into one jar. Then there is only one new artifact. -Alex
