release: 2022.3.*, 2022.2.4
Pakisan opened this issue · 4 comments
I spent a few days figuring out how this should work and still have no idea. Tried several configurations with the same behavior - errors while plugin validation.
If you develop a plugin, you can use new language features and APIs from Java 17, but only if the since-build attribute in plugin.xml is set to 223. If your plugin distribution needs to run on multiple versions of the IDE, for example, 2022.3 and 2022.2, then you must continue to use Java 11.
So I decided to next:
- This #12 PR will be merged into 1.8.0 release branch and released
- Those #11, #8 PRs will be merged to 2.0.0 release branch and released.
My main thought is to split releases and bind them to JRE instead of IDEA' versions, to save functionality for our users who stay on older releases.
Because of this I also will remove meta information from version - +2021 and replace it with jre+{version} instead.
1.*.*+jre11 - for JRE 11
2.*.*+jre17 - for JRE 17
Any concerns? If none I will merge your PRs till 23.01 and build releases
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Because of this I also will remove meta information from version - +2021 and replace it with jre+{version} instead.
1.*.*+jre11- for JRE 11
2.*.*+jre17- for JRE 17
The only question I would ask is: given that versions are being built for particular IDEA versions, isn't it better to know which plugin version is built for which IDEA version?
In theory you could version-name based upon all three items:
<plugin version>+<IDEA version>+jre<JRE version>
Because of this I also will remove meta information from version - +2021 and replace it with jre+{version} instead.
1.*.*+jre11- for JRE 11
2.*.*+jre17- for JRE 17The only question I would ask is: given that versions are being built for particular IDEA versions, isn't it better to know which plugin version is built for which IDEA version?
In theory you could version-name based upon all three items:
<plugin version>+<IDEA version>+jre<JRE version>
I thought about it too and created compatibility table in release/1.8.0
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience ❤️