Ok … so I was to bold to just create the missing branch for the typedefs repo … now the autobuild worked … well let’s say it started doing its job.
I changed the configuration for the auto-build jog to automatically build release branches too (even if I would like to suggest a more “release/0.8.0” like notation in the future). Unfortunately, this also demonstrates the failures I was getting locally. I guess no one really tested the release branch with maven yet, which makes me sad :-( Currently I have no idea what was changed during ApacheCon and in the time, I needed to get rid of the usual post-conference pile of work. This time I don’t really feel encouraged to fix it. Feels a little like being Don Quixote tilting at windmills. At least now you have a Jenkins job taking care of the automatic building so you’ll see if you’re getting there. This is exactly the sort of Double build problems I was talking about in the discussion round at the FlexJS Summit :-( https://builds.apache.org/view/E-G/view/Flex/job/FlexJS%20Pipeline/job/release0.8.0/ I’ll now commit my changes on the archetypes and the font-stuff as they didn’t add any additional errors. So, I wouldn’t recommend cutting a RC right now, because if the Maven build isn’t back to normal, I won’t +1 on it. Chris Am 24.05.17, 13:20 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>: Would it be ok to cut a release branch with the same name for the typedefs? Right now the Jenkinsfile which handles the auto-build-branch stuff requires all three repos to have matching branches. Chris Am 24.05.17, 12:59 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>: I just merged my changes to release and currently can’t build the examples due to this error: [INFO] --- flexjs-maven-plugin:0.8.0-SNAPSHOT:compile-app (default-compile-app) @ DataBindingExample-Express --- [INFO] Executing MXMLC in tool group FlexJS with args: [-load-config=/Users/christoferdutz/Projects/Apache/Flex/FlexJS/flexjs-framework/examples/express/DataBindingExample/target/compile-app-config.xml, -js-output=/Users/christoferdutz/Projects/Apache/Flex/FlexJS/flexjs-framework/examples/express/DataBindingExample/target/javascript, -compiler.targets=SWF,JSFlex, /Users/christoferdutz/Projects/Apache/Flex/FlexJS/flexjs-framework/examples/express/DataBindingExample/src/main/flex/DataBindingExample.mxml] Loading configuration: /Users/christoferdutz/Projects/Apache/Flex/FlexJS/flexjs-framework/examples/express/DataBindingExample/target/compile-app-config.xml /Users/christoferdutz/Projects/Apache/Flex/FlexJS/flexjs-framework/examples/express/DataBindingExample/src/main/flex/DataBindingExample.mxml(20): col: 1 Error: This tag could not be resolved to an ActionScript class. It will be ignored. <js:Application xmlns:fx="http://ns.adobe.com/mxml/2009"; ^ Anything changed here? Chris Am 24.05.17, 10:50 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>: It shouldn’t have anything to do with that, because my fixes just fine-tuned things there. Chris Am 24.05.17, 10:41 schrieb "Justin Mclean" <jus...@classsoftware.com>: Hi, I’m unable to compile the FlexJS nightly release using maven. A “mvn -X clean compile” gives: [ERROR] The build could not read 1 project -> [Help 1] org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [ERROR] Child module /Users/justinmclean/Downloads/FlexJSCheck/apache-flex-flexjs-0.8.0-src/archetypes of /Users/justinmclean/Downloads/FlexJSCheck/apache-flex-flexjs-0.8.0-src/pom.xml does not exist @ Is that because Chris fixes from the other day are not in the release branch yet? Thanks, Justin
