[MDEPLOY-16] snapshot deploy <-> dependency not working

[jira-importer]

spencer p opened MDEPLOY-16 and commented

I deploy a jar w/ the following pom.xml contents..

—
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>org.sporty</groupId>
<artifactId>qdox</artifactId>
<version>1.6-SNAPSHOT</version>
....
—

It drops the snapshot off at http://sporty.org/java/repository/org/sporty/qdox/ just fine. Iin my project, I have a dependency:

---

<dependency>
<groupId>org.sporty</groupId>
<artifactId>qdox</artifactId>
<version>1.6-SNAPSHOT</version>
</dependency>
—

It checks the repository, acessible via http at the above url, but fails. I get -

Downloading: org/sporty/qdox/1.6-SNAPSHOT/qdox-1.6-SNAPSHOT.jar
[WARNING] Unable to get resource from repository remote (http://sporty.org/java/
repository)

88.45.111.200 - - [12/Oct/2005:16:25:42 -0400] "GET /java/repository/org/sporty/qdox/1.6-SNAPSHO
T/qdox-1.6-SNAPSHOT.pom HTTP/1.1" 404 357 "-" "Java/1.5.0_04"
88.45.111.200 - - [12/Oct/2005:16:25:42 -0400] "GET /java/repository/org/sporty/qdox/1.6-SNAPSHO
T/qdox-1.6-SNAPSHOT.jar HTTP/1.1" 404 357 "-" "Java/1.5.0_04"

I like the ability to create build numbers w/ timestamps. If i turn the feature off via uniqueVersion, it works fine. Enable it, and it breaks.

---

Remote Links:

• GitHub Pull Request #228
  

[jira-importer]

Brett Porter commented

did the entire deploy process complete?

It looks like maven-metadata.xml didn't get written

[jira-importer]

spencer p commented

Yes, it ran to completion. There is a maven-metadata.xml at http://sporty.org/java/repository/org/sporty/qdox/maven-metadata.xml, but maybe that is not the one you are talking about?

[jira-importer]

Brett Porter commented

I see your repo is public - everything looks in order.

It may be requesting SNAPSHOT instead of the build number because you have <uniqueVersion> set to false?

[jira-importer]

spencer p commented

I just retried to recompile and now it downloaded the module fine. Serverside seems fine, confirmed, well and dandy.

Here's my access log on the webserver getting the info...

64.145.111.200 - - [13/Oct/2005:12:47:07 -0400] "GET /java/repository/org/sporty/qdox/1.6-SNAPSHOT/maven-metadata.
xml HTTP/1.1" 200 308 "-" "Java/1.5.0_04"
64.145.111.200 - - [13/Oct/2005:12:47:07 -0400] "GET /java/repository/org/sporty/qdox/1.6-SNAPSHOT/maven-metadata.
xml.sha1 HTTP/1.1" 200 40 "-" "Java/1.5.0_04"
64.145.111.200 - - [13/Oct/2005:12:47:08 -0400] "GET /java/repository/org/sporty/qdox/1.6-SNAPSHOT/qdox-1.6-200510
12.201618-2.pom HTTP/1.1" 200 384 "-" "Java/1.5.0_04"
64.145.111.200 - - [13/Oct/2005:12:47:08 -0400] "GET /java/repository/org/sporty/qdox/1.6-SNAPSHOT/qdox-1.6-200510
12.201618-2.pom.sha1 HTTP/1.1" 200 40 "-" "Java/1.5.0_04"

So I tried a second deploy to http://sporty.org/java/repository/org/sporty/qdox-huh/ and pointed my project at that in my pom.xml. Then I nuked the ~/.m2 directory and got the same issue all over again. All of my other dependencies redownloaded fine, 'cept this particular one.

Downloading: org/sporty/generama/1.2/generama-1.2.jar
Transferring 93K
Downloading: org/sporty/qdox/1.6-huh-SNAPSHOT/qdox-1.6-huh-SNAPSHOT.jar
[WARNING] Unable to get resource from repository remote (http://sporty.org/java/
repository)

To answer your last question, for the projecet I'm coding and downloading dependencies with, no, it's not mentioned

---

<dependency>
<groupId>org.sporty</groupId>
<artifactId>qdox</artifactId>
<version>1.6-huh-SNAPSHOT</version>
</dependency>

---

On my upload, it is set to true. Now the access logs show the same issue all over again -

64.145.111.200 - - [13/Oct/2005:12:54:29 -0400] "GET /java/repository/org/sporty/qdox/1.6-huh-SNAPSHOT/maven-metad
ata.xml HTTP/1.1" 404 358 "-" "Java/1.5.0_04"
64.145.111.200 - - [13/Oct/2005:12:54:30 -0400] "GET /java/repository/org/sporty/qdox/1.6-huh-SNAPSHOT/qdox-1.6-hu
h-SNAPSHOT.pom HTTP/1.1" 404 365 "-" "Java/1.5.0_04"

[jira-importer]

Brett Porter commented

I can download it using

<artifactId>qdox-huh</artifactId>
<version>1.6-SNAPSHOT</version>

from your repo. You had the "huh" in the wrong place.