Stefano Cordio

Moving OSGi integration tests to a separate artifact would also address #2347.

Proposal for a first milestone: 1. Update the project to be a multi-module: ``` assertj-build |--- assertj-core ``` 2. Convert `assertj/assertj-parent-pom` to be a submodule ([keeping git history](https://www.nomachetejuggling.com/2011/09/12/moving-one-git-repo-into-another-as-subdirectory/)) and archive...

Point 3 is where the magic happens 🪄 😄 We can selectively build submodules, I guess a mixture of the following options can help tune our workflows ([source](https://blog.sonatype.com/2009/10/maven-tips-and-tricks-advanced-reactor-options/)): ``` -rf,...

> Convert `assertj/assertj-parent-pom` to be a submodule ([keeping git history](https://www.nomachetejuggling.com/2011/09/12/moving-one-git-repo-into-another-as-subdirectory/)) and archive the source repository Done with the following steps: 1. Clone a fresh copy of `assertj/assertj-parent-pom` 2. Move all...

> Rename `assertj/assertj-core` repository to `assertj/assertj` Done.

Proposal for the second milestone: 1. New modules to better segregate integration tests: ``` assertj-build |--- assertj-core |--- assertj-parent |--- assertj-tests |--- assertj-integration-tests |--- assertj-core-junit4-with-opentest4j |--- assertj-core-osgi |--- assertj-core-testng-with-junit4 |---...

Under `assertj-tests`

If I got it correctly, your proposal is to create assertions for `java.lang.ClassLoader`. I think it would be a nice addition. Would you like to work on it? As it...

At the moment I would say it's a breaking change we would like to keep, especially if you have a way around it

I added one more breaking change to the release notes, also with the solution described by @filiphr.