Taylor Cowan wrote:
I believe this isn't related to your pom setup in the repo, things work fine with regular java builds, jar packaging, etc.... it has something to do with maven's webapp packaging, which isn't following tansitive dependencies. I'll report back when I've figured out what I'm doing wrong.
Taylor, I did not test the webapp packaging. But I think the problem is related to the dependency resolution. I would like to understand why with this pom.xml file: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>com.hp.hpl.test</groupId> <artifactId>test</artifactId> <version>0.1</version> <packaging>jar</packaging> <dependencies> <dependency> <groupId>com.hp.hpl.jena</groupId> <artifactId>sdb</artifactId> <version>1.2.0</version> </dependency> </dependencies> </project> I get this dependency tree: com.hp.hpl.test: test:jar: 0.1 \- com.hp.hpl.jena: sdb:jar:1. 2.0:compile +- com.hp.hpl.jena: arq:jar:2. 6.0:compile | +- com.hp.hpl.jena: jena:jar: 2.5.7:compile | +- org.apache.lucene: lucene-core: jar:2.3.1: compile | +- stax:stax-api: jar:1.0:compile | +- woodstox:wstx- asl:jar:3. 0.0:compile | \- com.hp.hpl.jena: json-jena: jar:1.0:compile \- com.hp.hpl.jena: arq-extra: jar:2.6.0: compile Which does not contains: +- com.hp.hpl.jena: iri:jar:0. 5:compile +- antlr:antlr: jar:2.7.5: compile +- commons-logging: commons-logging: jar:1.1.1: compile +- com.hp.hpl.jena: concurrent-jena:jar: 1.3.2:compile +- com.ibm.icu: icu4j:jar: 3.4.4:compile +- xerces:xercesImpl: jar:2.7.1: compile \- xerces:xmlParserAPI s:jar:2.0. 2:compile If, instead, I use this pom.xml file: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>com.hp.hpl.test</groupId> <artifactId>test</artifactId> <version>0.1</version> <packaging>jar</packaging> <dependencies> <dependency> <groupId>com.hp.hpl.jena</groupId> <artifactId>sdb</artifactId> <version>1.2.0</version> </dependency> <dependency> <groupId>com.hp.hpl.jena</groupId> <artifactId>jena</artifactId> <version>2.5.7</version> </dependency> </dependencies> </project> I get a dependency tree I am happy with: com.hp.hpl.test: test:jar: 0.1 +- com.hp.hpl.jena: sdb:jar:1. 2.0:compile | +- com.hp.hpl.jena: arq:jar:2. 6.0:compile | | +- org.apache.lucene: lucene-core: jar:2.3.1: compile | | +- stax:stax-api: jar:1.0:compile | | +- woodstox:wstx- asl:jar:3. 0.0:compile | | \- com.hp.hpl.jena: json-jena: jar:1.0:compile | \- com.hp.hpl.jena: arq-extra: jar:2.6.0: compile \- com.hp.hpl.jena: jena:jar: 2.5.7:compile +- com.hp.hpl.jena: iri:jar:0. 5:compile +- antlr:antlr: jar:2.7.5: compile +- commons-logging: commons-logging: jar:1.1.1: compile +- com.hp.hpl.jena: concurrent- jena:jar: 1.3.2:compile +- com.ibm.icu: icu4j:jar: 3.4.4:compile +- xerces:xercesImpl: jar:2.7.1: compile \- xerces:xmlParserAPI s:jar:2.0. 2:compile Maybe, someone on the u...@maven.apache.org mailing list can help me to understand the problem and show everyone how little I know about Maven. :-) Paolo -- Hewlett-Packard Limited - Cain Rd., Bracknell, Berks RG12 1HN, 690597 England --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
