Contribute WTP 3.43 M3 to 2026-09

[nitind]

No description provided.

[merks]

@nitind

How are you going about determining which 3rd party bundles are missing from WTP's repository?

[merks]

In the past on several occasions I'm created a repository that is a small subset of Orbit to workaround shortcomings in the contributed repositories:

https://download.eclipse.org/oomph/simrel-extras/

So locally it's easy to run the validation from the *.aggr editor. When it complains about something missing, I find it in Orbit and then added it to this feature:

I can build a local update site and use that in the aggregator.

So with that approach, I can verify that this aggregates:

So I think these three bundles are needed for aggregation to be successful:

   <plugin
         id="jakarta.xml.soap-api"
         version="0.0.0"/>

   <plugin
         id="jakarta.mail-api"
         version="0.0.0"/>

   <plugin
         id="javax.xml.rpc-api"
         version="0.0.0"/>

[nitind]

So I think these three bundles are needed for aggregation to be successful:

   <plugin
         id="jakarta.xml.soap-api"
         version="0.0.0"/>

   <plugin
         id="jakarta.mail-api"
         version="0.0.0"/>

   <plugin
         id="javax.xml.rpc-api"
         version="0.0.0"/>

They're already imported in the org.eclipse.wst.ws_core.feature, which builds fine, but two were not part of the "base" site coming from server tools.

[merks]

Note that though an "import" does not lead to the bundle being included in the website. In general imports of bundles in features are mostly entirely useless because the bundle that need the import bundle already specifies such dependencies.

In any case, yes, whatever fails the aggregation is missing from "site" being contributed...

[merks]

I believe these are still missing from your update site:

These will only be present if you include them in the category.xml or if you include them in some feature that you don't contribute to SimRel.