You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Robert Scholte <rf...@apache.org> on 2012/10/02 22:12:50 UTC

preparations for release Maven Invoker

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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: preparations for release Maven Invoker

Posted by Olivier Lamy <ol...@apache.org>.
2012/10/5 Robert Scholte <rf...@apache.org>:
> 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?
Perso I would prefer setMvnCommand(String)
I have already seen folks using alias mvn-3 or mvn-2  etc...
The other solutions are IMHO very limited for such use cases.
>
> thanks,
> Robert
>
>
> Op Tue, 02 Oct 2012 22:12:50 +0200 schreef Robert Scholte
> <rf...@apache.org>:
>
>
>> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: preparations for release Maven Invoker

Posted by Robert Scholte <rf...@apache.org>.
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  
<rf...@apache.org>:

> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org