Don't we need to remove arquillian-jakarta from the bom:

[starksm64]

Issue Overview

I see a PR to update the arquillian-jakarta version in the bom:
#596

I thought we had pulled out all non-arquillian-core artifacts from the bom.
It is an independent release at this point with its own bom, so it should be removed.

Expected Behaviour

We only have arquillian-core artifacts in the bom.

Current Behaviour

We have a reference to a 1.8.1.Final arquillian-jakarta artifact.

[jamezp]

This came from #581 and is used for the integration tests. I suppose we could remove it and rely on the implementations to bring in the dependencies they need transitively.

[hantsy]

There was an Aruillina Universe BOM project, but not active now.

I would like there to be a standalone BOM project to cover all the essential Arquillian projects for developers, including :

• Arquillian Core
• Arquillian Jakarta
• Arquillian Drone/Graphene, optional to be considered if it is aligned with the core in time in the future.

And like the Jakarta EE spec migration, when there are some breaking changes/upgrades in the major version in the core, other projects will provide an upgrade respectively and finally offer a stable version in the BOM, eg using YYYY.MM.RELEASENO as version.

[jamezp]

At this point these are all different projects and IMO it doesn't make sense to have a grouped BOM. That would mean the BOM would need to release any time each of these independent projects are released. That sounds like a lot of work for little gain IMO.

As for Arquillian Drone and Arquillian Graphene, I don't know what the state of those projects are.