Hi Markus,
I looked at the webdav pom file:
- you need to keep the version the same as Jersey. That way we keep
everything in sync (see later in reference to the sample).
- all other Jersey modules depend on Java SE 5. Are you using any SE
6 specific features? If so we need to make sure the
dependencies are set up correctly for that. I am no maven expert
but i not sure the compiler plugin declares such a
dependency.
- add java doc dependency. See the contribs/jersey-multpart/pom.xml
for use of the "maven-javadoc-plugin".
- observation: other Jersey modules use the com.sun.jersey package
name as the base. I have no big issue with using
"net.java.dev.jersey" for modules in contrib.
- i would prefer to keep the version of the dependent 311 module
exact, namely 1.0 rather than 1.0 plus anything else.
That we we know for sure what are depending on. Developers can of
course change this for their own projects.
For the samples pom.xml
- we need to keep the versions of dependency jersey stuff exact, and
the same as what it corresponds to for other modules. See the
helloworld/pom.xml file. Also for certain dependencies we need to
be exact e.g. Grizzly so we know what we test against. Notice the
use of ${project.version} which means you do not have to be
explicit on the version of the webdav module.
- samples are also required to be assembled as a downloadable zip
file, and require unit tests, the other samples
can be used as templates for such purposes. The unit tests for
samples actually serve as functional tests and ensure that
we do not need to manually test before we release.
Paul.