+1 (non binding) On 5/3/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
On May 2, 2007, at 7:18 PM, Brian E. Fox wrote: > Ok, here's where we are at: > > Still open: > > * [MINSTALL-18] - Bad algorithm to decide if the main artifact > is to be installed or not > > I think this could be easy to fix, but it needs a test case. > I'm out of time for now to make one. > > * [MINSTALL-30] - Command Line parameter 'version' does not > override pom file > > This involves rewriting the pom a little, probably making a > copy, then parsing and overriding the values from the CLI and using > that pom to install. I suggest we bump to 2.3. > > * [MINSTALL-37] - Add support to force install:install to use a > specific version > See separate vote email on this one. > > Fixed in 2.2: > > ** Bug > * [MINSTALL-19] - install-file sets distributionManagement > status to deployed > * [MINSTALL-23] - Issue tracking URL points to maven 2 jira. > * [MINSTALL-24] - Unable to install source or javadoc artifacts > in local repository > * [MINSTALL-29] - Can't use maven-install-plugin with > <goal>install-file</goal> in POM > * [MINSTALL-32] - classifier does not work on install:install- > file, default artifact overwritten > * [MINSTALL-34] - Make the install plugin work due the > repository-manager has been moved to archiva. > * [MINSTALL-36] - install:install-file ignores -DrepositoryLayout > > ** Improvement > * [MINSTALL-12] - Parameters should not be read-only > * [MINSTALL-35] - Possibility to install an artefact on a given > repository directory > > > I think we should proceed with a 2.2 release and bump the rest to 2.3. +1 --jason --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
