dev@glassfish.java.net

Why is a non-SNAPSHOT pom.xml referencing a SNAPSHOT version artifact?

From: Sahoo <Sahoo_at_Sun.COM>
Date: Tue, 04 Mar 2008 21:19:16 +0530

I think we are not being careful enough while using Maven. I just
noticed that javax/activation/activation/1.1/activation-1.1.pom [1] is
referencing org.glassfish.api:api:10.0-SNAPSHOT:
<parent>
    <artifactId>api</artifactId>
    <groupId>org.glassfish.api</groupId>
    <version>10.0-SNAPSHOT</version>
 </parent>

Why? How can anyone reproduce 1.1 version of
javax.activation:activation? I won't be surprised if there are more than
one such pom.xml. I think artifact owners need to review the poms and
fix them.

I came across this when I saw these log messages while running maven
without having Internet access:
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get
dependency information: Unable to read the metadata file for artifact
'javax.activation:activation:jar': Cannot find parent:
org.glassfish.api:api for project: javax.activation:activation:jar:1.1
for project javax.activation:activation:jar:1.1
  javax.activation:activation:jar:1.1

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  glassfish-repository (http://download.java.net/maven/glassfish),
  maven2-repository.dev.java.net (http://download.java.net/maven/2/),
  java.net-m2-repository (http://download.java.net/maven/2),
  java.net-m1-repository (http://download.java.net/maven/1),
  maven-repository.dev.java.net (http://download.java.net/maven/1/)
Path to dependency:
        1) com.sun.enterprise:auto-depends-plugin:jar:0.2-SNAPSHOT
        2) com.sun.xml.bind:jaxb-xjc:jar:2.1.3
        3) com.sun.xml.bind:jaxb-impl:jar:2.1.3
        4) javax.xml.bind:jaxb-api:jar:2.1

Thanks,
Sahoo

[1]
http://download.java.net/maven/glassfish/javax/activation/activation/1.1/activation-1.1.pom