Manual export of a product picks the wrong version of a JAR from the target platform

[AWanner23]

We use a frozen version of the Eclipse as a target platform. There are two versions of guava jars there, the newer one is used by our plugins.
The manual export from the product file takes the wrong one, but the launcher generated from the product file uses the right one.
It seems to be not always the case, just in our linux IDE Eclipse Version: 2023-12 (4.30.0)
Build id: 20231201-2043.

[merks]

Manual exports really are not well supported nor well tested. Investing effort into a Maven/Tycho build is significant work, but it is best for the long term...

[laeubi]

See

• Rework the PDE Export Wizards for products, features, bundles and categories using P2 #862

[laeubi]

Investing effort into a Maven/Tycho build is significant work, but it is best for the long term...

Actually it is quite easy:
https://tycho.eclipseprojects.io/doc/latest/StructuredBuild.html

[AWanner23]

Ah, I understand. Thank you for the information about the structured build. It seems like a little-effort-approach if it works for us.

[gireeshpunathil]

for the export function - whether manual or via tycho - I would expect to either run the same capability under the cover, or at least produce the same result. looks like that is not the case here.

looks like a way forward is to see which route is working fine (tycho?) and make the other one (manual export of PDE) at par with that?

[laeubi]

As mentioned here it internally uses ant + pde build, as even Eclipse itself is produced using Tycho/p2 these days I see little value in enhancing PDE build and that's also a reason it is abandoned.

If this is crucial to someones business and likes to speed up the development one can contact me to enter a contract about this specific issue or if there is need for dedicated enterprise support.

Of course a PR to fix the problem would also be welcome as plugin developers should be familiar with Eclipse PDE, see the contribution guides here and if Eclipse is an important Technology one maybe even want to join the Eclipse IDE Workingroup that also regularly funds development in critical areas or consider a funding to improve Eclipse IDE in general. Maybe @jonahgraham can even bring up the topic there, but from the last WG minutes I got the expression that individual funding of issues is no longer a priority.