Bug 575278 - Launch target validation is doesn't correctly validate when duplicate packages (different versions) are found
Summary: Launch target validation is doesn't correctly validate when duplicate package...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.20   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-06 08:50 EDT by Johan Compagner CLA
Modified: 2023-07-28 14:19 EDT (History)
0 users

See Also:


Attachments
lfs doesn't validate but packages are there. (59.14 KB, image/png)
2021-08-06 08:50 EDT, Johan Compagner CLA
no flags Details
4.0 not checked (65.75 KB, image/png)
2021-08-06 08:51 EDT, Johan Compagner CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Johan Compagner CLA 2021-08-06 08:50:35 EDT
Created attachment 286894 [details]
lfs doesn't validate but packages are there.

Not sure where this bug belongs to (i don't see a nice component for this, does it belong to the Equinox product and the p2?)

If you now have a Eclipse product based on 4.20 an also for example install Egit from the updates/2021.06 site.

You get a lot of different servlet stuff

JGit (org.eclipse.jgit.lfs.server) depends on javax.servlet 3.1

But eclipse now ships jakarta.servoy-api 4.0 that still has javax.servlet packages but with 4.0 version.

(and we now also have jakarta-servlet 5.0, but thats another package)

if i select both 4.0 and 3.1 and validate i get what i show in the first image.


if i then deselect the 4.0 version the lfs validats suddenly fine but ofcourse others then say i am not ok (second image)
Comment 1 Johan Compagner CLA 2021-08-06 08:51:39 EDT
Created attachment 286895 [details]
4.0 not checked
Comment 2 Eclipse Genie CLA 2023-07-28 14:19:58 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.