In this case you can perhaps use the following maven plugin.
It copies all jars you depend on into a folder target/lib. This is
probably what you need to build your war file the old way.
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>dependency-maven-plugin</artifactId>
<executions>
<execution>
<id>copy-dependencies</id>
<phase>package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/lib</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
Greetings
Christian
Steve Cohen schrieb:
Yeah, that's where I'm at.
1) in a BIG company with a Dilbert-style "Productivity Prevention
Department" :-)
2) on the other hand, in a small, practically invisible backwaterish
part of the BIG company so that there is nothing like an SCM team,
application not deployed in data center, etc.
3) Preexisting product with preexisting handbuilt war including some
VERY nonstandard proprietary jars and shared libraries that have to be
included.
4) Deadlines
The chances of rewriting the build process anytime soon to use Maven
in this context are next to nil, notwithstanding the value that Maven
nonetheless would undoubtedly provide.
But, since the advantages of using CXF here are great, my temporary
solution is going to have to be
* build the test project my vendor has supplied me with maven,
* transfer the jars maven downloads for me to another location
* build the new war incorporating the old stuff and the now stuff
It would be nice to port the whole mess to Maven but I don't have the
time for it now.
--
Christian Schneider
---
http://www.liquid-reality.de
