ers, OSGi
> bundles or JPMS for that matter. Only with shared classpath junit
> “deployment”
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
> Von: Tibor Digana
> Gesendet: Sunday, July 4, 2021 10:19:45 PM
> An: Maven Users List
>
You can easily solve this.
Just create (N+1) module which contains test classes.
The N+1 module should inherit from the module N having normal sources.
The trick is to build module N, and then N+1.
On Fri, Jul 9, 2021 at 1:13 AM Brandon Mintern wrote:
> Tibor,
>
> Thanks for your thoughts.
No, it cannot be based on one use case. It must be based on a theory and
generic and representative principles.
On Fri, Jul 9, 2021 at 1:13 AM Brandon Mintern wrote:
> Tibor,
>
> Thanks for your thoughts. Would it be worthwhile for me to construct and
> share a minimal concrete example to
Tibor,
Thanks for your thoughts. Would it be worthwhile for me to construct and
share a minimal concrete example to motivate this discussion? It's not
clear to me that you're open to the possibility that I'm describing a
reasonable use case here.
On Thu, Jul 8, 2021 at 4:06 PM Tibor Digana
The tests are dedicated to the module sources and not to the other module/s.
They were not designed to be inherited and it is logical because unit tests
have to test a small unit code where the unit is a method, class or a
module.
Integration tests are used to test the whole application which is a
Thanks for the pointer to that conversation! Andreas described exactly my
issue in a much clearer and more concise way.
For now, test-jars seem to be the best path forward in spite of the
drawbacks. I'm considering writing a plugin to prototype the "stubs"
approach that I described.
On Thu, Jul
On Thu, Jul 1, 2021 at 12:15 PM Brandon Mintern wrote:
> Maybe one of these—or a better alternative—is already possible? I feel like
> I must be missing something. Is something wrong with the way I'm
> structuring my projects? Does Maven already provide a way to achieve this
> out-of-the-box? Is
classpath junit “deployment”
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: Tibor Digana
Gesendet: Sunday, July 4, 2021 10:19:45 PM
An: Maven Users List
Betreff: Re: Sharing Test Dependencies
I did not have time to read it all but I have to say that even the first
I did not have time to read it all but I have to say that even the first
point is bad.
Many people want to share test JAR as they initially think it is a good
idea. And then the problems would come.
sharing stubs? This domain/project may not fit to other domain/project, and
it creates dangerous
Hello all,
I'm running up against an issue that I'm sure has come up countless times.
How can we share test dependencies in a principled way? I would like to
configure our projects such that:
1. For a project *P*, its tests are associated with the project, so that
`mvn install` from the
10 matches
Mail list logo
