Please move org.as3commons.logging.integration package to its own .swc

[GoogleCodeExporter]

I love as3commons-logging and the other common libraries, but a recent 
"improvement" has been hugely disruptive to me...

When I switched from as3commons-logging version 1.1 to version 2.5.1, my build 
process was suddenly broken by dependencies against several third-party 
libraries (which am I not using and am not interested in) present in 
org.as3commons.logging.integration.

Bear with me...  I understand the .swf link process and I am aware that if I 
link as3commons-library-2.5.1.swc directly into my .swf, the linker won't 
complain if my .swf doesn't actually depend on 
org.as3commons.logging.integration (and therefore won't depend on the 
third-party libraries) and there will be no problem.

HOWEVER...

In my projects, I routinely create a "ThirdParty.swc" which *includes* all my 
3rd-party libraries via the "-include-libraries" compiler switch.  This way, 
all of my modules don't need to endlessly duplicate numerous dependencies -- 
they all simply depend on ThirdParty.swc.  I use this technique in all of my 
build files and IDE configurations, implementing a "single point of change" for 
managing dependencies.

Previously, this approach worked wonderfully across the board with all of 
as3commons (since none of the libraries had any "invisible" external 
dependencies), but has been broken with the more-recent as3commons-logging and 
the "clever" dependencies in org.as3commons.logging.integration.

So, could you *please* consider moving the org.as3commons.logging.integration 
package to its own .swc so that its dependencies can be more explicitly 
controlled in build files and IDEs configurations?  Not everyone uses your 
libraries in the ways you might imagine.  I'm sure there must be others using 
the "common" .swc technique like me.

Thanks.

Original issue reported on code.google.com by m...@amphiox.com on 3 Aug 2011 at 10:45