| Bundle-level p2.inf ignored by recent versions of Buckminster [message #894164] |
Sat, 07 July 2012 02:09  |
Eclipse User |
|
|
|
Hi,
I'm trying to upgrade from Buckminster 3.6 to 3.7 and 4.2, but now my
build is completely ignoring the p2.inf files included in my bundles'
META-INF folders. The p2.inf files co-located with my product files are
still used but none of the bundle-level advices are applied. Buckminster
3.6 picks them up without a problem.
Can anyone think of a reason this would be the case? It's not just one
specific bundle, there are at least three that add jvm args during
configure phase (for example) that are now completely ignored.
Thanks in advance.
--Peter
|
|
|
| Re: Bundle-level p2.inf ignored by recent versions of Buckminster [message #905737 is a reply to message #894164] |
Thu, 30 August 2012 21:28  |
| Eclipse User |
|
|
|
FWIW -- I found the reason, kind of funny: I have bin.excludes =
META-INF/p2.inf in my build.properties so that p2.inf doesn't get
included in the final jars. If I remove that then all works fine.
Much less of a problem than not having p2.inf work; however, would be
nice to exclude p2.inf from final jars. Does anyone know of a simple way
(other than through buckminster.cspex, adding a step before site.p2,
etc. etc.)
On 7/7/12 2:09 AM, Peter Nehrer wrote:
> Hi,
>
> I'm trying to upgrade from Buckminster 3.6 to 3.7 and 4.2, but now my
> build is completely ignoring the p2.inf files included in my bundles'
> META-INF folders. The p2.inf files co-located with my product files are
> still used but none of the bundle-level advices are applied. Buckminster
> 3.6 picks them up without a problem.
>
> Can anyone think of a reason this would be the case? It's not just one
> specific bundle, there are at least three that add jvm args during
> configure phase (for example) that are now completely ignored.
>
> Thanks in advance.
>
> --Peter
|
|
|
Powered by
FUDForum. Page generated in 0.03691 seconds
Home