On 5/18/12 6:28 AM, "christofer.d...@c-ware.de" <christofer.d...@c-ware.de>
wrote:
> Yeah ... I found out that this would be a messy task ... even the guys from
> Adobe didn't want to submit their patches as they considered them far to messy
> to contribute :-(
> Think I'll just stick to reuse versions of oder sdks if they haven't changed.
>
> Chris
>
Hi, thanks for looking into this. Some possibly useful information:
0) I don't know much about Maven, so I could be completely off.
1) I think it is more important to make Flex usable in Maven than to make it
work with FlexMojos. IOW, FlexMojos may also be burdened with legacy of
having to work with Flex's idiosyncracies and we actually now have the
ability to change some aspects of Flex to make them work better with Maven.
Starting over might be the best bet and eliminates a dependency on something
that is not part of Apache Flex
2) Flex's use of Batik might really require a copy-and-rename. I'm pretty
sure there are some non-standard extensions to Batik CSS which is why our
changes never got contributed back. Not sure about Xerces. So, we might
fork Batik, give it a new package (org.apache.flex) and use our forked copy.
Especially if that makes Maven integration easier.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
