This content has been marked as final.
Show 3 replies
-
1. Re: Deployer ClassLoader dependencies and OSGi
alesj Aug 6, 2007 10:43 AM (in response to adrian.brock)"adrian@jboss.org" wrote:
Can anybody think of alternate way to do this?
I already introduced VersionRange interface (osgi-int\src\main\org\jboss\osgi\spi\metadata) on top of Scott's VersionRangeImpl in osgi-int module.
Could we just use this one? -
2. Re: Deployer ClassLoader dependencies and OSGi
alesj Aug 6, 2007 10:45 AM (in response to adrian.brock)"alesj" wrote:
I already introduced VersionRange interface (osgi-int\src\main\org\jboss\osgi\spi\metadata) on top of Scott's VersionRangeImpl in osgi-int module.
Could we just use this one?
Eh, this one also uses Version from OSGi API. :-(
I guess we'll have to introduce our own Version interface. -
3. Re: Deployer ClassLoader dependencies and OSGi
starksm64 Sep 18, 2007 2:01 PM (in response to adrian.brock)Let's add this to the common core lib then as I have another duplicate impl in org.jboss.profileservice.spi.repository.Version. Something like:
package org.jboss.util.id; public interface VersionFactory { public Version parseVersion(String version); public Version newVersion(int major, int minor, int micro, String qualifier); public Version emptyVersion(); } public class Version implements Comparable, Serializable { public int getMajor(); public int getMinor(); public int getMicro(); public String getQualifier(); public String toString(); public int hashCode(); public boolean equals(Object object); public int compareTo(Object object); }
Default osgi like implementations could be in org.jboss.util.id.osgi