Ignore "The type XXX is already defined." message for JEP 247

[RussiaVk]

I'm using maven-compiler-plugin to make my project support run on different jdk version (JEP 247).

	<plugin>
		<groupId>org.apache.maven.plugins</groupId>
		<artifactId>maven-compiler-plugin</artifactId>
		<executions>
                    <execution>
                        <id>compile-java-8</id>
                        <goals>
                            <goal>compile</goal>
                        </goals>
                        <configuration>
                        	<compilerVersion>1.8</compilerVersion>
                            <source>1.8</source>
                            <target>1.8</target>
                            <compileSourceRoots> <compileSourceRoot>${project.basedir}/src/main/java</compileSourceRoot>
                            </compileSourceRoots> 
                        </configuration>
                    </execution>
                    <execution>
                        <id>compile-java-14</id>
                        <phase>compile</phase>
                        <goals>
                            <goal>compile</goal>
                        </goals>
                        <configuration> 
                            <release>14</release> 
                            <compileSourceRoots> <compileSourceRoot>${project.basedir}/src/main/java14</compileSourceRoot>
                            </compileSourceRoots>
                            <outputDirectory>${project.build.outputDirectory}/META-INF/versions/14</outputDirectory>
                        </configuration>
                    </execution> 
                </executions>
	</plugin>

And I added different of compileSourceRoots into classpath.
But eclipse error:

The type XXX is already defined.
I hope eclipse can ignore this error message.

[Marcono1234]

Seems to be related to #265

[stephan-herrmann]

Seems to be related to #265

Right, the request seems to be related to JEP 238, not JEP 247.

[stephan-herrmann]

The type XXX is already defined.
I hope eclipse can ignore this error message.

Ignoring that error is not a good idea, as it would be totally unclear which of the duplicates should be used for the rest of the build. Let's continue in #265 - closing this one.