|
| Re: "Chanining" resolvers [message #669725 is a reply to message #669715] |
Wed, 11 May 2011 09:27   |
|
On 2011-05-11 11:11, Fabian Baboschi wrote:
> I want to include a feature and it's plugins in my product.
>
> The feature and plugins are stored into a .jar file on
> artifactory.
> Also, the .jar file doesn't contain a p2 update site, but a
> classic (3.4 style).
> The structure of the .jar containing the resources is:
> - .
> ---- features/
> ------- my.feature_1.0.0.20110511-1514.jar
> ---- plugins/
> ------- my.plugin_1.0.0.20110511-1514.jar
> ---- MANIFEST.MF
>
> My questions are:
> First of all, is it possible to use Buckminster to import
> from this source even by developing some sort of resolver
> or extending a reader type?
>
Yes, you can probably do that out of the box using a url reader type with a matcher (to extract names and versions from
file names).
> Is it possible to chain the resolvers somehow. For example:
>
> Use a p2SiteGenerator reader which uses a zip reader which
> uses an artifactory reader?
>
Yes, either put them both in the same provider (best fit wins) or put them in separate providers and use locators with
failOnError=false (first fit wins).
> What would be the best practice for doing such chaining
> (importing stuff into the workspace as well as in the
> build)?
>
I would never import binaries into the workspace. Put them in he target platform.
Regards,
Thomas Hallgren
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03226 seconds
] 
Search
Help
Register
Login
Home
