My solution: Create a Startup Project Group and have NetBeans always open that when starting. What I am trying to do is expose my library to the web, via an existing IIS 6.0 web server I already have on my network. Then I must cancel the operations and try to convince my machine that I really don’t want to go through all of that scanning and indexing… I just want to open up a much smaller project or even create a new one. That’s all fine and good if that is the project I am working on, but if it isn’t then it becomes a big headache. When I browse to /calibre I get the Calibre Content Server page, everything works fine and I can browse by Publisher, Authors, All Books etc. No Outbound rules are required as the Calibre website allows a URL prefix to be set. Some of the projects that I work on are quite large, with Maven repositories that must be scanned and re-indexed upon startup. To begin with I created a folder Calibre under Sites and the created the necessary rules in Inbound URL Rewrite as detailed in the Calibre manual. The problem lies in the fact that NetBeans will always open the last Project Group that you had open when it starts up. You can define multiple Project Groups and switch between them.

These are used to group projects that should be worked on at the same time, similar to a Solution in Visual Studio.

NetBeans has what they call Project Groups. As a user of the NetBeans IDE, I have always had this one complaint.

Calibre web server iis