java - Internal dependencies class qualified name conflict -


there 2 dependency libraries in gradle project:

  • old: full util lib
  • new: db lib (fixed lib)

which both holds same db connection classes including package eg.: net.mycompany.common.dbsq.dbconnector().

what need ensure use of db connection classes new, keeping old (can without db classes) dependency due rest of needed utils, not available in new.

is there possibility exclude/include particular classes or packages of dependency? or ensure 'overriding' of same named classes? unfortunately not question of transitive dependency, name conflicting db connection classes in both. cant have impact on content of dependencies.

with specifying both compile dependencies, ide (idea) uses classes new, running .war in weblogic server uses db connection classes old.

any ideas? can give more specific description, quite general question.

if including 2 libraries, including them full.

i can think of 2 approaches:

  1. remove old dependency , check new libraries include classes depend on. usually, when project replaces packaging based on 1 full jar packaging based on more fine grined ones, can have full set of classes adding fine-grined libraries. if tell library easier answer more specific stuff.
  2. take old library , repackage needed classes. discouraged , easy lead issues.

best option 1.


Comments

Popular posts from this blog

PHP and MySQL WP -

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

go - golang pprof for c library code -