Hi, I know ... I saw the failure and was waiting for some time, if there were fixes comming in, but I didn’t notice any tries to fix the buid, so I fixed it. I thought it wasn’t noticed, because I always immediately fix a broken build, as soon as I notice something going wrong.
Well Ant could read the poms when using Ivy and a Maven dependency manager ... but that would require a complete re-write of the Ant build. Maven generates it’s own config-xmls on the fly from the config in the pom. So the config files are a Ant only thing. Chris Am 16.11.16, 13:26 schrieb "Yishay Weiss" <[email protected]>: Hi Chris, That would have been me. I was aware the jobs were failing, you just beat me to it. Thanks for fixing it. Is there a way to have both builds read the same file for determining package dependencies? I thought that was what compile-as-config.xml and compile-js-config.xml were doing… From: Christofer Dutz<mailto:[email protected]> Sent: Wednesday, November 16, 2016 2:02 PM To: [email protected]<mailto:[email protected]> Subject: Keeping in mind that there's a Maven build ... Hi guys, I just fixed a build problem that was causing the Maven builds to fail. It was related to some changes for which the Ant build was corrected, but not the Maven build. It is ok if you don’t know how to do things in Maven, please ask for help and do changes like this on a dedicated branch. Breking develop without notifying anyone that you need help isn’t that good. So as soon as you start changing the Ant build, the chances are high, that Maven needs to be updated too. So please at least have a look if the jobs are working and call for help if something is wrong. You should get feedback here within a few minutes. And especially please keep in Mind that builds.apache.org is the reference build system, not apacheflexbuild.cloudapp.net Chris
