On Wed, Jun 22, 2011 at 8:09 AM, Amila Jayasekara <[email protected]> wrote: > Hi All, > > Exported package versions of some bundles are set to "0.0.0". > E.g :- commons-io. > > osgi> bundle 27 > commons-io_2.0.0.wso2v1 [27] > Id=27, Status=ACTIVE Data > Root=/home/amila/development/wso2/carbon/trunk/core/distribution/target/wso2carbon-core-3.2.0-SNAPSHOT/repository/components/configuration/org.eclipse.osgi/bundles/27/data > No registered services. > No services in use. > Exported packages > org.apache.commons.io.output; version="0.0.0"[exported] > org.apache.commons.io.monitor; version="0.0.0"[exported] > org.apache.commons.io.filefilter; version="0.0.0"[exported] > org.apache.commons.io.comparator; version="0.0.0"[exported] > org.apache.commons.io.input; version="0.0.0"[exported] > org.apache.commons.io; version="0.0.0"[exported] > No imported packages > No fragment bundles > Named class space > commons-io; bundle-version="2.0.0.wso2v1"[provided] > No required bundles > > Is this ok ?
this is because we haven't specified version while exporting commons-io packages. It dafaults to 0.0.0, when we import the package without verison it defaults to [0.0.0, infinity). While this is not wrong, we are taking away the possibility of having multiple versions of commons-io pakages in the runtime. --Pradeep > > Thanks > AmilaJ > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
