You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Erik de Bruin <er...@ixsoftware.nl> on 2014/12/12 11:00:01 UTC
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.xml
[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.xml: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/flex/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/flex/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/flex/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:411:
The following error occurred while executing this line:
/Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/modules/build.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.xml: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
Re: BlazeDS not compiling for clean copy of SDK source
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Sound like a plan. Release first, then 'rebuild'. Getting back to
basics is always a good thing, clear out the crud that inevitably
built up over the years at the previous owner, and start 'fresh'.
EdB
On Sun, Dec 14, 2014 at 1:16 PM, Christofer Dutz
<ch...@c-ware.de> wrote:
> How about re-organizing the code of the project? (But I would opt to do that after a release)
> Currently it seems as if the actual project is embedded in a wrapper of the old build (which I didn't get to work)
> I would like to move the "modules" content out to become the root, and to move all the old stuff to some "attic" directory I don't want to delete it, just want to park it so if users come with special needs, we can check what we have to do to revive parts of the attic code.
>
> Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Sonntag, 14. Dezember 2014 08:15
> An: dev@flex.apache.org
> Betreff: Re: BlazeDS not compiling for clean copy of SDK source
>
>
>
> On 12/13/14, 1:45 PM, "Gordon Smith" <gs...@hotmail.com> wrote:
>
>>> 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 ...
>>> [javac]
>>>/Users/erik/Documents/ApacheFlex/git/flexblazeds/modules/common/src/fl
>>>ex/
>>>messaging/config/ApacheXPathClientConfigurationParser.java:19:
>>> error: package org.apache.xpath does not exist
>>
>>I had the same problem.
>>
>>I don't think it should be a requirement to manually build flex-blazeds
>>before building flex-sdk. If the SDK needs something in BlazeDS,
>>BlazeDS should have an ant target that automatically builds that thing
>>without error, and the ant script for flex-sdk should call that target.
>>The README should explain that you must have source for both repos and
>>that you have asset BLAZEDS_HOME to point to flex-blazeds in addition
>>to setting FLEX_HOME to point to flex-sdk. (Bummer that this isn't
>>called SDK_HOME, or that both aren't FLEX_SDK_HOME and
>>FLEX_BLAZEDS_HOME.)
>>
>>The way that the build.xml for flex-sdk finds the flex-blazeds repo
>>looks inconsistent. I see references to ${BLAZEDS_HOME}, but I don't
>>have this set and the script didn't seem to complain. I also see
>>references to ${FLEX_HOME}/../flex-blazeds and to
>>${FLEX_HOME}/../blazeds. All references should go through BLAZEDS_HOME
>>and an early check should fail if this isn't set.
>
> We can make changes, but IMO, flex-falcon relies on flex-sdk being built first, so I thought that was fair precedence. For both the BlazeDS and TLF dependencies, the flex-sdk script checks to see if you have the repos in a few expected places so you don’t have to set up environment variables. We’ve been doing this for TLF for some time now.
>
>>
>>Is the dependency on BlazeDS something that got added recently? What
>>does the SDK need from BlazeDS?
>
> Yes, the BlazeDS dependency was added a few days ago. Before then, the SDK downloaded flex-messaging-common.jar from Adobe BlazeDS. We have now reduced our Adobe proprietary dependencies to just the optional fontswf jars. OSMF is under MPL, and AIR and Flash are considered build tools.
> The flex-messaging-common.jar is only needed when specifying a services-config in the MXMLC command line. No idea if this is supported in Falcon. FlexJS currently doesn’t leverage it.
>
> -Alex
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
AW: BlazeDS not compiling for clean copy of SDK source
Posted by Christofer Dutz <ch...@c-ware.de>.
How about re-organizing the code of the project? (But I would opt to do that after a release)
Currently it seems as if the actual project is embedded in a wrapper of the old build (which I didn't get to work)
I would like to move the "modules" content out to become the root, and to move all the old stuff to some "attic" directory I don't want to delete it, just want to park it so if users come with special needs, we can check what we have to do to revive parts of the attic code.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Sonntag, 14. Dezember 2014 08:15
An: dev@flex.apache.org
Betreff: Re: BlazeDS not compiling for clean copy of SDK source
On 12/13/14, 1:45 PM, "Gordon Smith" <gs...@hotmail.com> wrote:
>> 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 ...
>> [javac]
>>/Users/erik/Documents/ApacheFlex/git/flexblazeds/modules/common/src/fl
>>ex/
>>messaging/config/ApacheXPathClientConfigurationParser.java:19:
>> error: package org.apache.xpath does not exist
>
>I had the same problem.
>
>I don't think it should be a requirement to manually build flex-blazeds
>before building flex-sdk. If the SDK needs something in BlazeDS,
>BlazeDS should have an ant target that automatically builds that thing
>without error, and the ant script for flex-sdk should call that target.
>The README should explain that you must have source for both repos and
>that you have asset BLAZEDS_HOME to point to flex-blazeds in addition
>to setting FLEX_HOME to point to flex-sdk. (Bummer that this isn't
>called SDK_HOME, or that both aren't FLEX_SDK_HOME and
>FLEX_BLAZEDS_HOME.)
>
>The way that the build.xml for flex-sdk finds the flex-blazeds repo
>looks inconsistent. I see references to ${BLAZEDS_HOME}, but I don't
>have this set and the script didn't seem to complain. I also see
>references to ${FLEX_HOME}/../flex-blazeds and to
>${FLEX_HOME}/../blazeds. All references should go through BLAZEDS_HOME
>and an early check should fail if this isn't set.
We can make changes, but IMO, flex-falcon relies on flex-sdk being built first, so I thought that was fair precedence. For both the BlazeDS and TLF dependencies, the flex-sdk script checks to see if you have the repos in a few expected places so you don’t have to set up environment variables. We’ve been doing this for TLF for some time now.
>
>Is the dependency on BlazeDS something that got added recently? What
>does the SDK need from BlazeDS?
Yes, the BlazeDS dependency was added a few days ago. Before then, the SDK downloaded flex-messaging-common.jar from Adobe BlazeDS. We have now reduced our Adobe proprietary dependencies to just the optional fontswf jars. OSMF is under MPL, and AIR and Flash are considered build tools.
The flex-messaging-common.jar is only needed when specifying a services-config in the MXMLC command line. No idea if this is supported in Falcon. FlexJS currently doesn’t leverage it.
-Alex
Re: BlazeDS not compiling for clean copy of SDK source
Posted by Alex Harui <ah...@adobe.com>.
On 12/16/14, 2:07 PM, "Gordon Smith" <gs...@hotmail.com> wrote:
>> [Alex:] flex-falcon relies on flex-sdk being built first, so I thought
>>that was fair precedence
>
>OK, that's fair. But if I make flex-falcon build what it needs in
>flex-sdk, would you be willing to make flex-sdk build what it needs in
>flex-blazeds?
IMO, it doesn’t have to be consistent. It is fine to adjust the flex-sdk
build so you don’t have to build flex-blazeds first. Flex-falcon doesn’t
have to be fixed first. FWIW, the flex-sdk build of that jar might just
need an adjusted library-path. I think the jars it needs are already
downloaded into the flex-sdk/lib/external.
-Alex
RE: BlazeDS not compiling for clean copy of SDK source
Posted by Gordon Smith <gs...@hotmail.com>.
> [Alex:] flex-falcon relies on flex-sdk being built first, so I thought that was fair precedence
OK, that's fair. But if I make flex-falcon build what it needs in flex-sdk, would you be willing to make flex-sdk build what it needs in flex-blazeds?
- Gordon
> From: aharui@adobe.com
> To: dev@flex.apache.org
> Subject: Re: BlazeDS not compiling for clean copy of SDK source
> Date: Sun, 14 Dec 2014 07:14:30 +0000
>
>
>
> On 12/13/14, 1:45 PM, "Gordon Smith" <gs...@hotmail.com> wrote:
>
> >> 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 ...
> >> [javac]
> >>/Users/erik/Documents/ApacheFlex/git/flexblazeds/modules/common/src/flex/
> >>messaging/config/ApacheXPathClientConfigurationParser.java:19:
> >> error: package org.apache.xpath does not exist
> >
> >I had the same problem.
> >
> >I don't think it should be a requirement to manually build flex-blazeds
> >before building flex-sdk. If the SDK needs something in BlazeDS, BlazeDS
> >should have an ant target that automatically builds that thing without
> >error, and the ant script for flex-sdk should call that target. The
> >README should explain that you must have source for both repos and that
> >you have asset BLAZEDS_HOME to point to flex-blazeds in addition to
> >setting FLEX_HOME to point to flex-sdk. (Bummer that this isn't called
> >SDK_HOME, or that both aren't FLEX_SDK_HOME and FLEX_BLAZEDS_HOME.)
> >
> >The way that the build.xml for flex-sdk finds the flex-blazeds repo looks
> >inconsistent. I see references to ${BLAZEDS_HOME}, but I don't have this
> >set and the script didn't seem to complain. I also see references to
> >${FLEX_HOME}/../flex-blazeds and to ${FLEX_HOME}/../blazeds. All
> >references should go through BLAZEDS_HOME and an early check should fail
> >if this isn't set.
>
> We can make changes, but IMO, flex-falcon relies on flex-sdk being built
> first, so I thought that was fair precedence. For both the BlazeDS and
> TLF dependencies, the flex-sdk script checks to see if you have the repos
> in a few expected places so you don’t have to set up environment
> variables. We’ve been doing this for TLF for some time now.
>
> >
> >Is the dependency on BlazeDS something that got added recently? What does
> >the SDK need from BlazeDS?
>
> Yes, the BlazeDS dependency was added a few days ago. Before then, the
> SDK downloaded flex-messaging-common.jar from Adobe BlazeDS. We have now
> reduced our Adobe proprietary dependencies to just the optional fontswf
> jars. OSMF is under MPL, and AIR and Flash are considered build tools.
> The flex-messaging-common.jar is only needed when specifying a
> services-config in the MXMLC command line. No idea if this is supported
> in Falcon. FlexJS currently doesn’t leverage it.
>
> -Alex
>
Re: BlazeDS not compiling for clean copy of SDK source
Posted by Alex Harui <ah...@adobe.com>.
On 12/13/14, 1:45 PM, "Gordon Smith" <gs...@hotmail.com> wrote:
>> 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 ...
>> [javac]
>>/Users/erik/Documents/ApacheFlex/git/flexblazeds/modules/common/src/flex/
>>messaging/config/ApacheXPathClientConfigurationParser.java:19:
>> error: package org.apache.xpath does not exist
>
>I had the same problem.
>
>I don't think it should be a requirement to manually build flex-blazeds
>before building flex-sdk. If the SDK needs something in BlazeDS, BlazeDS
>should have an ant target that automatically builds that thing without
>error, and the ant script for flex-sdk should call that target. The
>README should explain that you must have source for both repos and that
>you have asset BLAZEDS_HOME to point to flex-blazeds in addition to
>setting FLEX_HOME to point to flex-sdk. (Bummer that this isn't called
>SDK_HOME, or that both aren't FLEX_SDK_HOME and FLEX_BLAZEDS_HOME.)
>
>The way that the build.xml for flex-sdk finds the flex-blazeds repo looks
>inconsistent. I see references to ${BLAZEDS_HOME}, but I don't have this
>set and the script didn't seem to complain. I also see references to
>${FLEX_HOME}/../flex-blazeds and to ${FLEX_HOME}/../blazeds. All
>references should go through BLAZEDS_HOME and an early check should fail
>if this isn't set.
We can make changes, but IMO, flex-falcon relies on flex-sdk being built
first, so I thought that was fair precedence. For both the BlazeDS and
TLF dependencies, the flex-sdk script checks to see if you have the repos
in a few expected places so you don’t have to set up environment
variables. We’ve been doing this for TLF for some time now.
>
>Is the dependency on BlazeDS something that got added recently? What does
>the SDK need from BlazeDS?
Yes, the BlazeDS dependency was added a few days ago. Before then, the
SDK downloaded flex-messaging-common.jar from Adobe BlazeDS. We have now
reduced our Adobe proprietary dependencies to just the optional fontswf
jars. OSMF is under MPL, and AIR and Flash are considered build tools.
The flex-messaging-common.jar is only needed when specifying a
services-config in the MXMLC command line. No idea if this is supported
in Falcon. FlexJS currently doesn’t leverage it.
-Alex
RE: BlazeDS not compiling for clean copy of SDK source
Posted by Gordon Smith <gs...@hotmail.com>.
> 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 ...
> [javac] /Users/erik/Documents/ApacheFlex/git/flexblazeds/modules/common/src/flex/messaging/config/ApacheXPathClientConfigurationParser.java:19:
> error: package org.apache.xpath does not exist
I had the same problem.
I don't think it should be a requirement to manually build flex-blazeds before building flex-sdk. If the SDK needs something in BlazeDS, BlazeDS should have an ant target that automatically builds that thing without error, and the ant script for flex-sdk should call that target. The README should explain that you must have source for both repos and that you have asset BLAZEDS_HOME to point to flex-blazeds in addition to setting FLEX_HOME to point to flex-sdk. (Bummer that this isn't called SDK_HOME, or that both aren't FLEX_SDK_HOME and FLEX_BLAZEDS_HOME.)
The way that the build.xml for flex-sdk finds the flex-blazeds repo looks inconsistent. I see references to ${BLAZEDS_HOME}, but I don't have this set and the script didn't seem to complain. I also see references to ${FLEX_HOME}/../flex-blazeds and to ${FLEX_HOME}/../blazeds. All references should go through BLAZEDS_HOME and an early check should fail if this isn't set.
Is the dependency on BlazeDS something that got added recently? What does the SDK need from BlazeDS?
- Gordon
Re: BlazeDS not compiling for clean copy of SDK source
Posted by Erik de Bruin <er...@ixsoftware.nl>.
+1 for Maven on BlazeDS. It is not something a lot of our users will be
directly using, and it will be a nice opportunity for us to get some
experience with an alternative build tool.
I would hope to see some documentation on the 'new' process on the Wiki, or
at least plenty comments in the build file.
Thanks,
EdB
On Saturday, December 13, 2014, Christofer Dutz <ch...@c-ware.de>
wrote:
> So if you guys haven't got any objections, I would try starting the
> release process.
> But I would initiate the Maven release and not use the Ant stuff.
>
> I invested several days of fixing the testsuite a few months ago and I
> managed to get all unit tests green. Also I switched all of my applications
> to Apache BlazeDS for a test and didn't encounter any problems with it ...
> was a real drop-in replacement.
>
> Chris
>
> ________________________________________
> Von: Alex Harui <aharui@adobe.com <javascript:;>>
> Gesendet: Freitag, 12. Dezember 2014 18:23
> An: dev@flex.apache.org <javascript:;>
> Betreff: Re: BlazeDS not compiling for clean copy of SDK source
>
> 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" <erik@ixsoftware.nl <javascript:;>>
> 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.dutz@c-ware.de <javascript:;>> 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 <erik@ixsoftware.nl <javascript:;>>
> >> Gesendet: Freitag, 12. Dezember 2014 12:10
> >> An: dev@flex.apache.org <javascript:;>
> >> 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.dutz@c-ware.de <javascript:;>> wrote:
> >>> The ant build doesn't work ... try mvn clean install in the modules
> >>>directory :-)
> >>>
> >>>
> >>> Chris
> >>>
> >>> ________________________________________
> >>> Von: Erik de Bruin <erik@ixsoftware.nl <javascript:;>>
> >>> Gesendet: Freitag, 12. Dezember 2014 11:00
> >>> An: dev@flex.apache.org <javascript:;>
> >>> 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
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
AW: BlazeDS not compiling for clean copy of SDK source
Posted by Christofer Dutz <ch...@c-ware.de>.
So if you guys haven't got any objections, I would try starting the release process.
But I would initiate the Maven release and not use the Ant stuff.
I invested several days of fixing the testsuite a few months ago and I managed to get all unit tests green. Also I switched all of my applications to Apache BlazeDS for a test and didn't encounter any problems with it ... was a real drop-in replacement.
Chris
________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Freitag, 12. Dezember 2014 18:23
An: dev@flex.apache.org
Betreff: Re: BlazeDS not compiling for clean copy of SDK source
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" <er...@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
><ch...@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 <er...@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
>> <ch...@c-ware.de> wrote:
>>> The ant build doesn't work ... try mvn clean install in the modules
>>>directory :-)
>>>
>>>
>>> Chris
>>>
>>> ________________________________________
>>> Von: Erik de Bruin <er...@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
Re: BlazeDS not compiling for clean copy of SDK source
Posted by Alex Harui <ah...@adobe.com>.
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" <er...@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
><ch...@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 <er...@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
>> <ch...@c-ware.de> wrote:
>>> The ant build doesn't work ... try mvn clean install in the modules
>>>directory :-)
>>>
>>>
>>> Chris
>>>
>>> ________________________________________
>>> Von: Erik de Bruin <er...@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
Re: BlazeDS not compiling for clean copy of SDK source
Posted by Erik de Bruin <er...@ixsoftware.nl>.
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
<ch...@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 <er...@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
> <ch...@c-ware.de> wrote:
>> The ant build doesn't work ... try mvn clean install in the modules directory :-)
>>
>>
>> Chris
>>
>> ________________________________________
>> Von: Erik de Bruin <er...@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.xml
>>
>> [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.xml: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/flex/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/flex/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/flex/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:411:
>> The following error occurred while executing this line:
>>
>> /Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/modules/build.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.xml: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
AW: BlazeDS not compiling for clean copy of SDK source
Posted by Christofer Dutz <ch...@c-ware.de>.
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 <er...@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
<ch...@c-ware.de> wrote:
> The ant build doesn't work ... try mvn clean install in the modules directory :-)
>
>
> Chris
>
> ________________________________________
> Von: Erik de Bruin <er...@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.xml
>
> [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.xml: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/flex/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/flex/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/flex/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:411:
> The following error occurred while executing this line:
>
> /Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/modules/build.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.xml: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
Re: BlazeDS not compiling for clean copy of SDK source
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Thanks, Chris.
EdB
P.S. Good to hear from you again!
On Fri, Dec 12, 2014 at 11:58 AM, Christofer Dutz
<ch...@c-ware.de> wrote:
> The ant build doesn't work ... try mvn clean install in the modules directory :-)
>
>
> Chris
>
> ________________________________________
> Von: Erik de Bruin <er...@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.xml
>
> [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.xml: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/flex/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/flex/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/flex/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:411:
> The following error occurred while executing this line:
>
> /Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/modules/build.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.xml: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
AW: BlazeDS not compiling for clean copy of SDK source
Posted by Christofer Dutz <ch...@c-ware.de>.
The ant build doesn't work ... try mvn clean install in the modules directory :-)
Chris
________________________________________
Von: Erik de Bruin <er...@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.xml
[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.xml: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/flex/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/flex/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/flex/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:411:
The following error occurred while executing this line:
/Users/erik/Documents/ApacheFlex/git/flex-sdk_release4.14.0/modules/build.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.xml: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