# Bndtools and baselining

**URL:** https://bnd.discourse.group/t/bndtools-and-baselining/322
**Category:** GENERAL
**Created:** [July 22, 2023, 2:47pm UTC](https://bnd.discourse.group/t/bndtools-and-baselining/322 "2023-07-22T14:47:43Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rimmeraj](https://yyz2.discourse-cdn.com/free1/user_avatar/bnd.discourse.group/rimmeraj/32/251_2.png) [@rimmeraj](https://bnd.discourse.group/u/rimmeraj)
#### Post date: [July 22, 2023, 2:47pm UTC](https://bnd.discourse.group/t/bndtools-and-baselining/322/1 "2023-07-22T14:47:43Z")

</div>

When using bndtools and baselining if the project bnd file has to have a version bump the only way to see why is going into the problems tab and hover over the error item. The project itself has the red x but the bnd file does not. Older versions would mark the bnd file with the x and then you could go into the bnd file , hover over the version and find out why bnd wanted to update the version.

I am using bnd 6.4 in eclipse 2023-03 (4.27.0) with Java 17

---

<div class="post-metadata">

### Author: ![juergen-albert](https://yyz2.discourse-cdn.com/free1/user_avatar/bnd.discourse.group/juergen-albert/32/20_2.png) [@juergen-albert](https://bnd.discourse.group/u/juergen-albert)
#### Post date: [July 23, 2023, 5:43pm UTC](https://bnd.discourse.group/t/bndtools-and-baselining/322/2 "2023-07-23T17:43:31Z")

</div>

Thanks for the pointer. I have created an issue for it: [Baselining errors are only shown in the problems view · Issue #5731 · bndtools/bnd · GitHub](https://github.com/bndtools/bnd/issues/5731)