You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Paolo Castagna (JIRA)" <ji...@apache.org> on 2010/03/21 09:25:27 UTC
[jira] Created: (ZOOKEEPER-721) No set for log4j
dependency in the generated pom.xml
No <exclusions> set for log4j dependency in the generated pom.xml
-----------------------------------------------------------------
Key: ZOOKEEPER-721
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-721
Project: Zookeeper
Issue Type: Improvement
Components: build
Affects Versions: 3.0.0, 3.3.1
Reporter: Paolo Castagna
Priority: Minor
The generated Maven pom.xml file contains:
{code}
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
<scope>compile</scope>
</dependency>
{code}
It would be better to have:
{code}
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
<scope>compile</scope>
<exclusions>
<exclusion>
<groupId>javax.jms</groupId>
<artifactId>jms</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jdmk</groupId>
<artifactId>jmxtools</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.jmx</groupId>
<artifactId>jmxri</artifactId>
</exclusion>
<exclusion>
<groupId>javax.mail</groupId>
<artifactId>mail</artifactId>
</exclusion>
</exclusions>
</dependency>
{code}
This would avoid to people depending on ZooKeeper artifacts the pain to exclude such "broken" dependencies by themselves.
A similar issue is discussed in HADOOP-6629, although I am not clear on how to solve fix it using Ivy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-721) No set for log4j
dependency in the generated pom.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859690#action_12859690 ]
Patrick Hunt commented on ZOOKEEPER-721:
----------------------------------------
I tried this in ivy.xml but it doesn't effect the generated pom file:
<dependency org="log4j" name="log4j" rev="1.2.15" transitive="false">
<exclude org="javax.jms" module="jms"/>
<exclude org="com.sun.jdmk" module="jmxtools"/>
<exclude org="com.sun.jmx" module="jmxri"/>
<exclude org="javax.mail" module="mail"/>
</dependency>
any ideas?
> No <exclusions> set for log4j dependency in the generated pom.xml
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-721
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-721
> Project: Zookeeper
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.3.0
> Reporter: Paolo Castagna
> Priority: Minor
> Fix For: 3.3.1, 3.4.0
>
>
> The generated Maven pom.xml file contains:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> </dependency>
> {code}
> It would be better to have:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> <exclusions>
> <exclusion>
> <groupId>javax.jms</groupId>
> <artifactId>jms</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jdmk</groupId>
> <artifactId>jmxtools</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jmx</groupId>
> <artifactId>jmxri</artifactId>
> </exclusion>
> <exclusion>
> <groupId>javax.mail</groupId>
> <artifactId>mail</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> {code}
> This would avoid to people depending on ZooKeeper artifacts the pain to exclude such "broken" dependencies by themselves.
> A similar issue is discussed in HADOOP-6629, although I am not clear on how to solve fix it using Ivy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-721) No set for log4j
dependency in the generated pom.xml
Posted by "Paolo Castagna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paolo Castagna updated ZOOKEEPER-721:
-------------------------------------
Labels: maven ivy (was: )
> No <exclusions> set for log4j dependency in the generated pom.xml
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-721
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-721
> Project: Zookeeper
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0, 3.3.1
> Reporter: Paolo Castagna
> Priority: Minor
>
> The generated Maven pom.xml file contains:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> </dependency>
> {code}
> It would be better to have:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> <exclusions>
> <exclusion>
> <groupId>javax.jms</groupId>
> <artifactId>jms</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jdmk</groupId>
> <artifactId>jmxtools</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jmx</groupId>
> <artifactId>jmxri</artifactId>
> </exclusion>
> <exclusion>
> <groupId>javax.mail</groupId>
> <artifactId>mail</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> {code}
> This would avoid to people depending on ZooKeeper artifacts the pain to exclude such "broken" dependencies by themselves.
> A similar issue is discussed in HADOOP-6629, although I am not clear on how to solve fix it using Ivy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-721) No set for log4j
dependency in the generated pom.xml
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-721:
------------------------------------
Fix Version/s: (was: 3.3.1)
moving this out to 3.4.
> No <exclusions> set for log4j dependency in the generated pom.xml
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-721
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-721
> Project: Zookeeper
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.3.0
> Reporter: Paolo Castagna
> Priority: Minor
> Fix For: 3.4.0
>
>
> The generated Maven pom.xml file contains:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> </dependency>
> {code}
> It would be better to have:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> <exclusions>
> <exclusion>
> <groupId>javax.jms</groupId>
> <artifactId>jms</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jdmk</groupId>
> <artifactId>jmxtools</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jmx</groupId>
> <artifactId>jmxri</artifactId>
> </exclusion>
> <exclusion>
> <groupId>javax.mail</groupId>
> <artifactId>mail</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> {code}
> This would avoid to people depending on ZooKeeper artifacts the pain to exclude such "broken" dependencies by themselves.
> A similar issue is discussed in HADOOP-6629, although I am not clear on how to solve fix it using Ivy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-721) No set for log4j
dependency in the generated pom.xml
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-721:
-----------------------------------
Affects Version/s: (was: 3.3.1)
(was: 3.0.0)
3.3.0
Fix Version/s: 3.4.0
3.3.1
> No <exclusions> set for log4j dependency in the generated pom.xml
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-721
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-721
> Project: Zookeeper
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.3.0
> Reporter: Paolo Castagna
> Priority: Minor
> Fix For: 3.3.1, 3.4.0
>
>
> The generated Maven pom.xml file contains:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> </dependency>
> {code}
> It would be better to have:
> {code}
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <scope>compile</scope>
> <exclusions>
> <exclusion>
> <groupId>javax.jms</groupId>
> <artifactId>jms</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jdmk</groupId>
> <artifactId>jmxtools</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.jmx</groupId>
> <artifactId>jmxri</artifactId>
> </exclusion>
> <exclusion>
> <groupId>javax.mail</groupId>
> <artifactId>mail</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> {code}
> This would avoid to people depending on ZooKeeper artifacts the pain to exclude such "broken" dependencies by themselves.
> A similar issue is discussed in HADOOP-6629, although I am not clear on how to solve fix it using Ivy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.