Community
Participate
Working Groups
Seems like m2eclipse always turns on --batch mode. The cause is that interactive executions resort on default values. For example, one cannot interactively type in the version identifiers and other properties that *should* be asked by release:prepare goal - instead, the build resorts to the default values. I don't know the reasoning behind setting it always enabled, but maybe allow disabling the --batch-mode through an additional checkbox on the launch page? Previous questions about the issue (with no answers): http://maven.40175.n5.nabble.com/release-prepare-in-non-batch-mode-td511082.html http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg00008.html
closing old/stale bugreports
I think this is a valid issue. There are some helper plugins that cannot be executed as m2e launch in practice because of the fact that the batch mode cannot be disabled. My use case: Update a version in a multi-module project with versions:set goal(versions-maven-plugin). When the plugin is launched in interactive mode it would prompt for the new version. However, in batch mode you have to specify the new version as parameter in the launch file and therefore cannot be re-used because you always have to change it. It would be nice to have a "Batch Mode" checkbox in the launch dialog which is of course enabled by default to control the "-B" command line option.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
