The repo structure is ok, your maven should download the metadata file [1]
which has a reference to the last snapshot index then it should continue
downloading the pom [2] and jar [3] files.
Maybe something wrong in your local repo cache, try to force updating
snapshots running:
mvn -U clean
indeed mvn clean install -U does the trick...
Thanks Manolo
On Thu, Aug 21, 2014 at 4:24 PM, Manuel Carrasco Moñino man...@apache.org
wrote:
The repo structure is ok, your maven should download the metadata file [1]
which has a reference to the last snapshot index then it should continue
For what its worth, we use a slightly different snapshot url:
https://oss.sonatype.org/content/repositories/google-snapshots/. This
appears to only contain snapshots instead of releases and snapshots.
The /google/ url for whatever reason has a newer md5 and sha1 for the
maven-metadata.xml file,
Right, both contain the same snapshot versions. Our jenkins CI server is
pushing to the google-snapshots folder, hence some process else should be
mirroring to the google one after a while, that is the reason for
differences in sha1/md5. I think the best choice is to point to the url you
suggest.
We should add a section on the website explaining how to install and use
the snapshot.
On Thu, Aug 21, 2014 at 4:45 PM, Manuel Carrasco Moñino man...@apache.org
wrote:
Right, both contain the same snapshot versions. Our jenkins CI server is
pushing to the google-snapshots folder, hence some
