If you are using the maven-war-plugin, you can use the warSourceExcludes
elements to exclude jars from your war. They will still appear in the work
directory (where the war is assembled) but once your war is bundled up, they
won't be there. You should also look at dependentWarExcludes.
Where did you define ${app.name} at?
On 10/16/06, Zarar Siddiqi [EMAIL PROTECTED] wrote:
If you are using the maven-war-plugin, you can use the
warSourceExcludes
elements to exclude jars from your war. They will still appear in the
work
directory (where the war is assembled) but once your
How is that relevant to the problem? It's defined in a property file which
I read in through a plugin and then store them as project properties. A
different propertly file is read for different environments (development,
production etc).
Mick Knutson-4 wrote:
Where did you define
it was not relevant. I am just trying to find better ways to manage the
build maintenance process for items like names and version numbers that can
be easy for a muilti-module project.
On 10/16/06, Zarar Siddiqi [EMAIL PROTECTED] wrote:
How is that relevant to the problem? It's defined in a
Hi,
Dmystery wrote:
IS there a way to turn off transitive dependencies while packaging a war
file?
I want my ejb-client in the war-packaging but it brings along all the
ejb-client dependencies. I've searched enough on this forum but cant find
a solution.
My webapp pom has a dependency
Thanks! I was not aware of the warSourceExcludes
But, wont it be great to just turn-off the t-dependency by a
transitive/transitive element.
dependency
groupIdcom-server/groupId
artifactIdcom-server-ejb/artifactId
version1/version
typeejb-client/type
