You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Harsch, Timothy J. (ARC-SC)[LOCKHEED MARTIN SPACE OPNS]" <ti...@nasa.gov> on 2008/09/15 01:00:36 UTC
Exclusions not working?
Hi All,
What can I do when I have a transitive dependency problem? In
this case I have a very simple project that includes only log4j 1.2.15
and jxl 2.6.3 ( which requires log4j 1.2.14 ). The effect I'm seeing is
that the app compiles and runs fine, but log4j silently stops working.
All calls print nothing to the console. The manual suggests using
exclusions, which I've tried to no avail )(see below). Maven
dependency:tree will report there is no longer a conflict, but the app
behavior is still a problem. Is there something else I should try?
Thanks,
Tim
PS This same behavior happens between log4j and Jena.
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
</dependency>
<dependency>
<groupId>net.sourceforge.jexcelapi</groupId>
<artifactId>jxl</artifactId>
<version>2.6.3</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
RE: Exclusions not working?
Posted by "Harsch, Timothy J. (ARC-SC)[LOCKHEED MARTIN SPACE OPNS]" <ti...@nasa.gov>.
For those interested. I've determined this has nothing to do with
Maven. Even a non-Maven project has conflicts between log4j and jxl
API. Looking in JXL API it looks as if they are extending log4j
classes. I have no idea why... but it is likely causing the problem.
Tim
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Sunday, September 14, 2008 9:48 PM
To: Maven Users List
Subject: Re: Exclusions not working?
so you said, even with depepdencyManagement, log4j 1.2.14 still show up?
It sounds like bug
-D
On Sun, Sep 14, 2008 at 9:10 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
> Hi,
> Thanks for taking the time to respond. Yes, that is the way I
> understand <dependancyManagement> to work as well. I don't think any
of
> that helps me here though as I have only a parent pom. I have attached
> an m2eclipse project that shows my exact problem. Hopefully the list
> server doesn't block it out, I've named the file ltest.piz to get past
> attachment scanners, rename to .zip.
>
> Here's the contents of the full pom just in case.
>
> <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>ltest</groupId>
> <artifactId>ltest</artifactId>
> <packaging>jar</packaging>
> <version>0.0.1-SNAPSHOT</version>
> <name>ltest</name>
> <url>http://maven.apache.org</url>
> <dependencies>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> </dependency>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.4</version>
> <scope>test</scope>
> </dependency>
> <!-- Uncomment below to see log4j stop working -->
> <!-- <dependency>
> <groupId>net.sourceforge.jexcelapi</groupId>
> <artifactId>jxl</artifactId>
> <version>2.6.3</version>
> </dependency>
> -->
> <!-- Tried placing this in jxl artifact
> <exclusions> <exclusion>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> </exclusion> </exclusions>
> -->
> </dependencies>
> <!--
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> </dependency>
> </dependencies>
> </dependencyManagement>
> -->
> <build>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <source>1.6</source>
> <target>1.6</target>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
>
>
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Sunday, September 14, 2008 8:00 PM
> To: Maven Users List
> Subject: Re: Exclusions not working?
>
> if you defined log4j version in dependencyManagement at the top pom,
> the sub poms will use that version, just make sure dont specify the
> version in sub pom 's dependency
>
> -D
>
> On Sun, Sep 14, 2008 at 7:36 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
> MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
>> Hi,
>> Thanks for the response. If your referring to <dependencyManagement>
> in
>> the parent pom, I did try that I was working this problem in my mondo
>> app. In this case I have boiled it down to first principles, the
>> project is quite simple as it only has the two projects in the mix.
> So,
>> in this case, I don't see how it would help, as all
>> <dependencyManagement> really does is prescribe the version for any
>> child pom's via inheritance. This pom has versions prescribed for
> both
>> projects. If you are thinking it would help in some other way,
please
>> elaborate.
>>
>> Thanks again,
>> Tim
>>
>> -----Original Message-----
>> From: Dan Tran [mailto:dantran@gmail.com]
>> Sent: Sunday, September 14, 2008 5:19 PM
>> To: Maven Users List
>> Subject: Re: Exclusions not working?
>>
>> Use dependencyManagement.
>>
>> -D
>>
>> On Sun, Sep 14, 2008 at 4:00 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
>> MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
>>> Hi All,
>>>
>>> What can I do when I have a transitive dependency problem? In
>>> this case I have a very simple project that includes only log4j
> 1.2.15
>>> and jxl 2.6.3 ( which requires log4j 1.2.14 ). The effect I'm
seeing
>> is
>>> that the app compiles and runs fine, but log4j silently stops
> working.
>>> All calls print nothing to the console. The manual suggests using
>>> exclusions, which I've tried to no avail )(see below). Maven
>>> dependency:tree will report there is no longer a conflict, but the
> app
>>> behavior is still a problem. Is there something else I should try?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Tim
>>>
>>>
>>>
>>> PS This same behavior happens between log4j and Jena.
>>>
>>>
>>>
>>> <dependencies>
>>>
>>> <dependency>
>>>
>>> <groupId>log4j</groupId>
>>>
>>> <artifactId>log4j</artifactId>
>>>
>>> <version>1.2.15</version>
>>>
>>> </dependency>
>>>
>>> <dependency>
>>>
>>> <groupId>net.sourceforge.jexcelapi</groupId>
>>>
>>> <artifactId>jxl</artifactId>
>>>
>>> <version>2.6.3</version>
>>>
>>> <exclusions>
>>>
>>> <exclusion>
>>>
>>> <groupId>log4j</groupId>
>>>
>>> <artifactId>log4j</artifactId>
>>>
>>> </exclusion>
>>>
>>> </exclusions>
>>>
>>> </dependency>
>>>
>>> </dependencies>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Exclusions not working?
Posted by Dan Tran <da...@gmail.com>.
so you said, even with depepdencyManagement, log4j 1.2.14 still show up?
It sounds like bug
-D
On Sun, Sep 14, 2008 at 9:10 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
> Hi,
> Thanks for taking the time to respond. Yes, that is the way I
> understand <dependancyManagement> to work as well. I don't think any of
> that helps me here though as I have only a parent pom. I have attached
> an m2eclipse project that shows my exact problem. Hopefully the list
> server doesn't block it out, I've named the file ltest.piz to get past
> attachment scanners, rename to .zip.
>
> Here's the contents of the full pom just in case.
>
> <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>ltest</groupId>
> <artifactId>ltest</artifactId>
> <packaging>jar</packaging>
> <version>0.0.1-SNAPSHOT</version>
> <name>ltest</name>
> <url>http://maven.apache.org</url>
> <dependencies>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> </dependency>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.4</version>
> <scope>test</scope>
> </dependency>
> <!-- Uncomment below to see log4j stop working -->
> <!-- <dependency>
> <groupId>net.sourceforge.jexcelapi</groupId>
> <artifactId>jxl</artifactId>
> <version>2.6.3</version>
> </dependency>
> -->
> <!-- Tried placing this in jxl artifact
> <exclusions> <exclusion>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> </exclusion> </exclusions>
> -->
> </dependencies>
> <!--
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> </dependency>
> </dependencies>
> </dependencyManagement>
> -->
> <build>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <source>1.6</source>
> <target>1.6</target>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
>
>
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Sunday, September 14, 2008 8:00 PM
> To: Maven Users List
> Subject: Re: Exclusions not working?
>
> if you defined log4j version in dependencyManagement at the top pom,
> the sub poms will use that version, just make sure dont specify the
> version in sub pom 's dependency
>
> -D
>
> On Sun, Sep 14, 2008 at 7:36 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
> MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
>> Hi,
>> Thanks for the response. If your referring to <dependencyManagement>
> in
>> the parent pom, I did try that I was working this problem in my mondo
>> app. In this case I have boiled it down to first principles, the
>> project is quite simple as it only has the two projects in the mix.
> So,
>> in this case, I don't see how it would help, as all
>> <dependencyManagement> really does is prescribe the version for any
>> child pom's via inheritance. This pom has versions prescribed for
> both
>> projects. If you are thinking it would help in some other way, please
>> elaborate.
>>
>> Thanks again,
>> Tim
>>
>> -----Original Message-----
>> From: Dan Tran [mailto:dantran@gmail.com]
>> Sent: Sunday, September 14, 2008 5:19 PM
>> To: Maven Users List
>> Subject: Re: Exclusions not working?
>>
>> Use dependencyManagement.
>>
>> -D
>>
>> On Sun, Sep 14, 2008 at 4:00 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
>> MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
>>> Hi All,
>>>
>>> What can I do when I have a transitive dependency problem? In
>>> this case I have a very simple project that includes only log4j
> 1.2.15
>>> and jxl 2.6.3 ( which requires log4j 1.2.14 ). The effect I'm seeing
>> is
>>> that the app compiles and runs fine, but log4j silently stops
> working.
>>> All calls print nothing to the console. The manual suggests using
>>> exclusions, which I've tried to no avail )(see below). Maven
>>> dependency:tree will report there is no longer a conflict, but the
> app
>>> behavior is still a problem. Is there something else I should try?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Tim
>>>
>>>
>>>
>>> PS This same behavior happens between log4j and Jena.
>>>
>>>
>>>
>>> <dependencies>
>>>
>>> <dependency>
>>>
>>> <groupId>log4j</groupId>
>>>
>>> <artifactId>log4j</artifactId>
>>>
>>> <version>1.2.15</version>
>>>
>>> </dependency>
>>>
>>> <dependency>
>>>
>>> <groupId>net.sourceforge.jexcelapi</groupId>
>>>
>>> <artifactId>jxl</artifactId>
>>>
>>> <version>2.6.3</version>
>>>
>>> <exclusions>
>>>
>>> <exclusion>
>>>
>>> <groupId>log4j</groupId>
>>>
>>> <artifactId>log4j</artifactId>
>>>
>>> </exclusion>
>>>
>>> </exclusions>
>>>
>>> </dependency>
>>>
>>> </dependencies>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Exclusions not working?
Posted by "Harsch, Timothy J. (ARC-SC)[LOCKHEED MARTIN SPACE OPNS]" <ti...@nasa.gov>.
Hi,
Thanks for taking the time to respond. Yes, that is the way I
understand <dependancyManagement> to work as well. I don't think any of
that helps me here though as I have only a parent pom. I have attached
an m2eclipse project that shows my exact problem. Hopefully the list
server doesn't block it out, I've named the file ltest.piz to get past
attachment scanners, rename to .zip.
Here's the contents of the full pom just in case.
<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>ltest</groupId>
<artifactId>ltest</artifactId>
<packaging>jar</packaging>
<version>0.0.1-SNAPSHOT</version>
<name>ltest</name>
<url>http://maven.apache.org</url>
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.4</version>
<scope>test</scope>
</dependency>
<!-- Uncomment below to see log4j stop working -->
<!-- <dependency>
<groupId>net.sourceforge.jexcelapi</groupId>
<artifactId>jxl</artifactId>
<version>2.6.3</version>
</dependency>
-->
<!-- Tried placing this in jxl artifact
<exclusions> <exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion> </exclusions>
-->
</dependencies>
<!--
<dependencyManagement>
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
</dependency>
</dependencies>
</dependencyManagement>
-->
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
</plugins>
</build>
</project>
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Sunday, September 14, 2008 8:00 PM
To: Maven Users List
Subject: Re: Exclusions not working?
if you defined log4j version in dependencyManagement at the top pom,
the sub poms will use that version, just make sure dont specify the
version in sub pom 's dependency
-D
On Sun, Sep 14, 2008 at 7:36 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
> Hi,
> Thanks for the response. If your referring to <dependencyManagement>
in
> the parent pom, I did try that I was working this problem in my mondo
> app. In this case I have boiled it down to first principles, the
> project is quite simple as it only has the two projects in the mix.
So,
> in this case, I don't see how it would help, as all
> <dependencyManagement> really does is prescribe the version for any
> child pom's via inheritance. This pom has versions prescribed for
both
> projects. If you are thinking it would help in some other way, please
> elaborate.
>
> Thanks again,
> Tim
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Sunday, September 14, 2008 5:19 PM
> To: Maven Users List
> Subject: Re: Exclusions not working?
>
> Use dependencyManagement.
>
> -D
>
> On Sun, Sep 14, 2008 at 4:00 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
> MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
>> Hi All,
>>
>> What can I do when I have a transitive dependency problem? In
>> this case I have a very simple project that includes only log4j
1.2.15
>> and jxl 2.6.3 ( which requires log4j 1.2.14 ). The effect I'm seeing
> is
>> that the app compiles and runs fine, but log4j silently stops
working.
>> All calls print nothing to the console. The manual suggests using
>> exclusions, which I've tried to no avail )(see below). Maven
>> dependency:tree will report there is no longer a conflict, but the
app
>> behavior is still a problem. Is there something else I should try?
>>
>>
>>
>> Thanks,
>>
>> Tim
>>
>>
>>
>> PS This same behavior happens between log4j and Jena.
>>
>>
>>
>> <dependencies>
>>
>> <dependency>
>>
>> <groupId>log4j</groupId>
>>
>> <artifactId>log4j</artifactId>
>>
>> <version>1.2.15</version>
>>
>> </dependency>
>>
>> <dependency>
>>
>> <groupId>net.sourceforge.jexcelapi</groupId>
>>
>> <artifactId>jxl</artifactId>
>>
>> <version>2.6.3</version>
>>
>> <exclusions>
>>
>> <exclusion>
>>
>> <groupId>log4j</groupId>
>>
>> <artifactId>log4j</artifactId>
>>
>> </exclusion>
>>
>> </exclusions>
>>
>> </dependency>
>>
>> </dependencies>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Exclusions not working?
Posted by Dan Tran <da...@gmail.com>.
if you defined log4j version in dependencyManagement at the top pom,
the sub poms will use that version, just make sure dont specify the
version in sub pom 's dependency
-D
On Sun, Sep 14, 2008 at 7:36 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
> Hi,
> Thanks for the response. If your referring to <dependencyManagement> in
> the parent pom, I did try that I was working this problem in my mondo
> app. In this case I have boiled it down to first principles, the
> project is quite simple as it only has the two projects in the mix. So,
> in this case, I don't see how it would help, as all
> <dependencyManagement> really does is prescribe the version for any
> child pom's via inheritance. This pom has versions prescribed for both
> projects. If you are thinking it would help in some other way, please
> elaborate.
>
> Thanks again,
> Tim
>
> -----Original Message-----
> From: Dan Tran [mailto:dantran@gmail.com]
> Sent: Sunday, September 14, 2008 5:19 PM
> To: Maven Users List
> Subject: Re: Exclusions not working?
>
> Use dependencyManagement.
>
> -D
>
> On Sun, Sep 14, 2008 at 4:00 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
> MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
>> Hi All,
>>
>> What can I do when I have a transitive dependency problem? In
>> this case I have a very simple project that includes only log4j 1.2.15
>> and jxl 2.6.3 ( which requires log4j 1.2.14 ). The effect I'm seeing
> is
>> that the app compiles and runs fine, but log4j silently stops working.
>> All calls print nothing to the console. The manual suggests using
>> exclusions, which I've tried to no avail )(see below). Maven
>> dependency:tree will report there is no longer a conflict, but the app
>> behavior is still a problem. Is there something else I should try?
>>
>>
>>
>> Thanks,
>>
>> Tim
>>
>>
>>
>> PS This same behavior happens between log4j and Jena.
>>
>>
>>
>> <dependencies>
>>
>> <dependency>
>>
>> <groupId>log4j</groupId>
>>
>> <artifactId>log4j</artifactId>
>>
>> <version>1.2.15</version>
>>
>> </dependency>
>>
>> <dependency>
>>
>> <groupId>net.sourceforge.jexcelapi</groupId>
>>
>> <artifactId>jxl</artifactId>
>>
>> <version>2.6.3</version>
>>
>> <exclusions>
>>
>> <exclusion>
>>
>> <groupId>log4j</groupId>
>>
>> <artifactId>log4j</artifactId>
>>
>> </exclusion>
>>
>> </exclusions>
>>
>> </dependency>
>>
>> </dependencies>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Exclusions not working?
Posted by "Harsch, Timothy J. (ARC-SC)[LOCKHEED MARTIN SPACE OPNS]" <ti...@nasa.gov>.
Hi,
Thanks for the response. If your referring to <dependencyManagement> in
the parent pom, I did try that I was working this problem in my mondo
app. In this case I have boiled it down to first principles, the
project is quite simple as it only has the two projects in the mix. So,
in this case, I don't see how it would help, as all
<dependencyManagement> really does is prescribe the version for any
child pom's via inheritance. This pom has versions prescribed for both
projects. If you are thinking it would help in some other way, please
elaborate.
Thanks again,
Tim
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Sunday, September 14, 2008 5:19 PM
To: Maven Users List
Subject: Re: Exclusions not working?
Use dependencyManagement.
-D
On Sun, Sep 14, 2008 at 4:00 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
> Hi All,
>
> What can I do when I have a transitive dependency problem? In
> this case I have a very simple project that includes only log4j 1.2.15
> and jxl 2.6.3 ( which requires log4j 1.2.14 ). The effect I'm seeing
is
> that the app compiles and runs fine, but log4j silently stops working.
> All calls print nothing to the console. The manual suggests using
> exclusions, which I've tried to no avail )(see below). Maven
> dependency:tree will report there is no longer a conflict, but the app
> behavior is still a problem. Is there something else I should try?
>
>
>
> Thanks,
>
> Tim
>
>
>
> PS This same behavior happens between log4j and Jena.
>
>
>
> <dependencies>
>
> <dependency>
>
> <groupId>log4j</groupId>
>
> <artifactId>log4j</artifactId>
>
> <version>1.2.15</version>
>
> </dependency>
>
> <dependency>
>
> <groupId>net.sourceforge.jexcelapi</groupId>
>
> <artifactId>jxl</artifactId>
>
> <version>2.6.3</version>
>
> <exclusions>
>
> <exclusion>
>
> <groupId>log4j</groupId>
>
> <artifactId>log4j</artifactId>
>
> </exclusion>
>
> </exclusions>
>
> </dependency>
>
> </dependencies>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Exclusions not working?
Posted by Dan Tran <da...@gmail.com>.
Use dependencyManagement.
-D
On Sun, Sep 14, 2008 at 4:00 PM, Harsch, Timothy J. (ARC-SC)[LOCKHEED
MARTIN SPACE OPNS] <ti...@nasa.gov> wrote:
> Hi All,
>
> What can I do when I have a transitive dependency problem? In
> this case I have a very simple project that includes only log4j 1.2.15
> and jxl 2.6.3 ( which requires log4j 1.2.14 ). The effect I'm seeing is
> that the app compiles and runs fine, but log4j silently stops working.
> All calls print nothing to the console. The manual suggests using
> exclusions, which I've tried to no avail )(see below). Maven
> dependency:tree will report there is no longer a conflict, but the app
> behavior is still a problem. Is there something else I should try?
>
>
>
> Thanks,
>
> Tim
>
>
>
> PS This same behavior happens between log4j and Jena.
>
>
>
> <dependencies>
>
> <dependency>
>
> <groupId>log4j</groupId>
>
> <artifactId>log4j</artifactId>
>
> <version>1.2.15</version>
>
> </dependency>
>
> <dependency>
>
> <groupId>net.sourceforge.jexcelapi</groupId>
>
> <artifactId>jxl</artifactId>
>
> <version>2.6.3</version>
>
> <exclusions>
>
> <exclusion>
>
> <groupId>log4j</groupId>
>
> <artifactId>log4j</artifactId>
>
> </exclusion>
>
> </exclusions>
>
> </dependency>
>
> </dependencies>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org