Christian, Although I was answering Richard, thanks for the note on the downside to using -include-sources. It'll be good to know the next time I need to include non-class resources such as .css files and images! :)
-Jun --- In [email protected], Christian Edward Gruber <[EMAIL PROTECTED]> wrote: > > That's actually why I built the maven plugin the way I did. While > classes can be handled this way, non-class resources (such as .css > files or images) can't. You have to explicitly call them out for > compc. I essentially search the source path for .as files and the > resource path for all other files, and include them all behind the > scenes. That one would have to specify explicit resources on the > command-line (or as a separate param) is just ludicrous. > > But at least the below should work for pure .as class files. > > Christian. > > On 15-Oct-07, at 7:59 PM, realeyes_jun wrote: > > > Richard, > > > > So far the suggestions have been made to use: > > > > - Flex Ant tasks > > - flex2ant plugin > > - antennae > > > > Although I'm sure each of the above solutions work well, I ran across > > this issue myself recently and solved the issue you're asking about by > > providing the -include-sources option to compc in my custom ant > > script. > > > > This option allowed me to select the parent directory of all the > > classes > > I wanted to include, and it was recursive. Example: > > > > -include-sources="com/realeyesmedia/debug/redbug" > > > > This path of course was relative to the project dir. > > > > -Jun > > > > > > --- In [email protected], "Richard Rodseth" rrodseth@ > > wrote: > >> > >> A colleague is setting up Ant builds for our project, and hasn't > >> found > >> a (good) way to build a SWC without having to specify every class to > >> include in the SWC. Any pointers to resources would be much > >> appreciated. > >> > > > > >
