Hi Justin,
I haven't tested the Artifacts the Ant release produces for its buildability with Ant. I guess I would not expect it to (but be happy if it did), I'll give that a try right away as this doesn't require the huge setup of the Ant build. Actually you probably would have to run 5 builds in exatly this order to get everything to pass: 1. compiler-jburg-types:1.0.0 2. compiler-build-tools:1.0.0 3. compiler:0.7.0 4. flexjs-typedefs:0.7.0 5. flex-asjs:0.7.0 This will only be needed as long as we don't have a version of the first two out in the wild. I would currently expect the versions of the first two to be 1.1.0-SNAPSHOT, so building them first will probably not bring the solution to build problems in general. Alternatively the staging repo could be added to the repo-list. Then maven would download those artifacts from the ASF repo and build the rest the normal way. Ahhh yes ... and another thing I noticed when performing the release is that I removed the "compiler" and "utils" profile in the maven build as this was causing problems with the release. In order to do what the utils profile did, just go into the compiler-jburg-types and compiler-build-tools directory and to a "mvn clean install" ... but as I stated earlier, this will produce "1.1.0-SNAPSHOT" versions. For now I would just claim that the Ant release isn't intended on being built with Maven untill we have the first binaries for jburg-types and build-tools out the door. The Mavenizer should automatically kick in to download and deploy the playerglobal if your Maven version is 3.3.1 or greater. I didn't pick the 20 for any reason. I think it was the default in some of the Ant scripts. I also thought that by using an older version, the build will also work for older Flash versions. As we aren't using features of new versions (not that I know of), I thought this is ok. Chris ________________________________ Von: Justin Mclean <jus...@classsoftware.com> Gesendet: Dienstag, 6. September 2016 01:26:01 An: dev@flex.apache.org Betreff: Re: [DISCUSS] Discuss Release Apache Flex FalconJX 0.7.0 RC1 Hi, > It it possible to test the maven build with this release? Answering part of my own question - changing the pom file to have this, means it get a little further: <compiler-build-tools.version>1.0.0-SNAPSHOT</compiler-build-tools.version> <compiler-jburg-types.version>1.0.0-SNAPSHOT</compiler-jburg-types.version> But then complains about this: Failure to find com.adobe.flash.framework:playerglobal:swc:20.0 in https://repository.apache.org/content/repositories/releases Look at MAVEN_README.txt it says to do this: mvn -s settings-template.xml clean install -P utils However that generates the same error and a warning as well: [WARNING] The requested profile "utils" could not be activated because it does not exist. I assume the player global.swc needs to be put into the maven repo somehow. Any reason for version 20 btw and not a later one? Thanks, Justin
