Setting an unlimited 'Until Build' for my plugin

Answered

Hello,

I received an email from JetBrains Marketplace saying that my plugin will not be compatible with the upcoming IDE version (2024.3)

Although I know what to do to make my plugin compatible with such a version, the email mentioned the following statement. 

“… The EAP version was just released, so you have time to address the issue by uploading a new version with a higher or unlimited 'Until Build' setting.”

My question is: How do I set an unlimited “Until Build” as suggested in the email? I could not find that in the documentation.

Thank you

0
8 comments

Thank you for the help Yann Cebron 

0

As a follow-up Yann Cebron

I might be misinterpreting the statement from the docs that says “An undefined value signifies compatibility with all IDEs starting from the version mentioned in since-build, including potential future builds that may cause compatibility issues.”

Because this is my observation so far

> No adding the pluginUntilBuild property ----→ Does not work

> Specifying pluginUntilBuild=null ----→ Does not work

> Specifying pluginUntilBuild= ----→ Works. (That is, I have the pluginUntilBuild followed by the `=` and no value after.

When I say “Does not work” I mean that I get the message “File '~/Developer/plugin-jetbrains/build/idea-sandbox/plugins/{PLUGIN NAME}/lib/instrumented-{PLUGIN NAME}-2.9.1.jar' contains invalid plugin descriptor.

So, is it correct to say that when the docs say An undefined value they mean to assign an empty value for pluginUntilBuild

0

When I specify `pluginUntilBuild=` in my `gradle.properties`, then the “Verify Plugin” job in the GitHub Action fails with:

 

Plugin problems:
              Invalid plugin descriptor 'plugin.xml'. The <until-build> attribute with only a branch number () is not valid. To specify compatibility with a whole branch, include a wildcard, for example '.*'.
              Invalid plugin descriptor 'plugin.xml'. The <until-build> attribute () does not match the multi-part build number format such as <branch>.<build_number>.<version>, for example, '182.4132.789'.
0

Interesting Wim Deblauwe . To me, nothing fails when using the option of `pluginUntilBuild=`

I managed to publish a beta version (it is under review) and nothing failed. Is your code publicly available? If so, can you share the link to the repo to see what it could be?

It might be worth mentioning that I am using version "1.17.0" of the org.jetbrains.intellij plugin

Finally, I also noticed why the other two options did not work: Because in the build.gradle.kts file I had forgotten I was accessing properties("pluginUntilBuild") and thus if I remove the property from the gradle.properties then it fails

0

Wim Deblauwe 

Not sure if it is the reason for the problem you are experiencing but I notice that you have in line #19 from the `gradle.properties` file

`platformPlugins=` that could be causing the problem. Have you tried removing it or placing a value in there instead?

0

The correct way to unset it as per the page linked above is

The until-build attribute can be unset by setting provider { null } as a value. Note that passing only null will make Gradle use a default value instead.

0

Please sign in to leave a comment.