They have been ranked minor - so at least beta-3, and risk being left to Maven 2.1 as we get into the business end of the release.
Of course, votes influence that, and patches make it happen :) Cheers, Brett On 9/16/05, David Pick <[EMAIL PROTECTED]> wrote: > > Thanks for the prompt response. > > Any idea when these will these features will be made available? > > Cheers > Dave > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 16 September 2005 14:33 > To: Maven Users List > Subject: Re: [m2] Snapshot dependency handling > > Hi David, > > install should not number the JAR, but deploy does. We have an open issue > to > download the numbered versions into a single SNAPSHOT version locally, as > well as making the numbering optional. Neither are included in beta-1. > > Regards, > Brett > > On 9/16/05, David Pick <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > If I build an artifact with a dependency on a snapshot (i.e. version " > > 1.0-SNAPSHOT") I get the latest copy of the dependency in the local > > repository named groupId/artifactId-1.0-yyyyMMdd.HHmm-s.jar. > > > > > > > > Is there a (simple) way to also generate a file in the local repository > > named groupId/artifactId-1.0-SNAPSHOT.jar whilst downloading a snapshot > > dependency? > > > > > > > > I want a file with a constant filename that represents the latest > > downloaded snapshot dependency for integration with third party tools > etc, I > > do not want to have to check/update path/classpath settings each time I > > perform a maven build. > > > > > > > > I am using Maven 2.0-alpha-3. > > > > > > > > Many Thanks > > > > Dave > > > > > > > > > > >
