>This patch unifies interactive and batch mode behavior.
filtering is done only in part of the code that get's executed when interactive mode is used. Batch mode has completely separate handling. I merged these two execution paths together so that the only real difference is that required user input in interactive mode is replaced with default values in batch mode
>Replacement of required properties now fails if transitive properties are not resolved.
code seems to call as property values containing references to other properties (like $
.itest1) as 'transitive properties'. If property references can't be resolved the build fails.
>There (is) also an oddity...
Codebase seems to treat groupId, artifactId, version (and package) a bit differently than other properties. Properties with same name can't be configured for instance as optional because what you'd only be generating duplicate properties with same name. This is just something that caught my eye.
There wasn't existing test cases to begin with so I only could test with my own code and while trying to keep the number of changed lines in minimum.