I fixed the “main” target of the BlazeDS Ant build. At least, I got it working for me. I haven’t turned it on in the CI server because I wasn’t sure if it would interfere with that Chris has running there now, which uses Maven.
The SDK’s build of the BlazeDS jar does assume that the BlazeDS Ant script ran successfully in the flex-blazeds repo. Should that be clarified in the README? From my point of view BlazeDS may also be in a releasable state unless there really are test issues that we think we should fix before releasing. We opted to have the SDK build the one jar it needed so that we wouldn’t have to go through a first BlazeDS release before releasing 4.14. Also, it makes it one less dependency to download. -Alex On 12/12/14, 4:50 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >Alex made it so that the SDK build no creates the one jar it needs >from BlazeDS, and uses that for it's own build. I guess he made an >assumption based on something that already happened on his system >(maybe the same partially successful 'ant' build that fixed it for >me). > >Can you also maybe look at the download issue I encountered on Windows >(the Mustella VM) while it was trying to download the 'flex-tool-api' >(see the other thread)? > >Thanks! > >EdB > > > >On Fri, Dec 12, 2014 at 1:37 PM, Christofer Dutz ><christofer.d...@c-ware.de> wrote: >> Seems like the air has cleared up for now ... so I come out of my hole >>again ;-) >> >> But serious ... The Ant Build doesn't seem to work. It needs some >>pre-configured legacy systems available for some tests to run and I >>remember not being able to build BlazeDS with Ant. Looking at the code >>the BlazeDS guys switched to Maven some time ago and didn't continue to >>maintain the Ant part. >> >> Some of the Tests needed a server to be setup. In order to be able to >>run them in our CI servers, I updated the tests to start a minimal >>BlazeDS server and run the tests against that. Now the testsuite is >>green most of the time. Only when the build agent is completely swamped >>with load, some timeouts might pop up, but this hasn't happened for >>quite some time. >> >> From my point of view BlazeDS is in a releaseable state, but I think >>there were still some things Alex wanted, but I have to admit that post >>must have been deleted by me together with about 99% of the other mails >>on this list ;-) Think it was some Jars not containing classes he was >>expecting or the jars being created in a directory he wasn't expecting. >> >> Chris >> >> ________________________________________ >> Von: Erik de Bruin <e...@ixsoftware.nl> >> Gesendet: Freitag, 12. Dezember 2014 12:10 >> An: dev@flex.apache.org >> Betreff: Re: BlazeDS not compiling for clean copy of SDK source >> >> Thanks, Chris. >> >> EdB >> >> P.S. Good to hear from you again! >> >> >> >> On Fri, Dec 12, 2014 at 11:58 AM, Christofer Dutz >> <christofer.d...@c-ware.de> wrote: >>> The ant build doesn't work ... try mvn clean install in the modules >>>directory :-) >>> >>> >>> Chris >>> >>> ________________________________________ >>> Von: Erik de Bruin <e...@ixsoftware.nl> >>> Gesendet: Freitag, 12. Dezember 2014 11:00 >>> An: dev@flex.apache.org >>> Betreff: BlazeDS not compiling for clean copy of SDK source >>> >>> Hi (Alex), >>> >>> I get the following error on a clean copy of the SDK, when I do an >>> 'ant release' ... But as soon as I did an 'ant' on 'flex-blazeds' and >>> then tried again, the problem went away ... >>> >>> prepare: >>> >>> [echo] >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/build.x >>>ml >>> >>> [mkdir] Created dir: >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/lib >>> >>> [mkdir] Created dir: >>> >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/classes >>> >>> >>> run-depend: >>> >>> [echo] Removing class files that changed and dependent class >>>files. >>> >>> >>> compile: >>> >>> [javac] >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/build.x >>>ml:54: >>> warning: 'includeantruntime' was not set, defaulting to >>> build.sysclasspath=last; set to false for repeatable builds >>> >>> [javac] Compiling 47 source files to >>> >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/classes >>> >>> [javac] warning: [options] bootstrap class path not set in >>> conjunction with -source 1.4 >>> >>> [javac] >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/src/fle >>>x/messaging/config/ApacheXPathClientConfigurationParser.java:19: >>> error: package org.apache.xpath does not exist >>> >>> [javac] import org.apache.xpath.CachedXPathAPI; >>> >>> [javac] ^ >>> >>> [javac] >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/src/fle >>>x/messaging/config/ApacheXPathClientConfigurationParser.java:37: >>> error: cannot find symbol >>> >>> [javac] private CachedXPathAPI xpath; >>> >>> [javac] ^ >>> >>> [javac] symbol: class CachedXPathAPI >>> >>> [javac] location: class ApacheXPathClientConfigurationParser >>> >>> [javac] >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/src/fle >>>x/messaging/config/ApacheXPathClientConfigurationParser.java:41: >>> error: cannot find symbol >>> >>> [javac] this.xpath = new CachedXPathAPI(); >>> >>> [javac] ^ >>> >>> [javac] symbol: class CachedXPathAPI >>> >>> [javac] location: class ApacheXPathClientConfigurationParser >>> >>> [javac] 3 errors >>> >>> [javac] 1 warning >>> >>> >>> BUILD FAILED >>> >>> >>>/Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/build.xml:41 >>>1: >>> The following error occurred while executing this line: >>> >>> >>>/Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/modules/buil >>>d.xml:157: >>> The following error occurred while executing this line: >>> >>> >>>/Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/modules/flex >>>-messaging-common/build.xml:86: >>> The following error occurred while executing this line: >>> >>> /Users/erik/Documents/ApacheFlex/git/flex-blazeds/build.xml:159: The >>> following error occurred while executing this line: >>> >>> >>>/Users/erik/Documents/ApacheFlex/git/flex-blazeds/modules/common/build.x >>>ml:54: >>> Compile failed; see the compiler error output for details. >>> >>> Thanks, >>> >>> EdB >>> >>> >>> >>> -- >>> Ix Multimedia Software >>> >>> Jan Luykenstraat 27 >>> 3521 VB Utrecht >>> >>> T. 06-51952295 >>> I. www.ixsoftware.nl >> >> >> >> -- >> Ix Multimedia Software >> >> Jan Luykenstraat 27 >> 3521 VB Utrecht >> >> T. 06-51952295 >> I. www.ixsoftware.nl > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
