Re: Correct place for plugin development questions

2018-05-25 Thread sgparry
I think I have worked out the problem and a solution: Sources sources = ProjectUtils.getSources(project); SourceGroup sourceGroup = sources.getSourceGroups(JavaProjectConstants.SOURCES_TYPE_JAVA)[0]; FileObject sgRoot = sourceGroup.getRootFolder();

Re: Correct place for plugin development questions

2018-05-25 Thread sgparry
The plugin is Fred Vinet's ANTLR4 plug in. The plugin adds ANTLR4 support to Netbeans, i.e. syntax checking / highlighting / completion of the grammar and an automated build via ANT or Maven. IT implements a very useful "Add ANTLR support" menu option to the file menu which adapts an ANT or Mave

Re: Correct place for plugin development questions

2018-05-25 Thread Stephen Parry
Sorry, did not even realise I was On 25/05/2018 17:21, Antonio wrote: Hi, Please do not cross post to both dev@netbeans.incubator.apache.org and d...@netbeans.apache.org The proper email address is dev@netbeans.incubator.apache.org, as NetBeans is a proud member of the Apache Incubator Pro

Re: Correct place for plugin development questions

2018-05-25 Thread Antonio
Hi, Please do not cross post to both dev@netbeans.incubator.apache.org and d...@netbeans.apache.org The proper email address is dev@netbeans.incubator.apache.org, as NetBeans is a proud member of the Apache Incubator Project. Thanks, Antonio ---

Re: Correct place for plugin development questions

2018-05-25 Thread Geertjan Wielenga
On Fri, May 25, 2018 at 11:50 AM, sgpa...@mainscreen.com < sgpa...@mainscreen.com> wrote: > Hi, > Can someone please direct me to the correct place for asking questions > regarding plugin devlopment? > I am having trouble contributing a fix to a bug in a third-party NB 8 > plugin Which 3rd part

Re: Correct place for plugin development questions

2018-05-25 Thread sgparry
Sorry, I misunderstood what you were getting at. FQN is: org.netbeans.modules.java.api.common.classpath.ClassPathModifier On 2018/05/25 12:57:10, Peter Nabbefeld wrote: > > Hi Stephen, > > the package is exported as public (not friend), so You should be able to > look for the implementation

Re: Correct place for plugin development questions

2018-05-25 Thread Peter Nabbefeld
Hi Stephen, the package is exported as public (not friend), so You should be able to look for the implementation (which might not be public, but we only need the FQCN). What "parameter 3" are You referring to? Regards P. Am 25.05.2018 um 14:44 schrieb sgpa...@mainscreen.com: I'll try lo

Re: Correct place for plugin development questions

2018-05-25 Thread sgparry
I'll try looking up the pcpmi if the visibility will let me - The pcpmi can at least provide a list of the extensible source groups, which should lead to the right value for the second parameter to addLibraries. How do get the list of types for parameter 3 I wonder? On 2018/05/25 11:57:42, Pete

Re: Correct place for plugin development questions

2018-05-25 Thread Peter Nabbefeld
Oops, sorry for the duplicate postings - had some problems with my email client. Regards Peter Am 25.05.2018 um 12:11 schrieb Peter Nabbefeld: Hi Stephen, what does it mean, You "cannot get it working"? Which problems (behaviour or exceptions) do You have exactly? Kind regards Peter Am

Re: Correct place for plugin development questions

2018-05-25 Thread Peter Nabbefeld
Hi Stephen, I've found the following source code:     @SuppressWarnings("deprecation")     public static org.netbeans.spi.java.project.classpath.ProjectClassPathExtender extenderForModifier(final Project p) {     return new org.netbeans.spi.java.project.classpath.ProjectClassPathExtender

Re: Correct place for plugin development questions

2018-05-25 Thread Peter Nabbefeld
Hello Stephen, as it's Your source code, the right place for questions is here. I haven't used ProjectClassPathModifier or ProjectClassPathExtender yet, but from the JavaDoc I'd guess You should probably be able to use "ProjectClassPathExtender pcpe = pcpm.extenderForModifier(pcpe);". While

Re: Correct place for plugin development questions

2018-05-25 Thread sgparry
Hi Peter, Thanks for the quick reply. The plugin adds a library to the classpath, currently by rewriting the projevct properties file. I am trying to use the API instead. I can get it working using ProjectClassPathExtender but not ProjectClassPathModifier, which gives me: Java.lang.UnsupportedOpe

Re: Correct place for plugin development questions

2018-05-25 Thread Peter Nabbefeld
Hi Stephen, what does it mean, You "cannot get it working"? Which problems (behaviour or exceptions) do You have exactly? Kind regards Peter Am 25.05.2018 um 11:50 schrieb sgpa...@mainscreen.com: Hi, Can someone please direct me to the correct place for asking questions regarding plugin d

Correct place for plugin development questions

2018-05-25 Thread sgparry
Hi, Can someone please direct me to the correct place for asking questions regarding plugin devlopment? I am having trouble contributing a fix to a bug in a third-party NB 8 plugin - I have a fix using the deprecated ProjectClassPathExtender class but I want to use the replacement ProjectClassPa