[
https://issues.apache.org/jira/browse/QPID-8779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Partha Sarathy Maripini closed QPID-8779.
-----------------------------------------
Resolution: Won't Do
Not needed. broker-core no longer depends on Bouncy Castle, and the Bouncy
Castle plugin declares it as a provided dependency, so no build profile or
separate assembly is required. A deployment that must not ship the standard
Bouncy Castle libraries leaves out the plugin and the Bouncy Castle jars, or
installs a different generator through the SPI.
> [Broker-J] Configure build profiles and assembly isolation for BC-FIPS
> artifacts
> --------------------------------------------------------------------------------
>
> Key: QPID-8779
> URL: https://issues.apache.org/jira/browse/QPID-8779
> Project: Qpid
> Issue Type: Sub-task
> Components: Broker-J
> Reporter: Partha Sarathy Maripini
> Priority: Major
>
> *Background:*
> Standard Bouncy Castle (`bcprov-jdk*`) and `bc-fips` artifacts cannot coexist
> on the same runtime classpath due to package and class conflicts.
> *Tasks:*
> 1. Establish Maven build profiles or distribution assembly configurations to
> separate standard and FIPS artifact sets.
> 2. Ensure distribution archives bundle either the standard certificate plugin
> or the BC-FIPS plugin cleanly.
> 3. Add unit and integration tests verifying SPI resolution and certificate
> validity under both configurations.
> *Acceptance Criteria:*
> - Assembly builds generate non-conflicting classpath bundles for standard and
> FIPS targets.
> - Test suite passes under both execution profiles.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
