Skip to main content

Source code revision

svn

summary: Issue #5992: Specify version constraints in Import-Package The reason version is missing from our Import statements is because of our lack
revision: 22703
author: Sahoo
date: 2008-09-16 15:49:03 UTC (6 years)
message: Issue #5992: Specify version constraints in Import-Package
The reason version is missing from our Import statements is because of our lack
of awareness about a feature of maven-bundle-plugin. As mentioned in
https://issues.apache.org/jira/browse/FELIX-548, maven-bundle-plugin does not
encode version number for classes resolved from dependencies with provided
scope. We mark a lot of our dependencies especially javax dependencies with such scope,
hence for them version does not appear for most of them. In this check-in, I am fixing all
such dependencies to use compile scope. I am not touching admingui module as they don't
affect server runtime as much. I will send a note to admingui team to make
necessary change.
Change Path Actions
M trunk/v3/common/common-util/pom.xml
M trunk/v3/core/kernel/pom.xml
M trunk/v3/ejb/ejb-connector/pom.xml
M trunk/v3/ejb/ejb-container/pom.xml
M trunk/v3/ejb/ejb-timer-service-app/pom.xml
M trunk/v3/security/common/pom.xml
M trunk/v3/security/realm/pom.xml
M trunk/v3/security/webintegration/pom.xml
 
 
Close
loading
Please Confirm
Close