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
I read up a bit more on Maven ids. One question I have is: Can there be more than one jar per artifactid? For the current org.apache.flex:compiler, isn't there multiple jars for that "coordinate"? Looking way ahead, within the compiler.jx folder, there is the possibility of multiple output targe

AW: [Discuss] Naming of Falcon/FlexJS artifacts

2016-02-20 Thread Christofer Dutz
Hi Alex, I agree with most of your thoughts, but my intention was to make it simpler for people to get started, having to know all of the history just in order to know which artifacts to get doesn't make things easier. I guess the best thing would have been, if we didn't change the groupIds an