JAR File is included in WAR File inspite of mentioning scope as provided in maven

[Naresh Shanmugam]

I was under the impression that when I make the "scope" of a "Jar" as "provided" in maven, then that would not be included in the WAR file(available only at the compile tile). Hence I mentioned scope as "provided"(JMS jar) in the pom.xml file, but I still see that jar file in the lib folder of WAR file. Does anybody know What I am missing here or is my understanding incorrect?

<dependency>
            <groupId>javax.jms</groupId>
            <artifactId>jms</artifactId>
            <version>1.1</version>
            <scope>provided</scope>
</dependency>

Thank you!!

[Tim Holloway]

Your assumption is correct. "Provided" means that the JAR in question is provided by the service container, which is true for full-stack J(2)EE servers.

Most likely, one of the following is to blame:

1. It isn't the jar you think it is. In some instances, there's an API jar that defines the standard interfaces and an implementation jar that actually provides the services themselves. So you might be pulling in an API jar from some other part of the POM and thinking it's the implementation jar.

2. You might have a complication in your build. For example, I can set up a "universal" build with different profiles in it - say one for Tomcat and one for WebSphere. Since Tomcat doesn't implement jms itself, but WebSphere does, the profile would ensure that builds for Tomcat included the jar but builds for WebSphere did not. So if you build using the wrong profile, you get unexpected consequences.

[Stephan van Hulst]

Can you post your complete POM?

[Naresh Shanmugam]

Thank you Tim and Stephan for your response.

As Tim mentioned,

It isn't the jar you think it is. In some instances, there's an API jar that defines the standard interfaces and an implementation jar that actually provides the services themselves. So you might be pulling in an API jar from some other part of the POM and thinking it's the implementation jar.

the JMS Jar that I had mentioned in my post was getting downloaded as a transitive dependency of some other dependent component. I figured this out by opening the pom.xml in STS (Dependencies Hierarchy View) that showed all the transitive dependencies.  
Since we dont have control over the external pom. We used the following code to remove that JAR file from the WAR file.

    
      <plugin>
        <artifactId>maven-war-plugin</artifactId>
        <version>3.1.0</version>
        <configuration>
          <packagingExcludes>WEB-INF/lib/JMS-*.jar</packagingExcludes>
        </configuration>
      </plugin>

I am positing this so that it would be helpful to some one else.

[Rob Spoor]

If JMS is a direct dependency of one of your dependencies you can also exclude it. For instance:
<dependency> <groupId>commons-configuration</groupId> <artifactId>commons-configuration</artifactId> <version>1.10</version> <exclusions> <exclusion> <artifactId>commons-logging</artifactId> <groupId>commons-logging</groupId> </exclusion> </exclusions> </dependency> <dependency> <artifactId>commons-logging</artifactId> <groupId>commons-logging</groupId> <version>1.2</version> </dependency>