|
| Re: Unwanted bundles in the final product (optional dependencies) [message #759035 is a reply to message #758970] |
Fri, 25 November 2011 17:49   |
|
On 2011-11-25 13:28, Peter Kullmann wrote:
> Hi,
>
> I just now saw a strange thing with one of our buckminster based builds.
> We have a system consisting of a server and a client part. Both features
> are included in the site feature. When I provision the client using
> director, some server bundles end up in the client. After I removed the
> server feature from the site, the client no longer contains these
> bundles. Also a PDE export of the client product does not include these
> server bundles.
>
> I think this is some kind of an error. The client feature contains a
> bundle (org.springframework.context) which has optional dependencies to
> some JPA related server stuff. Buckminster resolves and includes these
> bundles in the client build although they are not included in the product.
>
> Is there a simple workaround?
It's normal for p2 to always include optional bundles in the install
when it can find them. This is somewhat annoying in some situations. Not
sure if that's applicable here though. The quick remedy would be to not
make a repository available to the p2 director that contains them.
- thomas
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03970 seconds
] 
Search
Help
Register
Login
Home
