Tycho 2.6.0 release #497
Replies: 9 comments 5 replies
-
|
M2E build looks good with this snapshot: |
Beta Was this translation helpful? Give feedback.
-
|
@cdietrich can you confirm that this works with xtext/xtend? |
Beta Was this translation helpful? Give feedback.
-
|
@seiferma @SchubP @Dmor01 @vogella @RoiArthurB @ppogorzelski can you verify the 2.6.0-SNAPSHOT? |
Beta Was this translation helpful? Give feedback.
-
|
I verified this with several internal builds without a problem. |
Beta Was this translation helpful? Give feedback.
-
|
Verified on my end as well |
Beta Was this translation helpful? Give feedback.
-
|
Build works perfectly with SWT 2021-12 and OpenJDK 17.0.1! 🚀🚀 |
Beta Was this translation helpful? Give feedback.
-
|
@laeubi Update on my tests : Keeping the project as it was and just changing the tycho version for the snapshot one did worked perfectly. After that, just changing the JDK version did worked too (leaving just some warnings). But, since I tried to clean it all, especially changing in my to this one : The compilation ( I probably miss something simple, but I don't see what I miss 🤔🤔 |
Beta Was this translation helpful? Give feedback.
-
|
Tychos default EE is currently java 11: you need to explicitly configure the EE then e.g in your target platform or pom. There is also a TODO in the code I think Tycho should actually default to the current build-vm-EE (I assume you are running with J17 now), you might want to open an issue for that. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the answer, I understand your explanation for the default JavaSE-11 value now :) However, in my case, I do explicit the EE in each of my bundles with Eclipse or by scripts : Which gives me the following MANIFEST.MF : And produce the error in my message (not on the same bundle, but it's the same process and the same error for each of them) :/ |
Beta Was this translation helpful? Give feedback.
-
|
In the manifest you define a Requirement on JavaSE-17 but your target cannot fulfill this as it not provides JavaSE-17 (only JavaSE-11), that's why you get this error. You can configure it in your target file if your are using one:
Or in the pom with the target-platform-configuration:target-platform-configuration mojo. |
Beta Was this translation helpful? Give feedback.
-
|
Ok I see the difference, thanks a lot for your help ! 🙏 EDIT : Ok so setting the EE in my pom.xml did fix every problem. I'll still open 2 issues to (1) propose to upgrade to the latest LTS version (JavaSE-17) and (2), as you suggested, propose to use the current jdk by default instead of forcing one. Thanks again for your help 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
My example RCP builds work fine with this version. |
Beta Was this translation helpful? Give feedback.
-
|
In our first tests until now, 2.6.0-SNAPSHOT seems to works like a charm with java.vm.name=OpenJDK 64-Bit Server VM; java.version=17.0.1; os.arch=amd64 by Adoptium and some of our projects (a few hundred thousand LOC). Thanks a lot (y) |
Beta Was this translation helpful? Give feedback.
-
|
Tycho 2.6.0 has been released and is available from Maven Central repository. 🆕 https://github.com/eclipse/tycho/blob/tycho-2.6.0/RELEASE_NOTES.md
and thanks and to everyone who helped us with testing the staged version. Regards, |
Beta Was this translation helpful? Give feedback.
-
We plan to release Tycho 2.6.0 at end of January 2022. For details of new features and bugfixes, see release notes.
Please help by testing the SNAPSHOTS build. To use it, change your tycho version to 2.6.0-SNAPSHOT and add the following snippet to your pom.
We plan to promote this release at end of month unless major regressions are found that can't be fixed at least one week before the release date.
Regards,
Tycho team
Beta Was this translation helpful? Give feedback.
All reactions