Christian,
At one point, if you do a full "distribution" build, the common_build.xml in
the src/main/release/sample detected that and then the ant builds would start
working in the src/main/release/samples dir. Thus, it kind of allows
building/testing sample in the src tree, but you do have
My WSDL-first example provides both a Maven- and an Ant-way to create the
project (See Step #3). The Ant script closely follows the Maven standard
directory layout and can be used interchangably with the Maven pom files.
It's also in beautifully fluent, error-free German for you:
http://www.
Problem solved (hope there weren't too many people on this issue).
The problems was that my service was based on existing classes but only
partially --> my service didn't keep the part that close the
connection/entityManager...
My bad,
superk888 wrote:
>
> Hi everyone,
>
> Here's the proble
Hi Eamonn,
thanks for the info. I could perhaps define my own goal to not interfere
with the normal install process. There is even a copy-dependencies
plugin for maven that would copy all dependencies. The problem though is
that the install process of distribution already seems to copy certain
Hi Christian
for part 1 of the issue could you do something like this to your pom.xml to
copy the libs prior to building/running the demo.
maven-antrun-plugin
copylibs
install
Hi,
I currently try to create a new wsdl first example in response to a long
standing jira issue. (https://issues.apache.org/jira/browse/CXF-52)
The example already works quite well with maven. I can simply define the
dependencies in the pom and also directly test from the checkout folder.
