Maven Repository for compiled eXist artifacts

---

NOTE: From eXist-db 5.0.0-RC8 onwards, Maven artifacts are now published to Maven Central instead.

This repository holds the POMs for eXist compiled artifacts. In addition it holds any dependencies which cannot themselves be retrieved from Maven Central.

Unfortunately this does not work well as a source for Nexus proxy repositiories. As an alternative Evolved Binary mainatin a public Nexus repository of eXist-db artifacts here: http://repo.evolvedbinary.com/repository/exist-db/ (and snapshots here: http://repo.evolvedbinary.com/repository/exist-db-snapshots/)

Example

To use the core of eXist in your Maven project, add the dollowing to the dependencies section of your Maven pom.xml file:

    <dependency>
      <groupId>org.exist-db</groupId>
      <artifactId>exist-core</artifactId>
      <version>5.0.0-RC7</version>
    </dependency>

You will also need to add these repository to (or create) the repositories section of your Maven pom.xml file:

    <repository>
      <id>exist-db</id>
      <url>http://repo.evolvedbinary.com/content/repositories/exist-db/</url>
      <releases><enabled>true</enabled></releases>
      <snapshots><enabled>false</enabled></snapshots>
    </repository>
    <repository>
      <id>exist-db-snapshots</id>
      <url>http://repo.evolvedbinary.com/content/repositories/exist-db-snapshots/</url>
      <releases><enabled>false</enabled></releases>
      <snapshots><enabled>true</enabled></snapshots>
    </repository>

These artifacts can also be used from Ivy, SBT or Gradle build systems.

Caveats

These artifacts are manually constructed from the output of the eXist-db Ant build process on a best effort basis.

eXist 3.0 Maven Artifacts - these are built from the Git commit id 9911af8 as the tag for eXist 3.0 is not correct!

Scripts for producing Maven Artifacts from eXist-db

1. Build the JARs and generate checksum files for them

./update.sh --output-in-place --exist-build-dir /Users/aretter/code/exist-for-release

or if you want to produce a SNAPSHOT version you can use the --snapshot flag, e.g.:

./update.sh --output-in-place --exist-build-dir /Users/aretter/code/exist-for-release --snapshot

or if you want to use a specific version name, you can use the --tag flag, e.g.:

./update.sh --output-in-place --exist-build-dir /Users/aretter/code/exist-for-release --tag 5.0.0-RC6

2. Migrate the last version of the POMs

./migrate-pom-versions.sh --build-in-place --output-in-place --from-version 5.0.0-RC5 --to-version 5.0.0-RC6

3. Make any changes to the POM files that you need to make (e.g. updating dependency versions)

4. (Optional) Upload the Release Artifacts to the remote repo:

./upload.sh --output-in-place --artifact-version 5.0.0-RC6

or if you want to upload Snapshot Artifacts to the remote repo:

./upload.sh --output-in-place --snapshot --artifact-version 5.0.0-SNAPSHOT

or if you want to install locally (perhaps because you built a snapshot):

./upload.sh --output-in-place --snapshot --local --artifact-version 20170104-SNAPSHOT

5. Upload the artifacts to GitHub

   1. Modify the README.md replacing the version numbers with the latest

   2. Add, commit and push the files to GitHub:

   git add README.md
   git add **5.0.0-RC6**
   git commit
   git push