Hi Glen
Am 15.02.12 13:41, schrieb Glen Mazza:
> Good to hear. Have you looked into Mavenizing your projects (like the
> Jersey samples) -- that way you won't have to worry nearly as much about
> missing JARs.
What do You mean by Mavenizing? My project is already a Maven project. I
only do Maven projects. I don't like working with Java building all by
hand ;)
> The Maven samples don't need to mention individual
> dependencies because they are defined in the contract (the pom.xml) and
That's also why I use Maven. But all examples I found in the web does
not have a Maven dependency on jersey-servlet. They only depend on
jersery-server and some on jersey-json (if they use the JSON stuff). In
the example You gave me
(
http://java.net/projects/jersey/sources/svn/content/trunk/jersey/samples/simple-servlet/pom.xml?rev=4816)
I can't see a jersey-servlet dependency. You say "they are defined in
the contract (the pom.xml)" so there need to be this dependency, or not?
I'm confused.
> viewable via mvn dependency:list or mvn dependency:tree.
Ahh, cool. New commaneds learend :)
-Sven