This is my #1 annoyance with FB. I can't tell you how many times I've been editing a file and gotten confused because it didn't seem to be compiling (because it wasn't selected in the build path). Or editing one file and confused why it wasn't able to import another (again because the other wasn't in the build path).
UGH! I've gotten used to, as soon as I get a new update from the src repository, going directly into the project properties and updating the build path with everything. Bleh... --- In flexcoders@yahoogroups.com, "diehlryan" <[EMAIL PROTECTED]> wrote: > > Does anyone else find it annoying that you must explicitly specify the > classes that are included in your library project via the Flex Library > Build Path? This is especially annoying in a team environment when > someone else adds a new class, and I have to explicitly add it in > order to get a successful compilation. (I won't even go into the > issues I have with the compiler). > > If you look at how Eclipse handles this, you specify a source folder > and then can optionally specify anything that should be excluded from > compilation. This way, you can just say "my code is here" and it > picks up everything unless you tell it not to. > > Even if the compiler needs to know exactly which files to use, I think > a nice feature would be to automatically generate that > flexLibProperties file for you. >
