Filter unmanaged dependencies that are statically included in /lib

[poornerd]

I have a few IBM Websphere Jars that are needed at compile time, but I want to exclude them from the WAR. I am not including them with sbt as artifacts because I needed to copy them from the WAS installation.

I can't figure out how to exclude them, because they don't seem to be recognized as artifacts. (should they be?)

What is the best way to do this aside from removing them from the finished WAR file with an ant script?

[yanns]

If the libs are recognized as artifacts, you can exclude them from the war with https://github.com/play2war/play2-war-plugin/wiki/Play2War-configuration#artifacts-to-filter-out-from-war

The question is why are these libs not recognized. Are they kind of special? (I mean apart from being from IBM... ;)

Another solution would be to mark these libs as "provided".

[poornerd]

I have included these jars in my projects /lib directory (unmanaged dependencies - http://www.playframework.com/documentation/2.0/Anatomy ). How would I mark them as "provided"? They are not referenced as dependencies in the build.sbt .

Also, I don't want to add it to a local Maven repository, because that makes it more complicated for others in team to compile.

[dlecan]

How would I mark them as "provided"?

I think you can't. These artifacts must be filtered by their name. So we can image a new configuration key:

• Name: Play2WarKeys.filteredUnmanagedDependencies
• Value: Seq[String]

Each dependency whose name is found in filteredUnmanagedDependencies won't be packaged in the WAR file.

Do you need that for Play2War 1.2 or 1.3 ?

[poornerd]

I need it for 1.2