Test code not shared

[bentatham]

While we do this rarely, it is sometimes useful to be able to share test code with another project, for the purposes of testing there (often helper functions, etc).

For example, I have a project that explicitly declares two dependencies: for main and test jars (obviously part of a multi-module build):

    <dependency>
      <groupId>ca.nanometrics.util</groupId>
      <artifactId>system-util</artifactId>
      <version>${project.parent.version}</version>
    </dependency>
    <dependency>
      <groupId>ca.nanometrics.util</groupId>
      <artifactId>system-util</artifactId>
      <version>${project.parent.version}</version>
      <type>test-jar</type>
      <scope>test</scope>
    </dependency>

However, with the takari-lifecycle-plugin connector, a class from this test-jar cannot be found:

The import ca.nanometrics.util.TimingBreakdownTest cannot be resolved (io.takari.maven.plugins:takari-lifecycle-plugin:1.11.11:testCompile:default-testCompile:test-compile)

This worked fine before I tried the takari lifecycle. I suspect that this new plugin is trying to enforce test vs main classes being allowed, even in eclipse where such a notion does not exist. But perhaps this case of the test-jar as well being declared is not handled.

Version: Mars.1 Release (4.5.1)
Build id: 20150924-1200
Maven Integration for Eclipse: 1.7.0.20151124-2302
io.takari.m2e.lifecycle.feature.feature.group: 0.1.0.201507181950

[ifedorenko]

Please provide a small standalone example project that demonstrates the problem. Supported for classified artifacts is very fragile in general, so it is important to have specific example.