OK so back up. First, leave the dependency out of A and run "mvn clean package". Set that jar file aside (rename it and move it out of target or clean will remove it.)
Now add the dependency and run "mvn clean package". Set that jar file aside like you did before. Now use some tool to unzip both and compare the contents. Surely there is a difference you simply have not accounted for yet. Wayne On Wed, Jul 11, 2012 at 1:34 PM, Amir Gheibi <aghe...@fmep.ag.gov.bc.ca> wrote: > Here is A's Manifest entry which as I mentioned, is identical in both > scenarios. > > Manifest-Version: 1.0 > Built-By: bm03043 > Build-Jdk: 1.6.0_18 > Created-By: Apache Maven 3.0.4 > Archiver-Version: Plexus Archiver > Extension-List: entities > entities-Extension-Name: com.xxx.entities > > -----Original Message----- > From: Wayne Fay [mailto:wayne...@gmail.com] > Sent: July-11-12 11:13 AM > To: Maven Users List > Subject: Re: Dependency entry changes runtime > >> Runtime environment is a "Weblogic 10.3.3" in which "B" is registered as an >> Optional Package (Library) and there is an extension entry in A's MANIFEST >> that refers to it (that's how A finds B in runtime). >> >> I compared A's JAR file in both scenarios and I don't see any difference >> whatsoever except the POM file within the Maven directory, which as far as I >> understand, doesn't have any effect on runtime. >> >> Why would the dependency entry change runtime behavior? > > Didn't you already answer your own question? The answer is the > MANIFEST entry. If you check, the MANIFEST entry will (should) only > appear when the dependency is added with runtime scope. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
