So I updated the documentation on https://cwiki.apache.org/confluence/display/FLEX/Preparing+FDKs+for+Maven+builds with this new option :-)
Chris ________________________________________ Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Donnerstag, 4. Juni 2015 14:52 An: dev@flex.apache.org Betreff: Found the problem in the maven-extension :-D YAAAAAAAY!!! Ok ... now today I had another look at the problems I was having with the maven extension. While it worked great being manually installed in Maven lib/ext dir ... I totally didn't like this option. Maven 3.3.1 came with another option, to specify a ".mvn/extensions.xml" in the maven projects root dir and to use the extensions placed there. The cool thing with this option, is that the extensions are also automatically downloaded. So now all you need to do, is to add the following extensions.xml in a ".mvn" directory in your projects root and the mavenizer should kick in :) <extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd";> <extension> <groupId>org.apache.flex.utilities.converter</groupId> <artifactId>maven-extension</artifactId> <version>1.0.0-SNAPSHOT</version> </extension> </extensions> So I think ... if Alex eventually agrees to my "system-id-to-accept-adobe-license" we'd be ready to go for a release. As this was the last Issue I had on my radar :-) Chris
