Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven acting strange if I create a 'runtime' directory #458

Open
BurtHarris opened this issue Apr 15, 2020 · 0 comments
Open

Maven acting strange if I create a 'runtime' directory #458

BurtHarris opened this issue Apr 15, 2020 · 0 comments

Comments

@BurtHarris
Copy link
Collaborator

@sharwell I don't understand this, can you help explain?

For years, we've had this is tool/pom.xml:

        <testSourceDirectory>test</testSourceDirectory>
        <testResources>
            <testResource>
                <directory>test</directory>
            </testResource>
            <testResource>
                <directory>../runtime</directory>
            </testResource>
        </testResources>

I think testResource ../runtime has unintended consequences, but they were not triggered until I created a runtime folder. What is a testResource for?

Background

Expected contents of tool/target/test-classes folder:

image

I was doing some reorganization to untangle the build system. Anyway, I created a runtime/ directory that was a peer of tool/ and started having the build files (e.g. package.json) in that directory. This had an unexpected impact on the maven folder:

image

The first time (after clean) test generation works OK, but if I re-run test generation, it fails:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants