Confused with an instrumented jar present in the final plugin zip

Answered

We have an IntelliJ plugin which is having an intrumented jar present in the libs. 

Following is the structure of the build folder after the gradle build.

The zip file present in build/distribution folder has the following structure

 

We are not sure why do we get the instrumented jar packaged into the final zip, even though we see both intrumented & regular jar present in the /build/libs folder.

 

0
4 comments

Hi,

But we want to distrubte the final plugin.zip file to the clients. 

Here are the 2 jars generated after the build process.

Does it not make sense to include the .jar file instead of intrumented jar in the final zip when distrubiting to the clients?

Am I missing something?

P.S. We are using the Gradle IntelliJ Plugin(1.x)

0

You probably forgot to attach a screenshot.

Instrumented JAR should be included. As stated in the link I pasted:

The code instrumentation scans the compiled Java and Kotlin classes for JetBrains Annotations usages to replace them with their relevant functionalities.

Does it cause any issues?

0

Hi,
I am using Gradle IntelliJ Plugin (1.x) not the IntelliJ Platform Gradle Plugin(2.x)
No it doesn't cause any issue(not that i know of), but I was surprised to see instrumented jar in our final plugin zip, as my understanding was that instrumented jar is used only during development while profiling the plugin. I assumed only the jar (without instrumentation) should be shared with the clients

0

Please sign in to leave a comment.