[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.technology.iam] Re: Are dependency exclusions honoured by IAM?
|
- From: amuino@xxxxxxxxx (Abel Muiño)
- Date: Mon, 25 May 2009 17:26:27 +0000 (UTC)
- Newsgroups: eclipse.technology.iam
- Organization: Eclipse
- User-agent: NewsPortal/0.36 (http://florian-amrhein.de/newsportal)
Hello Ben,
BenH wrote:
Im expected that by using the exclusion below, it should prevent artefact
"selenium.server" from being pulled into the project dependencies
("selenium.server" has got problems in its POM, you see).
But it remains, and "Analyze Dependencies" says that its there due to
"org.openqa.selenium.client-drivers", ie this dependency.
Is exclusion is not working, or not implemented?
Eclipse IAM delegates on the Maven Embedder to calculate dependencies (and
exclusions).
By some reason, the version we use is not properly handling your exclusion.
A workaround is to add the exclusion in the dependency management section
of the pom (or a parent pom). Like this:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.openqa.selenium.client-drivers</groupId>
<artifactId>selenium-java-client-driver</artifactId>
<version>1.0-beta-1</version>
<exclusions>
<exclusion>
<groupId>org.openqa.selenium.server</groupId>
<artifactId>selenium-server</artifactId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
</dependencyManagement>
You can then remove the <exclusions> from the <dependency>.
Hope this helps!
<dependency>
<groupId>org.openqa.selenium.client-drivers</groupId>
<artifactId>selenium-java-client-driver</artifactId>
<version>1.0-beta-1</version>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>org.openqa.selenium.server</groupId>
<artifactId>selenium.server</artifactId>
</exclusion>
</exclusions>
</dependency>
-Ben
--
Abel Muiño