This is the bit that matters:

        <plugin>
                <groupId>org.codehaus.gmavenplus</groupId>
                <artifactId>gmavenplus-plugin</artifactId>
                <version>1.5</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>testCompile</goal>
                        </goals>
                    </execution>
                </executions>

Interesting... when I make a project with this kind of config it does NOT add the groovy sources folder. So in principle these project should work fine.

What I do see however is that the gmavenplus-based configurator never removes the paths when they are already there. So if the eclipse metadata was already present in the projects, then even after remove 'compile' (and related) goals, the main groovy source folder will not be removed.

If its manually removed however it stays gone upon refresh. Same if we delete the metadata and reimport project.

I'll make some adjustments to how this works so that:

a) source folders with paths controlled by the configurator are removed if their respective goals are missing.

b) source folders that do not actually exist will never be added.

That should make doubly sure this works correctly.

Uh oh!

Missing source folders are added to classpath #186

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions