0

I am developing a plugin for NetBeans 8.0 and I created a LookupProvider which is registered like that:

@LookupProvider.Registration(projectType = {
  "org-netbeans-modules-ant-freeform",
  "org-netbeans-modules-j2ee-archiveproject",
  "org-netbeans-modules-j2ee-clientproject",
  "org-netbeans-modules-j2ee-earproject",
  "org-netbeans-modules-j2ee-ejbjarproject",
  "org-netbeans-modules-java-j2seproject",
  "org-netbeans-modules-maven",
  "org-netbeans-modules-web-clientproject",
  "org-netbeans-modules-web-project"
})

I would like to know if there is the possibility to reference the project types from a constant (which is already defined by the NetBeans platform) or do I really have to declare them as strings (like org-netbeans-modules-web-clientproject)?

Benny Code
  • 51,456
  • 28
  • 233
  • 198

1 Answers1

0

I believe there are constants for these but the question is if you really want to depend on them. Oftentimes the constants are hidden in the project type's own module that doesn't provider API packages or provides them only to friends. And typically your own primary dependency is on the interface that you implement and put into the lookup. There could be some sort of master list in a public package somewhere but that could always just list the subset of project types. Also please note that for maven you can actually have an unlimited number of constants as we support only registering your LP to a given maven packaging type.

mkleint
  • 2,281
  • 1
  • 14
  • 17
  • Sometimes it's not obvious, what the project name is. For HTML5 projects I've seen "org-netbeans-modules-web-clientproject" and "org-netbeans-modules-web.clientproject". So it would be nice to have well defined constants given by the API. – Benny Code Oct 18 '14 at 22:18
  • I suppose one of these entries is actually wrong and not working. I agree a constant here and there would be nice but the problem is location of these constants and the fact the list will always be incomplete. – mkleint Oct 19 '14 at 09:34