l if you could check this for me.
Chris
Von: Alex Harui
Gesendet: Donnerstag, 30. Oktober 2014 18:18
An: dev@flex.apache.org
Betreff: Re: AW: AW: Generic FlexTool interface
On 10/30/14, 7:16 AM, "Christofer Dutz" wrote:
>I wanted to avoid a cyclic dependenc
On 10/30/14, 7:16 AM, "Christofer Dutz" wrote:
>I wanted to avoid a cyclic dependency on a library hosted at Sonatype. In
>the end I want all to be at Apache so I thought it would be best to add
>to Apache Flex.
Yes, I definitely don’t want a dependency on Sonatype stuff. I thought
there was
ave votes
on this and finally release it ... I guess it shouldn't take too long. And it
would be a good test for a first release of a maven artifact ;-)
Chris
Von: Alex Harui
Gesendet: Donnerstag, 30. Oktober 2014 14:42
An: dev@flex.apache.org
Betreff:
I’m ok with it too, but want to check on two alternatives:
1) Could you just release the Apache Flex version of flexmojos with the
interface in there and have the tools depend on that jar? That would be
one less release to vote on wouldn’t it?
2) Is there no other generic tool interface in the o
So I just committed a new "flex-tools-api" module in flex-utils.
I could have a SNAPSHOT version available in no time ... if this is ok with you
guys.
Chris
Von: Erik de Bruin
Gesendet: Donnerstag, 30. Oktober 2014 12:34
An: dev@flex.apache.org
Betreff:
Well the compiler parts in the official SDK, falcon and Flexmojos would use
this jar and there would be changes involved, but no change that would change
any existing logic. I would simply add an "implements FlexTool" and add
implementations for the tree methods, two of which simply return const
