Hi Scott, repository locations are simply represented as a URL. Since both metadata and artifact repositories are pluggable via extension point, any valid URL could potentially represent a repository. Currently the one way to find out if a give URL actually represents a repository is by calling loadRepository(URL, ...) on either IMetadataRepositoryManager or IArtifactRepositoryManager. Hope that helps get you started...
John Scott Lewis <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 02/05/2008 12:08 PM Please respond to Equinox development mailing list <equinox-dev@eclipse.org> To Equinox development mailing list <equinox-dev@eclipse.org> cc Subject [equinox-dev] [prov] ECF discovery of artifact and metadata repos In prep for EclipseCon, the ECF team would like to create a demo that discovers p2 artifact and metadata repos. ECF has a discovery API [1], now implemented with both zeroconf/bonjour and SLP providers [2]. We've recently done an example that discovers update sites on lan [3]. So, my main question is: for discovering artifact and metadata repos, what is the necessary meta-meta-data? (data about location/access to repos). Is it simply an URL, or is there more to it? Pointers into p2 code desired...as I need to do that anyway. Thanks, Scott [1] http://wiki.eclipse.org/ECF_API_Docs#Discovery_API [2] http://www.lemmster.de/blog/index.php/2008/02/03/168/ [3] http://wiki.eclipse.org/Update_Site_Discovery _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev