I have a similar setup and I have only noticed a few odd effects from
time to time.  When I update my Library A the build seems to take a
very long time. I think this is because then Library B needs to be
updated as well as the Main project.  If I update Library B it does
not take as long to build. I've been trying to figure out a better way
to handle libraries but have not.  And now to make it all worse I've
gotten to the point where my Library A has a reference to a class in
Library B... which does not work at all.  But I can fix that,
essentially someone just put a class in the wrong package.

--- In [email protected], "Brian Holmes" <[EMAIL PROTECTED]>
wrote:
>
> Are there any issues when referencing multiple Flex Library Projects? 
> 
>  
> 
> Say I have two libraries, Library A and Library B and one flex project. 
> 
>  -- Library B references Library A.
> 
>  -- Flex project references both Library A and Library B in the Build
> Path > Library Path.
> 
>  
> 
> Does this kind of referencing cause side effects? Or can I reference
> libraries in libraries in libraries?
> 
>  
> 
> Also, If I have two Flex Library Projects can they both use the same
> namespace url and then be used in the same in the same project?
> 
>  
> 
>  --Library B and Library A both have a namespace of
> http://my.domain.com/ 
> 
>  --Flex project then references both libraries.
> 
>    
> 
> I want to do this because we do have a rather large domain model. The
> libraries actually implement different sections of the domain. For
> example Library A would have classes such as com.domain.ap and Library B
> would have classes such as com.domain.cr or whatever. And then when
> they're used they can all be referenced with the same domain? Does that
> make sense? 
> 
>  
> 
> Thanks,
> 
> Brian..
> 
>  
> 
> 
> 
> ***
> The information in this e-mail is confidential and intended solely
for the individual or entity to whom it is addressed.  If you have
received this e-mail in error please notify the sender by return
e-mail delete this e-mail and refrain from any disclosure or action
based on the information.
> ***
>


Reply via email to