eclipse-packaging / packages

Eclipse IDE product definitions.
Eclipse Public License 2.0
4 stars 11 forks source link

jakarta.annotation-api_1.3.5.jar not available in Eclipse RCP 2023-09 #61

Closed tito-cu closed 10 months ago

tito-cu commented 12 months ago

While the jar "jakarta.annotation-api_1.3.5.jar" is available in the 4.29 repository for Eclipse 2023-09: https://download.eclipse.org/eclipse/updates/4.29/R-4.29-202309031000/plugins/

This jar is is not found in the zip for the Eclipse 2023-09 IDE (using "Eclipse IDE for RCP and RAP Developers") downloaded from https://www.eclipse.org/downloads/packages/. There the jar "javax.annotation_1.3.5.v20200909-1856.jar" is still used (/plugins + /artifacts.xml). This is a problem for people that use "Require Bundle" in the IDE for example.

merks commented 12 months ago

See this comment:

https://github.com/eclipse-platform/eclipse.platform/issues/691#issuecomment-1722876393

tito-cu commented 12 months ago

Hi @merks,

Since previous eclipse-platform ticket is closed maybe better to continue here:

This is not about providing endless version streams. It is more of a question (problem) why we have a discrepancy between what is being delivered in the IDE and what is found in the official 4.29 repo, shouldn't they match? Eclipse 2023-09 is based on 4.29 so one should expect that jars found in the 4.29 repo will match with what it is delivered in the IDE (here is: the repo has "jakarta.annotation-api_1.3.5.jar" while the IDE comes with javax.annotation_1.3.5.v20200909-1856.jar)?

akurtakov commented 12 months ago

My guess for what happens is that:

To resolve these included features will have to audited to use Import-Package and/or to explicitly require jakarta-annotations.

merks commented 12 months ago

Yes, it's exactly as @akurtakov "guessed". See audit here:

https://github.com/eclipse-platform/eclipse.platform/issues/691#issuecomment-1722909082

akurtakov commented 12 months ago

So an update of XWT (at least) is needed.

jonahgraham commented 12 months ago

This is a problem for people that use "Require Bundle" in the IDE for example.

I think that is outside of the responsibility of the Eclipse Packaging Project - if a project has a require-bundle on some third party library there is no guarantee that library will be included in an EPP produced output.

For the record, there are lots of changes expected to bundle names in the coming months and as all contributing projects make their updates. (e.g. org.apache.commons.io -> org.apache.commons.commons-io as bundle names, but with the same package names).

merks commented 10 months ago

There is nothing for which to take action here. That bundle will generally not be installed in products anymore.