[Exist-open] Exist in Maven Projects

[Gregory K. <gk...@gm...>]

Everybody,

I'm making a webapp in which I'd like to run the exist servlet.  Like
all of my java projects, I'd like to do the build with maven.  Since
this is a custom application, I don't want to include any of the exist
samples, or anything like that.  I want to start with fairly clean
base.  To do this with Maven, I see two options.

1) Declare the war as a dependency and explicitly exclude everything
that I don't want when it does the overlay.

This is probably the simplest way to go about it, but I see a few
disadvantages.  The first is that any changes to the examples or
anything could cause random files to show up in my war because the
excludes might not catch them.  The second is that because the war
overlay would pull jars into the lib directory, I might end up with
multiple versions of a jar.  For those reasons, I don't see the war
dependency as being a good, long-term option.

2) Declare each of the exist jars as a dependency and setup the
web.xml to look like the one in the default exist.war.

This method is a bit more effort, but I think that it has some
potential.  Essentially, it would just be a project that creates
something similar to exist.war but be built by maven.  The one thing
blocking this is that exist jars aren't in the maven repository and
the dependencies of each jar is not well-known.

Somebody might remember that I actually created poms for the exist
jars for 1.1rc-newcore a while back, but I don't know how accurate
they are anymore.  Also, they're woefully incomplete when it comes to
non-dependency metadata.  I don't have scm, issue tracking, developer
info, etc. listed.

If anybody's interested, I'd love to donate what I have and help with
getting the poms created, updated and deployed into the central
repository.  I also have an archetype that generates a skeleton
exist.war for rapid creation of new webapps.

Looking forward to comments,

Gregory Kick
gk...@gm...