This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Se this thread for details: http://www.netbeans.org/servlets/ReadMsg?msgId=729654&listName=nbdev
As I understand from the attached thread all you need is to plug another library provider. This can be done quite easily by extending the SPI. If you also needed to make the library non final, it would be much more worse. It would break the API/SPI design.
Jesse Glick wrote: "I don't think the current SPI permits this. Currently the SPI permits you to plug in "providers" which can load library definitions of a specified type (given as a String id) from a fixed location in the system file system. But what you need is a way to bypass this storage mechanism entirely and have a provider which can produce a list of library objects based on some quite different storage - i.e. Maven's local repository." AFAIK I need a way to bypass the 2-step LibraryImplementation creation process. (First an empty new instance is created, filled in by the framework somehow and later I can add my stuff form the provider) I alos don't need the storage provided by netbeans. I'm always able to regenerate the content of my library storage on startup. Plus running arbitrary maven goals can retrieve more artifacts from remote repository and make the available in the local repo. as far as I understand it, I would need a different contract in the SPI, to bypass the current SPI mechanism while maintaining the API-SPI contract. My libraryImplementation instances provider would give the framework a full fledged instance of libraryimplementation and no handling on the framework's side is required.
Fixed.
This issue was solved long time ago. Because nobody has reopened it neither added comments, we are verifying/closing it now. If you are still able to reproduce the problem, please reopen. Thanks in advance.