Sounds good. My WSDL-first tutorial shows how Ant can be used (http://www.jroller.com/gmazza/entry/web_service_tutorial), I can incorporate that into a new CXF sample (I've been meaning to rip out the Ant from that tutorial anyway), or we can leverage the Ant scripts in the simple wsdl-first and java-first examples for a new sample.
In the interim, until we have this "antbuild", we could remove Ant from all the samples except the two simplest (intro wsdl-first and java-first) samples. Alternatively, we can skip doing "antbuild" and just retain the Ant scripts for just these two newbie samples, for anything past that the user will need to work with Maven. I think I would have a slight preference for "antbuild" though as it would allow us to more thoroughly document how to use Ant without being distracted about needing to also teach web services (the main role of the two newbie samples), but either way is good IMO. Glen Daniel Kulp wrote: > > There's another option I just thought of: > > Remove all the ant things from all the CURRENT samples. Then add a single > "antbuild" sample that is pretty much just "hello world", but would show > how > to setup wsdl2java and such from within ant. That limits the ant > exposure to > a single, dedicated sample. That could probably cover Eric's and my > concern > about people that DO want to use ant, but pretty much keeps it away from > the > examples that we maintain and promote. > > Dan > -- View this message in context: http://cxf.547215.n5.nabble.com/Proposal-drop-ant-build-xml-files-for-samples-requiring-extra-stuff-tp3704042p3776811.html Sent from the cxf-dev mailing list archive at Nabble.com.
