Bug 49932 - Additional OSGI/BND configuration elements
Summary: Additional OSGI/BND configuration elements
Status: RESOLVED FIXED
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.2
Hardware: All All
: P2 normal
Target Milestone: 1.2.18
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-14 20:47 UTC by Steve Coy
Modified: 2012-05-31 13:04 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Coy 2010-09-14 20:47:37 UTC
Some additional elements are required in the maven-bundle-plugin configuration.

We should get off on the right foot and set this as recommended in the OSGI spec. The plugin tries to compose it from the groupId and artifactId (and arrives at "log4j"):

<Bundle-SymbolicName>org.apache.log4j</Bundle-SymbolicName>

The following is needed so that log4j.properties/xml files are externally accessible and also so that log4j can see user's .class files:

<Eclipse-BuddyPolicy>registered</Eclipse-BuddyPolicy>

... and it appears to be conventional to set this:

<Bundle-RequiredExecutionEnvironment>J2SE-1.4</Bundle-RequiredExecutionEnvironment>
Comment 1 grobmeier 2012-05-31 13:04:38 UTC
thanks, changes applied!