maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <br...@apache.org>
Subject Re: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?
Date Mon, 07 May 2007 11:40:37 GMT
I thought I already replied, sorry. Anyway, it sounds like this is a  
hack around the lack of ability to do something else, so I wouldn't  
be in favour of it. I haven't seen anyone else say they need this.

- Brett

On 06/05/2007, at 9:54 PM, Brian E. Fox wrote:

> I know many people where traveling last week for ApacheCon so I'm
> bumping this one again. I think it's important to get feedback on  
> this.
>
> Thanks
> Brian
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Wednesday, May 02, 2007 8:30 PM
> To: Maven Developers List
> Subject: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?
>
> I'm looking at the remaining open issues in MINSTALL. This one
> http://jira.codehaus.org/browse/MINSTALL-37 has had some unresolved
> discussion in the past. For easy reading, please see here:
> http://www.nabble.com/forceVersion-for-maven-install-plugin-- 
> tf3341272s1
> 77.html#a9292710
>
> In summary, Jason D is attempting to use a new flag in install to  
> force
> a version to "testing". This is to be bound to a pre-integration- 
> testing
> phase to make the plugin he's building get installed and available to
> the IT tests (to work around an invoker issue).
>
> Regardless of the use case, I'm leary about adding this flag to the
> install plugin because I can see people trying to use this to
> incorrectly force maven around some version (or version-less) scheme.
> That being said, I'm mainly only worried about this being used to
> influence the invocation of the goal in the default lifecycle and I  
> can
> see that it might be handy once in a while. I think perhaps a new goal
> that extended install:install and added this parameter would be a good
> compromise.
>
> I'm not sure what this new goal would be called and I think it
> essentially becomes very close to install:install-file once  
> MINSTALL-30
> is fixed except it is easier to bind in the pom.
>
> I'd like to move the discussion to a head and I think that since  
> this is
> a core plugin, it deserves a vote. I see 3 options:
>
> [] add forceVersion to install:install
> [] add new goal that extends install:install and includes forceVersion
> [] close MINSTALL-37 as won't fix and direct to use install:install- 
> file
> if needed.
>
> Here's my vote:
> [-1 (non veto)] add forceVersion to install:install
> [+0] add new goal that extends install:install and includes  
> forceVersion
> [+1] close MINSTALL-37 as won't fix and direct to use
> install:install-file if needed.
>
> Vote for 72 hrs.
>
> -----Original Message-----
> From: Jason Dillon [mailto:jason.dillon@gmail.com] On Behalf Of Jason
> Dillon
> Sent: Wednesday, March 14, 2007 11:29 PM
> To: Maven Developers List
> Subject: Re: forceVersion for maven-install-plugin?
>
> FYI, I've created a JIRA issue with the patch here:
>
>      http://jira.codehaus.org/browse/MINSTALL-37
>
> I'd appreciate it if this could get applied and new snaps
> deployed... :-)
>
> --jason
>
>
>
> ---------------------------------------------------------------------
> 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


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


Mime
View raw message