we do. Your repo manager will always have to do something
>in order to have flash, air and fontkit installed.
>
>So currently I'll not put that much effort into that.
>
>Chris
>
>Gesendet mit meinem HTC
>
>- Reply message -
>Von: "Frédéric THOMAS"
&
osExtensionInstallationHelper.java
> From: christofer.d...@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: Re : Re^10: Flex SDK Converter Maven Extension available
> Date: Tue, 21 Apr 2015 07:44:41 +
>
> If we were to publish all themes equally as swcs though, I wouldn&#x
__
> Von: Christofer Dutz
> Gesendet: Dienstag, 21. April 2015 07:41
> An: dev@flex.apache.org
> Betreff: AW: Re : Re^10: Flex SDK Converter Maven Extension available
>
> Well actually i should make flexmojos output sensible errors. That me
ow CI builds. If
anything here has changed, I would love to allow that.
Chris
Von: Christofer Dutz
Gesendet: Dienstag, 21. April 2015 07:41
An: dev@flex.apache.org
Betreff: AW: Re : Re^10: Flex SDK Converter Maven Extension available
Well actually i should
t put that much effort into that.
Chris
Gesendet mit meinem HTC
- Reply message -
Von: "Frédéric THOMAS"
An: "dev@flex.apache.org"
Betreff: Re : Re^10: Flex SDK Converter Maven Extension available
Datum: Di., Apr. 21, 2015 01:21
I think it is great as well but would li
I think it is great as well but would like to be able to do a complete build on
CI having the SDK in my repo manager, so at the moment, I still need to rely on
the deployer until a public mavenized version is out.
Otherwize I still have no clue why I add an error:null, hope Ill have more time
t
Not sure I fully understand, but sounds great. Does this mean there is no
mavenizer to be released by Apache Flex?
Thanks,
-Alex
On 4/20/15, 3:23 PM, "Christofer Dutz" wrote:
>Ok ... so with my latest change, I was able to build Flexmojos without
>any Flex related artifacts in my local repo. I
