Thanks Justin. Looks like when using an undefined <repository> the... <snapshots><enabled>false</enabled> I had to define a repo and make this true. I'm not sure this is a helpful default. Not when there is <dependency><version> and version ranges e.t.c. Anyway, that's my 2c :)
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd";> ... <profiles> <profile> ... <repositories> <repository> <id>codehausSnapshots</id> <name>Codehaus Snapshots</name> <releases> <enabled>false</enabled> <updatePolicy>always</updatePolicy> <checksumPolicy>warn</checksumPolicy> </releases> <snapshots> *<enabled>true</enabled>* <updatePolicy>never</updatePolicy> <checksumPolicy>fail</checksumPolicy> </snapshots> <url>http://snapshots.maven.codehaus.org/maven2</url> <layout>default</layout> </repository> </repositories> <pluginRepositories> ... </pluginRepositories> ... </profile> </profiles> ... </settings> On Wed, Feb 17, 2010 at 12:01 PM, Justin Edelson <[email protected]>wrote: > You are seeing the correct behavior in that mvn deploy will deploy to the > snapshot repository. Can you explain what you mean by "break all > 0.5-SNAPSHOT" dependencies? Maven should be resolving the timestamped > SNAPSHOT. > > Justin > > On Tue, Feb 16, 2010 at 8:22 PM, Andrew Hughes <[email protected]> wrote: > > > Hi All, > > > > I have looked but not be able to see how I get anything into our > > <snapshotRepository>. > > > > Release appears to target releases (i.e. not SNAPSHOT), install appears > to > > only be local (~/.m2) and deploy does put this in the > <snapshotRepository> > > but it replaces the 0.5-SNAPSHOT version with say 0.5-YYYYMMDD (and that > > seems to break all 0.5-SNAPSHOT dependencies). > > > > So how is this done? > > > > Thanks in Advance > > --AH > > >
