Dear CDK developers, I have run into minor issue with CDK binary releases (1.2.x or 1.3.x - does not matter). The problem is that cdk-1.3.8.jar contains CDK class + the classes from all dependent libraries. This makes it impossible for me to e.g. change the implementation of Log4j, because if JVM finds Log4j classes in cdk-1.3.8.jar, it will not continue searching the classpath, so I am stick to the version, which is bundled into CDK. Things get worse with slf4j, which is split into API and implementation: in case the API classes are taken from cdk-1.3.8.jar, they are binary not compatible with slf4j implementations available in the classpath (which e.g. have the higher implementation version), causing difficult-to-trace-down MethodNotFoundExceptions at runtime.
Perhaps, doing a correct splitting into smaller modules + tracing the dependencies is the best solution. It looks like Maven can help here. Finally I wonder, who is using CDK in Maven-based project and are there any ready-to-use POMs / Maven repositories? If not, is there anybody interested in modularizing CDK? Thanks -- With best regards, Dmitry ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Cdk-user mailing list Cdk-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdk-user
