Bug 43488 - Use provided scope for sun jars in maven pom
Summary: Use provided scope for sun jars in maven pom
Status: RESOLVED DUPLICATE of bug 43304
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.2
Hardware: Other other
: P2 major
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on: 37930
Blocks:
  Show dependency tree
 
Reported: 2007-09-26 08:27 UTC by Dennis Kieselhorst
Modified: 2007-09-26 23:34 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Kieselhorst 2007-09-26 08:27:57 UTC 
I appreciate that log4j now uses Maven2 as build tool. Unfortunately I'm unable
to build my application after upgrading to 1.2.15.

Please update the pom and set dependency scopes for the sun jars that are not on
a public repository (<scope>provided</scope>). The java.net repository
https://maven-repository.dev.java.net/nonav/repository referenced in the pom
doesn't contain these jars.

See also:
http://www.mail-archive.com/dev@cocoon.apache.org/msg53619.html
Comment 1 Curt Arnold 2007-09-26 14:49:18 UTC 
They have already been changed in the SVN HEAD to be "optional" since they are required to build log4j 
1.2 but they are not required to be on the classpath to use log4j "unless" you want to use the JMS or JMX 
features in log4j.  Are you suggesting "optional" be changed to "provided"?

This bug might be considered a duplicate to 43304.
Comment 2 Dennis Kieselhorst 2007-09-26 23:34:04 UTC 
Sorry I should have had a look in the trunk before posting. optional also meets 
the needs.

*** This bug has been marked as a duplicate of 43304 ***