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.
Netbeans 6.5 I have a Web Project that uses JAX-RS. Instead of using Netbeans built-in libraries I wish to provide my own JAR file for JAX-RS and Jersey because I am using newer versions than provided with Netbeans. It seems that Netbeans makes this impossible. If I remove the libraries from my project, delete them from the project "libraries" directory, and restart Netbeans then the project shows up with "missing dependencies" restapi, restlib. These dependencies come from Netbeans, not from my project settings. In fact, if I go into Project Properties -> Libraries there is absolutely no mention of REST. When I expand the project node all of a sudden Netbeans automatically adds restapi, restlib to my project. I am expecting: 1) Netbeans to warn me about the missing REST libraries like any other missing dependencies. If I omit other libraries Netbeans will simply complain of compilation errors. I expect the same here. 2) Netbeans to let me supply my own JAR files for these libraries.
Reassigning to web for evaluation.
Reassigning to rest for evaluation
It would be definitely great if people could turn off the automatic inclusion of NetBeans Jersey bundled libs, so that they can configure their own at their projects. It is not only about 3rd party JAX-RS implementations, but also impacts newer versions of Jersey, which are currently difficult to use.
After fixing the issue 154586, RESTful web service plugin pickup JAX-RS libraries from Glassfish if available. This will make it easier to use latest Jersey libraries than those available in the plugin *** This issue has been marked as a duplicate of 154586 ***
ayubskhan, I disagree. I am using the trunk build of Jersey and I would like to continue doing so. The fact that you pick up Jersey from Glassfish is nice, but isn't what I asked for. I don't want Netbeans to automatically import Jersey. It should wait for users to explicitly import the library from the global store into the project-specific store.
I am no longer interested in this feature. *** This bug has been marked as a duplicate of bug 154586 ***