This is the one:
http://livedocs.adobe.com/flex/3/html/help.html?content=l10n_3.html#158343
-allow-source-path-overlap=true
--- In flexcoders@yahoogroups.com, "bnsmeets" <[EMAIL PROTECTED]> wrote:
>
> Try finding the allow-source-overlap parameter for the compiler (don't
> know the exact name from where i am now). That will allow you to put
> locale in src.
>
> Ben
>
> --- In flexcoders@yahoogroups.com, "Richard Rodseth" <rrodseth@> wrote:
> >
> > Yes, I have suggested we consider using Ant, but I'm working with a
> > .NET team with established practices and expertise.
> >
> > I'm not sure I understand your response. Do you place your locales and
> > assets inside src, or as a sibling? Also, we are building libraries
> > (swc) and applications (swf). The particular case I was referring to
> > involved a library project with locale and src folders. My build guy
> > was struggling with compc, if the locale was a sibling of src.
> >
> > Thanks.
> >
> > On Sat, Apr 19, 2008 at 1:51 AM, cisnky <cisnky@> wrote:
> >
> > >
> > > I've always had the source code related to the project in the src
> folder.
> > > Then linked to any library source I may need on my project.
> > >
> > > We use Ant and just add the source path to the mxmlc compile task.
> > >
> > > Is there any reason why you can't get CruiseControl to launch Ant
> build
> > > files for the Flex part of your project. It can be done and works
> from a
> > > Windows and Unix box.
> > >
> > >
> > > "I get a warning from FlexBuilder that a source path is inside
another
> > > source path".
> > >
> > > I've had that warning before. If you ignore, your project ends up
> getting
> > > confused.
> > >
> > >
> > >
> > >
> > > On Fri, Apr 18, 2008 at 10:37 PM, Richard Rodseth <rrodseth@>
> > > wrote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Are there any definitive examples of best practices for project
> layout
> > > > of libraries and applications, that works well with
Flexbuilder, as
> > > > well as compc/mxmlc (example command-line arguments would help
too).
> > > >
> > > > My latest struggle is with locales. I followed an Adobe
example, and
> > > > placed locales alongside src, and added
> > > >
> > > > -locale en_US -source-path=../locale/{locale}
> > > >
> > > > to the additional compiler options in FlexBuilder.
> > > >
> > > > My colleague (who is working on the CruiseControl builds, and
is new
> > > > to Flex) requested that the locales folder be inside the src
folder,
> > > > and I know that I have had problems in the past with assets
outside
> > > > the src folder.
> > > >
> > > > So I complied, and changed the options to:
> > > >
> > > > -locale en_US -source-path=locale/{locale}
> > > >
> > > > However, doing it this way, I get a warning from FlexBuilder
that a
> > > > source path is inside another source path. Removing the compiler
> > > > option and checking the checkboxes in the Assets tab didn't work.
> > > >
> > > > Unfortunately, Ant or Maven are not options, as we are
> integrating with
> > > MSBuild.
> > > >
> > >
> > >
> >
>
