moved the faces-config xml under the package structure, renamed to more specific 'holistic-faces-config'
e.g. you can have more than one so you want to have specific names.
Added the path to this faces config to the xsp library
Deleted 'lib' folder.
For starter.project one, I don't think you are actually using this anywhere.
For org.openntf.domino one, you should not need to put the plugins that you depend on 'within' your own plugin. Eclipse should be able to resolve these using a) currently open plug-in projects.
e.g. if you had the openntf api source code plugin project open within your eclipse, eclipse will automatically try to use this (no build path project dependancies needed,  it is all done via Manifest.MF export/import)
b) if you don't have the source code project open in eclipse, you need to add define the plugins as part of your 'target platform' which is what I have done here.
I went to window -> preferences, -> plugin dev -> target platform, and added another 'location' to my XPages Domino Plugin Target, the locations by default have the default plugins that form the XPages target platform, by defining another location I am saying 'also use plugins from here'
you don't need to put features in this part.
also I think you just had the source jar maybe for openntf API? I downloaded the 2 plugins and added them to 'plugindepends' folder, and then added this directory to my target platform.
In your xsp Manifest.MF, I added the dependency to your utils plugin, this means you *should* be able to access your utils classes when this XspLibrary is loaded (even if there are in separate libraries)
Also I exported the package that your XspLibrary is in (otherwise xpages/designer can't see the class at all)
Added a dependancy to com.ibm.xsp.extsn , this should resolve your 'access violation/restriction' error. Basically that means you were using a class that you did not define a dependancy on.
To find out which plugin a class is in you can hit Ctrl + Shift + T and then search for the class, it should show the plugin in the search list. ' <class>  - com.some.plugin'

THen also exported all your packages so your classes are usable by other plugins (including xpages)