On 03/04/2020 12:46, Tom De Wolf wrote:
Hi,
I understand that for individual classes and non-java resources a
patch should replace them. However for directories which are actually
java packages this seems to be odd. Does this not make it impossible
to add a new class to an existing package or
Hi,
I understand that for individual classes and non-java resources a patch
should replace them. However for directories which are actually java
packages this seems to be odd. Does this not make it impossible to add a
new class to an existing package or replace only 1 class in a package but
keep t
Thanks for the explanation, it makes sense:
Patch acts more like an override than an append.
best,
Robert
On 3-4-2020 12:56:10, Alan Bateman wrote:
On 03/04/2020 10:17, Robert Scholte wrote:
> This issue was registered as SUREFIRE-1768[1]
> It contains a very small Maven project to demonstrate t
On 03/04/2020 10:17, Robert Scholte wrote:
This issue was registered as SUREFIRE-1768[1]
It contains a very small Maven project to demonstrate the issue.
That project contains one method executing the following:
Demo.class.getClassLoader().getResources("demo").asIterator().forEachRemaining(url
Hi,
On Fri, Apr 3, 2020 at 11:18 AM Robert Scholte wrote:
>
> This issue was registered as SUREFIRE-1768[1]
> It contains a very small Maven project to demonstrate the issue.
>
> That project contains one method executing the following:
>
> Demo.class.getClassLoader().getResources("demo").asItera
This issue was registered as SUREFIRE-1768[1]
It contains a very small Maven project to demonstrate the issue.
That project contains one method executing the following:
Demo.class.getClassLoader().getResources("demo").asIterator().forEachRemaining(url
-> {
System.out.println(url.getFile()); //
