With the release of the Community Edition, the old build numbering which one used in the since-build attribute of the <idea-version> tag in plugin.xml has been replaced with a very odd version string like "IC 90.96". I was wondering how we make use of this to indicate that a plugin requires this particular build of IDEA?

But this doesn't work. I had to set the until-build to either 90.96 (or 90.97 and higher) to get the plugin working in the community edition:

<idea-version since-build="9000" until-build="90.96" />

Obviously, this isn't a feasible solution because i see that the number will be incremented to 90.97 or something else after the next release. So what is the correct build number range (upper limit) for the community edition?

But this doesn't work. I had to set the until-build to either 90.96(or 90.97 and higher) to get the plugin working in the communityedition:

since-build="9000" until-build="90.96" /> ]]>

Obviously, this isn't a feasible solution because i see that thenumber will be incremented to 90.97 or something else after the nextrelease. So what is the correct build number range (upper limit) forthe community edition?

With the release of the Community Edition, the old build numberingwhich one used in the since-build attribute of the <idea-version> tagin plugin.xml has been replaced with a very odd version string like"IC 90.96". I was wondering how we make use of this to indicate that aplugin requires this particular build of IDEA?

Just to be clear: Are you saying that it might be best to leave out the until-build attribute completely? I ask because I'm sure that at some point in the past, I had to add the until-build attribute because otherwise the plugin wouldn't show up as available (sometime during the 8.0 EAP IIRC), so removing it again makes me wonder if I might break my plugin for users with older IDEA versions.

Here's what my Code Review Plugin, which AFAIK works fine with all IDEA versions since 7.0, currently has in plugin.xml:

<idea-version since-build="7000" until-build="11999"/>

That has been working fine for me at least with the Maia EAPs, but a colleague who also uses the EAPs wasn't able to get it to work (it showed up as red) until he edited/removed the idea-version tag. Should I change the tag to the following?

<idea-version since-build="7000"/>

I suspect plenty of other plugins are suffering from similar problems too.

Regards,Chris

DJ> Specifying an upper limit doesn't make much sense because you don'tDJ> know when your plugin will actually stop working. There is noDJ> "correct" thing to specify there.DJ> >> I too am trying to make an existing plugin compatible against the>> Community edition (90.96 build). I refered to this Build numbers wiki>> http://www.jetbrains.net/confluence/display/IDEADEV/BuildNumberRang>> e s which suggests 10000+ as the build number range for IDEA9:>> >>

IntelliJ IDEA 9 ->> 10000+

>> >> But this doesn't work. I had to set the until-build to either 90.96>> (or 90.97 and higher) to get the plugin working in the community>> edition:>> >>

> since-build="9000" until-build="90.96" /> ]]>

>> >> Obviously, this isn't a feasible solution because i see that the>> number will be incremented to 90.97 or something else after the next>> release. So what is the correct build number range (upper limit) for>> the community edition?>> >> --->> Original message URL:>> http://www.jetbrains.net/devnet/message/5247929#5247929