AW: AW: AW: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-21 Thread Christofer Dutz
ss] Naming of Falcon/FlexJS artifacts On 2/21/16, 7:45 AM, "Christofer Dutz" wrote: >Hi Alex, > >well in general per groupId:artifactId:version tuple there is only one >jar, but that artifact can provide dependencies to other artifacts with >an other groupId and/or ar

Re: AW: AW: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-21 Thread Alex Harui
On 2/21/16, 7:45 AM, "Christofer Dutz" wrote: >Hi Alex, > >well in general per groupId:artifactId:version tuple there is only one >jar, but that artifact can provide dependencies to other artifacts with >an other groupId and/or artifactId which is then transitively pulled in. >Above that there

AW: AW: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-21 Thread Christofer Dutz
a training in these basic things. I just finished such a training and it took about 1 day to understand the concepts. Chris Von: Alex Harui Gesendet: Sonntag, 21. Februar 2016 16:33 An: dev@flex.apache.org Betreff: Re: AW: [Discuss] Naming of Falcon

Re: AW: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-21 Thread Alex Harui
patibility. > >And just as a side info ... I think Maven doesn't like things such as >"2.0" in the groupId. > >Chris > >____________ >Von: Alex Harui >Gesendet: Sonntag, 21. Februar 2016 07:30 >An: dev@flex.apache.org >Bet

AW: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-20 Thread Christofer Dutz
#x27;t like things such as "2.0" in the groupId. Chris Von: Alex Harui Gesendet: Sonntag, 21. Februar 2016 07:30 An: dev@flex.apache.org Betreff: Re: [Discuss] Naming of Falcon/FlexJS artifacts More thoughts: Falcon was actually never int

Re: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-20 Thread Alex Harui
More thoughts: Falcon was actually never intended to be the product name for the compiler. Adobe teams often used code-names for the code. Adobe released flex-falcon/compiler as ASC2.0. We could call flex-falcon/compiler MXMLC2.0 since we completed the MXML support (or at least, lots of it) onc

Re: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-20 Thread Alex Harui
So in theory, the SWF compiler in flex-falcon/compiler, the Flash Builder integration jar in flex-falcon/flex-oem-compiler, and the FDB debugger in flex-falcon/debugger will some day replace MXMLC and its FDB for compiling future Flex (as well as FlexJS) SWFs. Then we have the cross-compiler or tr

[Discuss] Naming of Falcon/FlexJS artifacts

2016-02-20 Thread Christofer Dutz
Hi, while I see an actual chance to have Falcon built with maven and hereby producing Maven artifacts, I think we should discuss the coordinates these artifacts are created under. Currently I was using "org.apache.flex.compiler:falcon-compiler" while the normal compiler was "org.apache.flex.