Github user seanf commented on the pull request:
https://github.com/apache/maven-surefire/pull/108#issuecomment-161909472
Hi Tibor,
I don't understand. Are you saying you did try to build an IT for this?
Could you share it, please? What counts would you consider realistic?
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/108#issuecomment-161945817
@seanf
>>Are you saying you did try to build an IT for this?
reuseForks=false would not work in 2.19 feature.
Initially skipAfterFailureCount was not
On 03/12/2015 19:49, Robert Scholte wrote:
After reading the specs it seems like I can only refer to a directory
containing modules. For a dependency specified in the pom.xml I could
refer to the directory (within the local repository) containing that
specific artifact. However, such
Exploded modules are useful in developer usecases. For example, I work
on a codebase with 25M+ lines of code spread over 1100+ projects. To
save time, we suppress packaging of jars when developers run builds
locally.
--
Regards,
Igor
On Fri, Dec 4, 2015, at 07:03 AM, Alan Bateman wrote:
>
> On
On 04/12/2015 12:27, Ali Ebrahimi wrote:
Just as I said in another thread post:
If we have module group concept and modules belong to same module
group loaded by same classloader then we can support splited packages.
This way each module group maps to each classloader.
This will support
