Hi, While cleaning pom files, we realized that there is a set of dependencies used in styles bundle of each product. These are used as compile time dependencies for bundle activators.
And unlike other places, we are referring to the external versions of these bundles, not the orbit/carbonized bundles. Following is the list of these dependencies along with their versions. org.apache.felix : org.apache.felix.framework : 1.0.3 org.apache.felix : org.apache.felix.main : 1.0.3 org.apache.felix : org.osgi.compendium : 1.0.0 org.eclipse.equinox : org.eclipse.equinox.http.servlet : 2.2.2 org.eclipse.equinox : org.eclipse.equinox.http.helper : 1.0.0 org.eclipse.equinox : org.eclipse.equinox.jsp.jasper : 1.0.1.R33x_v20070816 org.eclipse.equinox : javax.servlet.jsp : 2.0.0.v200706191603 These dependencies are repeated in each and every product + stratos service within their styles bundles. Can we refer to the corresponding carbon artifacts instead of these versions ? Shall we move this to a upper level (i.e. products root pom), so that it is easier to manage these dependencies ? Thanks, Thilina -- Thilina Buddhika Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 77 44 88 727 blog : http://blog.thilinamb.com
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
