We define a simple test class to verify basic operations.

Fixes #1888

Signed-off-by: BJ Hargrave <[email protected]>

bnd-maven-plugin. So we use `-snapshot: SNAPSHOT` to correct this.

We also use `-noextraheaders: true` to remove headers which can break
reproducible builds. This elides `Bnd-LastModified` so we can remove it
from `-removeheaders`.

See https://github.com/bndtools/bnd/blob/master/maven/bnd-maven-plugin/README.md#reproducible-builds

Signed-off-by: BJ Hargrave <[email protected]>
Handle soft proxies for custom assert classes in OSGi bundles (#1979)

When using a composite class loader for defining soft proxies when the
assert class is from a different class loader than the AssertJ classes,
we now use the composite class loader as the ClassLoadingStrategy for
ByteBuddy. This is necessary for Java 9+ to avoid the
ClassLoadingStrategy.UsingLookup default strategy used by AssertJ for
Java 9+. That strategy always defines the proxy classes in the class
loader defining the assert class ignoring the specified class loader.
This change is also beneficial for Java 8 as it avoids the need to
reflectively call the composite class loader to define the proxy
classes.

We refactor the CompositeClassLoader into the
ClassLoadingStrategyFactory class so that we can centralize the logic
for class loader and class loading strategy determination. Assumptions
is updated to use these changes which prepares it for a future where it
could support defining custom assumptions.

Finally, we update the class loader used for the ByteBuddy class caches
to use the class loader of the assert class rather than AssertJ's class
loader as the key. This is important in the OSGi case where multiple
bundles could define custom assertions with the same class name and we
must allow for unique proxy class generation for each bundle.

Fixes #1979

Signed-off-by: BJ Hargrave <[email protected]>

This ensures that ByteBuddy experimental features can be enabled setting
the 'net.bytebuddy.experimental' property also when AssertJ is used as
a dependency of other applications.

Separate them from other soft assertions tests

New order of priority:
* org.testng.SkipException
* org.junit.AssumptionViolatedException
* org.opentest4j.TestAbortedException