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 <[email protected]> wrote: > 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 bunch > of compiled and packaged modules but these tests also do not need to be > shared. It's enough if a separate module is called IT and it is built at > last in the CI process. > > On Fri, Jul 9, 2021 at 12:41 AM Andy Feldman <[email protected]> > wrote: > > > On Thu, Jul 1, 2021 at 12:15 PM Brandon Mintern <[email protected]> > > 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 there a plugin that provides something like the > > "stubs" > > > functionality? > > > > > > > There was some discussion of this issue on this list a year ago as well: > > > > > https://lists.apache.org/thread.html/r6bfcf85aa7fd2b9a02a3f2513b9e10f1141b9102fda2bfc533d02379%40%3Cusers.maven.apache.org%3E > > > > The conclusion was also that there's no great way to accomplish this. I > > think one good way to fix this issue would be to have Maven resolve > > test-scoped dependencies transitively when you depend on test-jars, but > > perhaps there's a good reason why that's not practical or not a good > idea. > > > > -- > > Andy Feldman > > >
