Skip to main content
Mar 11, 2022 3:00 PM UTC
Solved

import custom extension failed: JAR conflict Checking deployed extension JARS

JAR conflict Checking deployed extension JARS [existing: xyz01.jar, package: xyz02.jar] 2022-03-11 14:37:44.606+0000 [L: ERROR] [O: c.t.e.u.ExtensionPackageUtilities] [I: ] [U: Administrator] [S: ] [P: ] [T: http-nio-8080-exec-2] Checking deployed extension JARS conflict(s) detected [package: xyz02]. Check application log for details!

 

according to my test, extensions abc01, abc02, abc03, ..., can't import together onto one twx, but abc01, xyz01,xz01 can. So it seems if the name differences are only in the digits, twx9.3.0 failed to distinguish during import.

slangleyAnswer
Apr 22, 2022 5:47 PM UTC

Hi @QZ_ASGRA.

 

We did some additional research and testing, and found that it appears the problem is caused by the fact that the root names are the same.  In the following example, the first digit will terminate the root name resulting in the same name:

 

TWQA709_ExtensionA.jar root name is TWQA
TWQA709_ExtensionB.jar root name is TWQA

 

Try changing the name of the jar to something unique and see if that resolves the issue.

 

Regards.

 

--Sharon

9 replies

Mar 11, 2022 10:10 PM UTC

 Hi,

 

Read this article - "Error "Checking ThingWorx system JARS conflict(s) detected" when importing customized Extension in ThingWorx": https://www.ptc.com/en/support/article/CS255014

QZ_ASGRAAuthor
Mar 12, 2022 12:14 AM UTC

I have checked that artical before my post actually, because I have tried to resolved it. Just to prove my guess, I have done a couple of tests, and I have attached the examples as well. My code didn't use any third party jar or lib , just one service call for one thing shape, quite simple, because my original purpose was to test the gradle plugin actually.