2009/4/24 Glen Mazza glen.ma...@gmail.com:
It would defeat one of the main purposes of Maven if you used a different
directory layout with that tool.
+1 for this -- if you use Maven, stick with the Maven, layout
otherwise other plugins won't know where to look for things and it'll
be a
On Fri April 24 2009 3:02:14 am Andrew Clegg wrote:
2009/4/24 Glen Mazza glen.ma...@gmail.com:
It would defeat one of the main purposes of Maven if you used a different
directory layout with that tool.
+1 for this -- if you use Maven, stick with the Maven, layout
otherwise other plugins
Part of the issue is that we don't have very good archetypes for CXF yet.
Thus, using the m2eclipse plugin to create CXF projects in eclipse that
work
well with CXF doesn't work very well. We really only have a single
jaxws
code first archetype which is very minimalistic.
What we
arg to generate the
*Impl.java. It requires that it be manually dropped in
/service-war/src/main/java.
Does this require a second invocation of wsdl2java using a different
target
dir when the -ipml arg is used?
-Bruce
--
View this message in context:
http://www.nabble.com/packaging
Tn Tue, Apr 21, 2009 at 8:28 AM, Andrew Clegg and...@nervechannel.comwrote:
One of Glen's excellent tutorials covers packaging and deploying using
both Maven and Ant:
http://www.jroller.com/gmazza/date/20080417
This example creates a different directory structure than the cxf plugin top
this message in context:
http://www.nabble.com/packaging-question-tp23158012p23207733.html
Sent from the cxf-user mailing list archive at Nabble.com.
Apologies, some rookie questions here.
What's the minimum env I need to run cxf and how should it be packaged up
along with the java code for deployment on jetty (or tomcat)?
Any implications to cxf servelet vs spring?
Is there anything smaller, and if so, what do I lose?
Specific RTFM
