On Fri April 24 2009 3:02:14 am Andrew Clegg wrote: > 2009/4/24 Glen Mazza <[email protected]>: > > 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 nightmare of extra configuration...
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 really need is someone to create and submit a couple simple sample maven projects that show the various ways to "get started" and then get them converted to archetypes that would be usable with m2eclipse. That and the WTP/STP eclipse tooling should then integrate with the m2eclipse stuff so it all works together seamlessly and consistently, but we kind of need the archetypes first. Any takers? -- Daniel Kulp [email protected] http://www.dankulp.com/blog
