you are right, there are no maven artifacts for DBAccess. Unilt now, no-one has been asking for them. Please open a bug with the feature request for tracking .
There are also some questions concerning the type/structure of the artifact(s):
DBAccess uses tycho to build the project. As a result, DBAccess offers a separate p2 "feature" for each supported database platform. Should this translate into separate maven artifacts (with individual GAVs)?
What is the best way to produce these artifacts? Running "mvn install" on the DBAccess project results in nearly 20 artifacts in my local .m2 repository.
For the 1.1 Milestone releases I have been experimenting with staying at the SNAPSHOT version in the poms, so you get the appended timestamps for the resulting plugins and features. This is less effort and avoids sorting issues. It is not a problem as long as people use the p2 update site. For a maven repository, you presumably do not want a SNAPSHOT version?
Thanks for the quick answer! I will try to integrate Milestone 4 in my build and will post the result here.
I see that the milestones are published to . Is the plan to merge this repo to the shared Gemini maven repo  when the final version is released ? If yes, why use a separate repo ?
Are there plans to use Eclipse's Nexus repo  at some point ?
Sorry for the many questions, I'd just want to make sure I understand Gemeini's approach, that will help making our builds resilient to changes.
You are right: As soon as Gemini DBAccess 1.1 is released, it will be available in the Gemini repository .
The Nexus repository at Eclipse  is still work in progress. On its wiki page  it is described as "prototype undergoing creation". Gemini does not (yet) have plans to offer its artifacts there. But it is certainly worth at thought.
Thanks for the follow-up Juergen, I appreciate the effort in sorting this through.
The reasons mentioned in the blog post "Why Putting Repositories in your POMs is a Bad Idea"  referenced by Jesse McConnell are precisely why I asked about the possibility of a shared repository in the first place. I'd like to rely on as few 3d party repos (i.e. non-Central) as possible.
FYI, from my own perspective as a user:
- Ideally, the released bundles would be available from Maven Central. Sonatype's OSS repository hosting really helps.
- If not possible, I'm OK with referencing a single stable Gemini repo - I understand Eclipse's Nexus instance is a work in progress
- I'm not fond of having separate repos for milestones (and I don't really undertand the rationale, maybe it's linked with Gemini's own release/build process) -- but I will certainly not use milestones in production anyway.