Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,12 @@ under the License.
<dependencies>
<!-- Maven Modules -->
<!--bootstrap-start-comment-->

<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk18on</artifactId>
<version>1.78.1</version>
</dependency>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not used by Maven core itself ... each project should define needed artifacts

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review and the suggestion.

I have removed the unused bcprov-jdk18on dependency as pointed out, since it is not required by Maven core itself and should be defined by individual projects if needed.

After updating the POM and force-pushing the changes to this PR, I verified that:

Maven no longer declares or resolves any BouncyCastle dependencies
The build completes successfully
No SNAPSHOT artifacts are downloaded
Offline build (mvn -o validate) works as expected

This aligns with Maven’s goal of avoiding unnecessary or unstable dependencies in core.

Please let me know if any further adjustments or validation are required.

<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-artifact</artifactId>
Expand Down