No worries Carol.
I'm curious to know how you will fix this though. I prefer having as little
properties as possible so IMO the PLAYERGLOBAL_HOME property + the fixed
playerglobal.swc name seems like the best option.
What's your take on this?
regards,
Christophe
2012/5/8 Carol Frampton <cfram...@adobe.com>
> You are correct. I blew it. Sorry about that. Will work on fixing that
> right now.
>
> Caorl
>
> On 5/8/12 8 :59AM, "Christophe Herreman" <christophe.herre...@gmail.com>
> wrote:
>
> >Hi,
> >
> >with the renaming of PLAYERGLOBAL_HOME to PLAYERGLOBAL, there are various
> >places in the project build files where PLAYERGLOBAL is used as a
> >directory. Some examples are framework, mx, rpc, charts, ...
> >
> >Usages with issues:
> >
> >a) <echo message="Using ${env.PLAYERGLOBAL}/playerglobal.swc"
> >level="info"/>
> >
> >b) <compc...>
> > ...
> > <external-library-path dir="${env.PLAYERGLOBAL}">
> > <include name="playerglobal.swc"/>
> > </external-library-path>
> > ...
> > </compc>
> >
> >
> >Some possible fixes:
> >
> >- use PLAYERGLOBAL in "external-library-path" without specifying the
> >library name. (I have not looked at the sources of the compc task to know
> >if this is possible.)
> >- re-introduce PLAYERGLOBAL_HOME, perhaps ommitting PLAYERGLOBAL if it can
> >be assumed that the file will always be called playerglobal.swc (as stated
> >in README)
> >- split PLAYERGLOBAL in the Ant build script and extract the directory and
> >the filename from it
> >
> >
> >regards,
> >Christophe
> >
> >--
> >Christophe Herreman
> >http://www.herrodius.com
> >http://www.springactionscript.org
> >http://www.as3commons.org
>
>
--
Christophe Herreman
http://www.herrodius.com
http://www.springactionscript.org
http://www.as3commons.org
