ping!
My current thought:
- Let's go for 2.1 and move to 3.0 once MSHARED-20 is included.
- Use the enum-solution for MvnCommand
Any objections?
thanks,
Robert
Op Tue, 02 Oct 2012 22:12:50 +0200 schreef Robert Scholte
<[email protected]>:
Hi,
I'd like to prepare a release of the Maven Invoker somewhere next week.
There are 3 issues left:
https://jira.codehaus.org/browse/MSHARED-20 - Extend Invoker API to
support the needs of the Release Plugin
We'll need to move the code from
org.apache.maven.shared.release.exec-package of the
maven-release-manager to the maven-invoker and get them in sync. I think
a lot of code is already available with a different classname.
Can be done later.
https://jira.codehaus.org/browse/MSHARED-141 - MavenCommandLineBuilder
incorrectly adds system properties
Looks like something cosmetic, we need tests to confirm that it will
work after applying the patch.
https://jira.codehaus.org/browse/MSHARED-251- Option to change from mvn
executable to mvnDebug executable
I'm not sure what's the preferred solution:
setMvnCommand(String); //extreme flexible, maybe a bit too much
setMvnCommand(MVNCOMMAND); //enum: bounded and extendable
useMvnDebug(boolean); //strict, but good enough if we don't expect more
executables
The current dev-version is 2.0.12-SNAPSHOT
This release will support most of the new Maven3 arguments (-t and -T
have been added), so I'd prefer to go for a 2.1, maybe even a 3.0
I've skipped --log-file, because there are already output handlers.
WDYT?
thanks,
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
