Skip to content

Commit babf6d9

Browse files
committed
When writing temporary projects, use more appropriate artifactIds
When we write a temporary project, it makes more sense to use the class' name as artifactId than a semi-random directory name of the temporary directory we just created. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
1 parent 8df91ef commit babf6d9

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

src/main/java/org/scijava/plugins/scripting/java/JavaEngine.java

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -369,7 +369,8 @@ private static MavenProject writeTemporaryProject(final BuildEnvironment env,
369369
}
370370

371371
// write POM
372-
return fakePOM(env, directory, fakeArtifactId(env, directory.getName()), mainClass);
372+
final String artifactId = mainClass.substring(mainClass.lastIndexOf('.') + 1);
373+
return fakePOM(env, directory, artifactId, mainClass, true);
373374
}
374375

375376
private static String fakeArtifactId(final BuildEnvironment env, final String name) {

0 commit comments

Comments
 (0)