1

When I run java code similar to this:

JavaCompiler compiler = ToolProvider.getSystemJavaCompiler();
...
CompilationTask task = compiler.getTask(null, javaFileManager, diagnosticCollector, null, null, Collections.singletonList(fileObject));
task.call();

A file called classlist.mf appears in my working directory.

None of my sources contain the string "classlist". I am only using the standard javax.tools api's. That file contains exactly one (of the many) classes that I generated:

org.optaplanner.core.impl.domain.common.accessor.generated.org.optaplanner.examples.common.domain.AbstractPersistable$getId

How can I prevent that classlist.mf file from appearing in my working directory?

Improve this question
2
  • 1
    Hey Geoffrey, you posted a blog where you write proper care needs to be taken that it doesn’t generate a classlist.mf file in the working directory. Did you ever figure this out? If so, can you please answer your own question here? Commented Dec 27, 2018 at 18:46
  • No, I didn't figure it out (if I recall correctly). Because of this problem - and the bootstrap performance cost - I ended up going with LamdbaMetaFactory instead which is sufficient for my use case... Commented Jan 1, 2019 at 15:46
Related questions
8
Why does Java generate Multiple .class files on compilation?
5
java generate class file at runtime
12
How to programmatically generate .class files?
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.