Only the apache classes need to end up in the apache swc
Sure and that's what happen even if we create a new manifest file for the
external classes and declare the relative namespace until we mention only
the apache namespace in include-namespaces directive.
if you look at the catalog file of the apache.swc; you'll see there's
nothing relative to the exposed classes, that's because they are not
included because the namespace wasn't included via include-namespaces.
I thought the external-library-path took care of the external classes too
it doesn't.
- Fred.
-----Message d'origine-----
From: Justin Mclean
Sent: Sunday, December 16, 2012 7:39 AM
To: flex-dev@incubator.apache.org
Subject: Re: [jira] [Created] (FLEX-33298) The apache lib compile without
including anything
HI,
All the exposed classes, yes, but not the classes used in this lib but
comming from other libs and that's apparently needed to compile
successfully.
"ant apache" compiles without error, so I'm sure sure what you mean by
"sucessfully"? I would assume that the external-library-path in the config
file takes care of the classes needed from other parts of the SDK. Only the
apache classes need to end up in the apache swc.
Thanks,
Justin
