It looks like the quotes fooled some code into thinking it was a relative path. Hopefully the next build will pass or at least get past this point.
-Alex On 9/29/15, 2:46 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Ok ... so I managed to get even more "blue balls" on builds.apache.org >... unfortunately I'm currently stuck with Falcon ... the problem should >be trivial, but it seems that the path to the Flash Debugger is totally >screwed up ... it's always set to the workspace + the path on drive C, >but I didn't quite understand how the ant script creates this ... could >you please have a look ... it should be easy to fix this: > >https://builds.apache.org/view/E-G/view/Flex/job/flex-falcon/ > >Chris > >________________________________________ >Von: Christofer Dutz <christofer.d...@c-ware.de> >Gesendet: Dienstag, 29. September 2015 18:24 >An: dev@flex.apache.org >Betreff: AW: AW: Jenkins builds > >Have to admit that it was probably me being lost in the target names ... >there seem to be 1000 targets that sort of sound like they are the one >you want, but actually you have to use the right one. I had a nother look >and took another target and it actually worked ... doing the >"binary-release" thing seems to have been a bad idea ;-) > >But in the end I did manage to get the build working by resolving some of >the cyclic dependencies (No need for BLAZEDS_HOME as this is loaded from >Maven Central). Did another few changes to the build files and comitted >them in a separate branch. The build now no longer downloads a Flex SDK >for the fontkit libraries and instead the libs are loaded directly. This >sort of matches to the agreement the user had to accept ... as he never >agreed to download the Adobe Flex SDK. > >With these changes I was able to get a lot of jobs Blue again ... please >have a look at my changes ... I'll merge them back to develop as soon as >I'm back from Budapest. > >Chris > >________________________________________ >Von: Alex Harui <aha...@adobe.com> >Gesendet: Dienstag, 29. September 2015 16:57 >An: dev@flex.apache.org >Betreff: Re: AW: Jenkins builds > >On 9/29/15, 4:16 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > >>While I'm trying to get the builds running on the ASF Jenkins, I noticed >>something strange: >>In order to run the tests in framework/tests/basicTests, I need the >>mustella.swc ... unfortunately this is build after the basicTests are >>run. It seems that the only purpose of this is to have the test end and >>report the results back. If I comment out this dependency, the build >>proceeds, but I have to manually kill the flash player. >> >>After that the build continues and the mustella.swc is created and I can >>comment in the last three lines of BasicTests-config.xml >> >>This seems rather strange ... > >I don’t see this in the build.xml. Checkintests runs basictests-mustella >which depends on mustella-setup so mustella-setup will run before the >steps in basictests-mustella and mustella-setup is where the mustella.swc >is created. > >-Alex
