Description Till Brychcy 2018-01-22 12:56:53 EST

DESCRIPTION:
Create a simply maven project with the following pom.xml:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>

	<groupId>completionbug</groupId>
	<artifactId>m1</artifactId>
	<version>1.0-SNAPSHOT</version>
	<packaging>jar</packaging>

	<dependencies>
		<dependency>
			<groupId>org.eclipse.collections</groupId>
			<artifactId>eclipse-collections-api</artifactId>
			<version>9.1.0</version>
		</dependency>
	</dependencies>
	<build>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>3.7.0</version>
				<configuration>
					<source>9</source>
					<target>9</target>
				</configuration>
			</plugin>
		</plugins>
	</build>
</project>

Now create module-info.java and try to complete:
module m1 {
	requires //<- complete before comment
}

"eclipse-collections-api" is proposed, but the Automatic-Module-Name for this jar is "org.eclipse.collections.api".

ANALYSIS:
In PackageFragmentRoot.getAutomaticModuleDescription(), getRawClasspathEntry() is used, which returns the entry for the "Maven Dependencies" classpath container, but there is no handling for this kind of classpath entry in the switch in PackageFragmentRoot.getAutomaticModuleDescription(IClasspathEntry)

PATCH: 
Use getResolvedClasspathEntry() in PackageFragmentRoot.getAutomaticModuleDescription()