Maven Support for JE, testers needed!

Question

Hello Berkeley DB Java Edition Fans and Developers!
In an effort to better support our developers we've setup what we hope is a functional Maven repository, but we'd like you to test it and let us know if we've been successful or not. I've tried to test it, but to be perfectly honest I'm not a Maven expert. If we've done anything in a non-standard or imperfect manner please speak up and let me know so that I can fix things now.
Here is the structure, the ever important POM file is found at:
http://download.oracle.com/maven/com/sleepycat/je/<release>/je-<release>.pom
e.g.
http://download.oracle.com/maven/com/sleepycat/je/3.2.76/je-3.2.76.pom
In that directory you will find:
je-<release>.pom
je-<release>.pom.md5
je-<release>.pom.sha1
je-<release>.jar
je-<release>.jar.md5
je-<release>.jar.sha1
sources.jar
sources.jar.md5
sources.jar.sha1
Also, I've uploaded a copy of each release's documentation tree to:
http://download.oracle.com/berkeley-db/docs/je/<release>/
e.g.
http://download.oracle.com/berkeley-db/docs/je/3.2.76/
Finally, the Sleepycat Public (open source) license file for JE is located at:
http://download.oracle.com/maven/com/sleepycat/je/license.txt
I believe that if you put the following into your Ant build.xml file it will pick up the JE .jar file using Maven, let me know if this is wrong:
  <!-- Use Maven to fetch Oracle Berkeley DB Java Edition -->
  <path id="maven-ant-tasks.classpath" path="lib/maven-ant-tasks-2.0.9.jar" />
  <typedef resource="org/apache/maven/artifact/ant/antlib.xml" uri="urn:maven-artifact-ant" classpathref="maven-ant-tasks.classpath" />
  <artifact:remoteRepository id="berkeleydb-je.repository" url="http://ossus.com/maven" />
  <artifact:dependencies pathId="dependency.classpath">
    <remoteRepository refid="berkeleydb-je.repository" />
    <dependency groupId="com.sleepycat" artifactId="je" version="3.2.76"/>
  </artifact:dependencies>
--------------------------------And here is an example project POM file for those who use Maven to build their applications. Let me know if this is correct and usable or if I've made mistakes or there are ways to improve it as well.
<?xml version="1.0" encoding="ISO-8859-1"?>
<project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/maven-v4_0_0.xsd"?>
  <modelVersion>4.0.0</modelVersion>
  <dependencies>
    <dependency>
      <groupId>com.sleepycat</groupId>
      <artifactId>je</artifactId>
      <version>3.2.76</version>
    </dependency>
  </dependencies>
  <repositories>
    <repository>
      <releases>
        <enabled>false</enabled>
        <updatePolicy>always</updatePolicy>
        <checksumPolicy>warn</checksumPolicy>
      </releases>
      <snapshots>
        <enabled>true</enabled>
        <updatePolicy>never</updatePolicy>
        <checksumPolicy>fail</checksumPolicy>
      </snapshots>
      <id>oracleReleases</id>
      <name>Oracle Released Java Packages</name>
      <url>http://download.oracle.com/maven</url>
      <layout>default</layout>
    </repository>
  </repositories>
</project>
--------------------------------If one or more Maven user could give this a try it would greatly help me out.
Questions I have are:
1. Did I put the source code up in the proper place/package/name/etc?
2. Did I leave anything out of the POM?
3. Did I put too much into the POM
4. Is there some other file I need to put somewhere that tells people what the latest version is of JE (and is that something that indicates the latest version for major releases, as in the latest version of the 2.x series and then also the latest version of the 3.x series, etc.)?
5. Does this work? :)
Thanks in advance for your help,
-greg
Greg Burd | Senior Product Manager
Oracle Berkeley DB | ORACLE United States

Answer 1

Update: I changed our POM to refer to the new version, 3.3.62, and again the download, build and test was successful. So, upgrading JE versions required just a few keystrokes.
FYI, you've still got a license typo, "Sleepcyat", in both the 3.2.76 and 3.3.62 POMs.
Also, though it seems harmless, and only happens when using the m2eclipse inside-Eclipse maven build, I'm still getting the following warning on builds:
[WARN] POM for 'com.sleepycat:je:pom:3.3.62:compile' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: Unrecognised tag: 'license' (position: START_TAG seen ...</organization>\n\n <license>... @15:12)
I don't know enough about Maven to know if there's a 'higher-level' way to indicate the latest version overall, or latest within a version-prefix. I suspect people should make that determination from prose elsewhere. They might also try to determine other releasesby browsing the containing directory -- ie: http://download.oracle.com/maven/com/sleepycat/je/ -- though I see that doesn't work, only the direct URLs to the POMs and other resources answer.
Your 'sources' URLs in both POMs trigger a JAR download as I would expect, but the Javadoc URLs both generate 404s. (I'm not sure if any automated tools depend on these delivering content, as opposed to the values just being there for human reference.)
HTH -- though the main message is "it's working the way I'd expect!"
- Gordon @ IA