----- Original Message -----
From: "David Fischer" <[EMAIL PROTECTED]>
To: "Open Source Flash Mailing List" <[email protected]>
Sent: Friday, July 08, 2005 12:17 AM
Subject: Re: [osflash] ASDT-Project - Best practices
i noticed that too as i mentioned in my first post.
but simply adding a new linked resource (like 'myCommonClasses') also
doesnt work for me.
of course we could place all com/net/org in the core classes
but thats not what i/we want :)
we could only pass additional params to mtasc like multiple -cp's and
achieve a solution that way, which is kinda easier ihmo for this task.
or am i totally missing the point ;) ?
Yes but I do that anyway in the build.xml. The one reason why I would like
to have the 'third party' class folder linked with a classpath variable in
the project properties is that these classes can then be opened by
F3-keypress when the type is highlighted in another class which is quite
comfortable.
I have checked the Eclipse docs but didn't found any helpful info on that
topic and trying to sneak behind Eclipse and add a classpath variable to the
projects .classpath file manually doesn't work either.
Maybe someone of the 'Eclipse-Gurus' can enlighten us?
-sascha
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
