Hi Gary, Thanks for the response. I take it then that most of the plugin providers package their JARs with the appropriate Manifest data. And I assume that if they don't, then the Package#getImplementationVersion method will return null.
Cheers, Mark On Sun, Jun 2, 2013 at 3:01 PM, Gary Gregory <[email protected]> wrote: > On Jun 2, 2013, at 13:46, Mark Fortner <[email protected]> wrote: > > > I've been tinkering with yet another GUI for Commons VFS (hasn't > everybody > > at this point). And I was wondering if there's a way to programmatically > > determine whether or not a SPI is compatible with a specific version of > the > > API? > > > Someclass.class.getPackage() gives you access to the info from the > manifest file, which includes the version. > > Gary > > > The idea is that a user would be able to safely install support for > > one of the file systems. > > > > My thought was that I could use a simple maven resolver to point to an > > implementation on a maven repo, and download that JAR and it's > dependencies > > to a known location. When you relaunch the browser, it would then add > > those JARs to its classpath. > > > > Admittedly, this is a half-baked idea, so I was wondering if anyone had > any > > similar thoughts, or if there were any VFS projects that have already > > addressed this issue? > > > > Cheers, > > > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
