RE: Adding system scope jars to the manifest class path
> Seriously, just get over it and run a repository manager. Ok, will do :) Thanks for your help guys! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Adding system scope jars to the manifest class path
>> Sounds right; system scoped stuff are supposed to be provided by the >> JVM etc. so they shouldn't be any need for the manifest to point them out. >Also to expand a bit; if you intent to bundle those jars with your app use the default (compile) scope and if >you expect something like a servlet container to provide them instead use the provided scope. Ok, allow me to rephrase :) I'm struggling with some proprietary (IBM, Oracle, etc..) jars that I need to get added to my manifest class path. I don't want to do that manually obviously. When I add the proprietary jars to my pom and set their scope to default level, when I try to build Maven complains that it can't find the proprietary jars in any of the public repositories. I have added the jars to my local repository and correctly set the directory structure to match my pom but to no avail. So I googled and read that the way round that is to set the scope to system. But then the jars don't get added to the manifest class path anymore. So I guess my question is: how do I set it up so that Maven only looks for proprietary jars on my local repository and doesn't try to go outside and look for them? Thanks, Jonck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Adding system scope jars to the manifest class path
Hi, I'm trying to get Maven to correctly set my class path entry in the Jar manifest file. It's all working as it should except for my system scoped jars, these get excluded from the manifests class path for some reason. I have several system scoped dependencies as such: com.ibm.db2 db2jcc 1.3.1 system ${maven.home}/repository/com/ibm/db2jcc/1.3.1/db2jcc.jar But here is what the manifest.mf looks like after Maven runs, as you can see the DB2 driver is not included: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: kogeljo Build-Jdk: 1.6.0_05 Main-Class: com.completer.startup.App Class-Path: lib/spring-beans-2.5.6.jar lib/commons-logging-1.1.1.jar l ib/spring-core-2.5.6.jar lib/spring-context-2.5.6.jar lib/aopalliance -1.0.jar lib/spring-context-support-2.5.6.jar lib/spring-dao-2.0.8.ja r lib/spring-jdbc-2.5.6.jar lib/spring-tx-2.5.6.jar lib/spring-suppor t-2.0.8.jar lib/commons-dbcp-1.2.2.jar lib/commons-pool-1.3.jar lib/c ommons-beanutils-core-1.7.0.jar lib/commons-collections-2.0.jar lib/c glib-full-2.0.2.jar lib/log4j-1.2.15.jar lib/mail-1.4.jar lib/activat ion-1.1.jar Currently I have the maven-jar-plugin configured as such: org.apache.maven.plugins maven-jar-plugin com.completer.startup.App true lib/ Could someone please tell me what I'm doing wrong? Thanks, Jonck