On 19/12/11 21:32, Paolo Castagna wrote:
Benson Margulies wrote:
(Still haven't completely grokked why SNAPSHOT versions can't pull down
SNAPSHOT parent POMs but life is too short.)
Whoops, missed this question. Have you run 'mvn deploy' to push the
snapshot? Even if you have, the snapshot repo isn't in anyone's repo
list by default. They would have to add it to their settings.xml.
Does adding a<repositories> section in each of the modules help?
Maven cannot retrieve the parent pom.xml file from Maven Central
(which is the only repository available before retrieving the
parent pom itself).
Ah - good point. They are in the Apache POM which is jena-top's parent.
Adding them to settings.xml causes things to work. My bad.
It's not ideal because of the repetition, but if it works would be
not that bad (Apache Maven repositories are not going to change).
Could do - there's <repositories> in TDB and Fuseki currently which
current use the staged artifacts for testing.
My 2 cents,
Paolo
Thanks,
Andy
