Paul,
> > For the sample: As it is dependend of the WebDAV support, and as
> > WebDAV support is in the contrib project (not in the overall Jersey
> > project), I do not see a chance to split the sample out into the
> > samples project -- it just won't find it's dependency to WebDAV
> > anymore, unless you manually install it into your local repository
> > before.
>
> mvn install will compile, test and install the artifacts to the local
> repo. You do not need to do it manually. Also when this moves to the
> trunk it will get built, installed and automatically deployed to the
> java.net maven repo.
Yes, I with "manually" I meant typing "mvn install" for WebDAV before doing
the same for the sample project. "Manually" because this will be done under
the hood if the sample is NOT in its own project. Anyways, as soon as this
is in trunk, this unconvenience will be solved, as WebDAV is found in the
global repository then.
> > So I think the sample cannot get splitted into its own project
> > unless WebDAV is part of Jersey itself. But maybe I am wrong?
>
> It is not an issue. It can be part of the samples just like the spring
> sample where the spring code resides on contrib as well.
Got the point. Dissolved the sample. Now it is found inside of the
jersey/samples folder, what makes the core WebDAV project much more cleaner.
Thanks for the help! :-)
Markus