cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Proposal: drop ant build.xml files for samples requiring extra stuff.....
Date Wed, 16 Mar 2011 03:54:16 GMT

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.


On Tuesday 15 March 2011 9:20:23 AM Daniel Kulp wrote:
> Right now, we have a samples-lib directory that contains some extra libs
> that CXF doesn't require for anything, but various samples do.   I'd like
> to go ahead and remove that directory and the build.xml for samples that
> require it. We have Maven poms for all the samples so the sample would
> still be buildable and runnable with Maven, but not with Ant.
> I see some value in keeping SOME of the samples working with Ant as not
> everyone uses Maven.   However, shipping a bunch of libs just for a couple
> of samples seems a bit silly.
> That said, a lot of projects have gone Maven only and don't provide any ant
> scripts at all.   We could also do that.      So, there are two options:
> 1) Remove ant build support entirely
> 2) Remove ant build support for some of the samples, specifically anything
> requiring extra libraries or extra ant configs and such.
> What are peoples thoughts?    I'm leaning more toward #2, but I could
> definitely be persuaded to go #1.   If we do go #1, I'd like to refactor
> the samples into the standard maven structure (src/main/[java|resources]),
> but that could be done over time as well.

Daniel Kulp
Talend -

View raw message