This is a situation where ivy configurations come in handy.

eg, your project could have two configurations: "compile" and "deploy", where "compile" extends from "deploy".

When you are building your war to deploy to tomcat, you only include the artifacts from the "deploy" configuration.

That's how I would do it, at least =).

http://ant.apache.org/ivy/history/latest-milestone/ivyfile/configurations.html


Mike Shea.

I am building an webapp and I am using ivy:cachefileset to compile and to
deploy.
Some jars are both needed for compilation and runtime others like el-api are
only needed at compile time
because Tomcat ships it allready. How can I configure this?

Thanks,
Evert


Reply via email to