Builders property page is bollixed

HCL Domino Domino Forum
1

  • The above is from an application’s Project Properties after closing DDE and relaunching it. I count five separate instances of each and every “builder” on the list. That doesn’t seem like it can be good.

  • Marginally related, the settings on this panel are never remembered across DDE sessions, so each and every time I load this “application” I have to come here and uncheck everything, because I never want it to be part of the build process.

  • It doesn’t help that I’m nagged every check box with an “are you sure?”. Once, maybe. After that it seems like I may actually be doing that on purpose. Then again if it would remember what I told it the first time, the nag dialog would become a non-issue as well, since I’d never see it again.

Thanks for your time…

2

Subject: looks very odd

looks like the db project file must be corrupted; we’ll investigate.

In the meantime, perhaps I’m misunderstanding, but if you don’t want to be part of the build process, the typical way to to do that is to turn off the Build Automatically menu under Project.

3

Subject: I want other applications to build…

  • In this instance I have two applications open, which is certainly a rarity for me.

  • One is the application I’m developing, and I want that one to build.

  • The other is an “application” were I store XPage elements so I can recover from the frequent XPage corruptions I experience. Once I get some aspect to function correctly I copy that working element to the other “application”, with a date stamp in the name. It’s just a storage area and nothing else.

  • I want them both open at once, but the “application” that’s storing elements couldn’t build if it tried, because it’s not a real application. I don’t want 513 “Problems” to appear because it won’t build, and I don’t want to have to build manually and select only the other application.

  • When I uncheck all of the boxes on the Builder panel for the storage “application”, DDE does what I would expect it to do … it ignores that “application” entirely. I can’t “clean” it, I can’t select it to build, I can’t do anything with it, which is precisely what I want.

  • If the “db project is corrupted”, how do I recover from that?

Thanks for your time…

4

Subject: one way…

I reproduced the replicating builder issue; we’ll take a look at that. The .project file is still correct when this goes on, so I will have to debug a bit to see where the duplicates are hiding.

In the meantime, it might be worth configuring the problems view, using working sets to filter which errors you want to see rather than do what you have been. If you put your stash db in its own working set, then your other dbs in a different one, display both working sets at once, then do a configure problems view on the working set where you don’t want to see errors something like this:

the building would still happen, but you wouldn’t see the errors.

5

Subject: I appreciate your suggestion…

  • But I’ve had little luck with working sets and I don’t like the idea of it wasting all the time to “build” the ever-growing pile of unbuildables, which are now about three times larger than the application itself… I’ll just keep deselecting the Builders and getting nagged about it until Lotus comes up with a solution.

  • I’d like to hear when it’s resolved though, if possible.

Thanks again, Maureen!..