@@ -591,7 +591,8 @@ handles those files by one rule:
591591
592592- ** Only a full run cleans up.** A run of the project's whole generator list decides; a run
593593 narrowed to some generators (` --generators ` ), to some entities (` meta gen <Entity> ` ,
594- ` metaobjects gen --entities ` ), or to a target that shares its directory with a target left
594+ ` metaobjects gen --entities ` , ` dotnet meta gen --entities ` , Maven ` -Dmeta.entities ` ), or to
595+ a target that shares its directory with a target left
595596 out, deletes nothing, because the files of the part it skipped would all look stale. So
596597 does ` --baseline=adopt ` , which writes nothing by definition.
597598- ** A candidate is a file the manifest says ` gen ` wrote.** It lies under an output directory
@@ -612,8 +613,10 @@ handles those files by one rule:
612613 that name is not mistaken for generated output.
613614- ** A dry run** (` meta gen --dry-run ` ) reports what it would remove and removes nothing.
614615
615- On ** Java and Kotlin** every ` mvn metaobjects:generate ` execution is a full run, since its
616- ` <generators> ` list is always complete. Every manifest entry names its owner: the generator's
616+ On ** Java and Kotlin** every ` mvn metaobjects:generate ` execution runs the whole
617+ ` <generators> ` list, since there is no ` --generators ` narrowing; a run narrowed by
618+ ` meta.entities ` is the one exception, and it deletes no orphaned file (see
619+ [ Select objects] ( ../ports/java.md#generate ) on the Java page). Every manifest entry names its owner: the generator's
617620registry id and its output directory within the module, not the Maven execution, so
618621` default-cli ` , a renamed execution and the lifecycle execution agree. A recorded file no
619622generator emitted in this build is an orphan when this run's own generators own it, or when
0 commit comments