e).
So no worries, that my work would break anything. It will not have any effect
on the current build.
Chris
Von: Alex Harui
Gesendet: Montag, 6. Oktober 2014 06:36
An: dev@flex.apache.org
Betreff: Re: AW: How to handle the groupIds of the default
;
>Chris
>
>
>-Ursprüngliche Nachricht-
>Von: Christofer Dutz [mailto:christofer.d...@c-ware.de]
>Gesendet: Samstag, 4. Oktober 2014 21:03
>An: dev@flex.apache.org
>Betreff: AW: How to handle the groupIds of the default and falcon compiler
>
>No ... not exactl
not yet really
official. I thing tweaking a little is absolutely legitimate.
Chris
-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Gesendet: Samstag, 4. Oktober 2014 18:27
An: dev@flex.apache.org
Betreff: RE: How to handle the groupIds of the default and falcon
legitimate.
Chris
-Ursprüngliche Nachricht-
Von: Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Gesendet: Samstag, 4. Oktober 2014 18:27
An: dev@flex.apache.org
Betreff: RE: How to handle the groupIds of the default and falcon compiler
The 2 solution seems more logical to me, can you
xml in a subfolder of the META-INF directory ? that's just
the way it should be IMO.
Frédéric THOMAS
> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Subject: How to handle the groupIds of the default and falcon compiler
> Date: Sat, 4 Oct 2014 16:09:50 +
>
Hi guys,
sorry for all the flexmojos & maven spam recently, but I'm trying to get some
things finished ;-|
Usually we had all the compiler artifacts deployed with the group-id
"org.apache.flex:compiler" and all oft he artifacts it needed were in
"org.apache.flex.compiler:xxx" (The root artifac
