Re: How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

No problem - I doubt I'll have enough time to test the update before next release, but I'll have to start at some time.  ;-) As already mentioned, I'll need to check for the eclipse xpath plugin (org.eclipse.wst.xml.xpath2.processor_1.2.0.jar) for what it is needed. Probably even more issues

Re: How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

I'd suggest not trying to do this for Apache NetBeans 10, which we are feature freezing this week. Better to take your time and not rush things and investigate what is needed -- we have plans for at least 3, possibly 4, releases next year. Gj On Wed, Sep 26, 2018 at 11:31 AM, Peter Nabbefeld

Re: How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

Thank You for the pointer! I'm still struggling about the xerces packaging, as there're two different packages at the download page - I "just" have to make sure it will further work as expected. And there's a bundled eclipse jar, I'll have to figure out what it is for (and if I need it).

Re: How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

This could help to show you what's needed, i.e., this is a different library that's being updated: https://github.com/apache/incubator-netbeans/pull/898/commits/05e5d92a93aafa2123b1c08f3f3f629055d258ac Gj On Sat, Sep 22, 2018 at 12:52 PM, Peter Nabbefeld wrote: > > Hm, why does

Re: How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

Hm, why does spec.version.base=1.41.0 differ from the jar's version? IMHO, this doesn't make really sense for a module adding "just" a jar to NB. Regards Peter Am 22.09.18 um 12:22 schrieb Geertjan Wielenga: Start by pointing where in the source code, i.e., provide a link to the Apache

Re: How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

The module's source is here: https://github.com/apache/incubator-netbeans/tree/master/ide/libs.xerces It refers to xerces 2.8. IMO, this should be updated to the newest one (2.12.0). Beginning from version 2.10 there's XSD 1.1 support included, with error corrections in both newer

Re: How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

Start by pointing where in the source code, i.e., provide a link to the Apache NetBeans GitHub repo here, the current Xerces code, etc, references, are found, and let's start there in understanding what needs to be done. Gj On Sat, Sep 22, 2018 at 12:08 PM, Peter Nabbefeld wrote: > Hello, > >

How to write/update/deploy netbeans modules for usage as dependencies in plugin development?

Hello, I'd like to update a NetBeans module (Xerces to version 2.12). For the original Ant build, the sources are located on Github, so they can be changed. But: 1. I have to upload an updated external library - there're upload instructions to Mercurial at

Maven repo for latest plugin development

Dear All May I know where is the Maven repo for latest plugin development? I think i need this org.netbeans.api org-netbeans-modules-editor-settings RELEASE90 Thanks >From Peter

Re: Correct place for plugin development questions

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

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

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

Re: Correct place for plugin development questions

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 >

Re: Correct place for plugin development questions

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

Re: Correct place for plugin development questions

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,

Re: Correct place for plugin development questions

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

Re: Correct place for plugin development questions

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

Re: Correct place for plugin development questions

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

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:

Re: Plugin development

Hi Am 25.05.2018 um 10:21 schrieb sgpa...@mainscreen.com: I am currently developing a fix for a bug in a NB 8.2 plugin but I am running into an issue regarding ProjectClassPathModifier versus ProjectClassPathExtender. Can someone please direct me to the correct place to ask a

Plugin development

I am currently developing a fix for a bug in a NB 8.2 plugin but I am running into an issue regarding ProjectClassPathModifier versus ProjectClassPathExtender. Can someone please direct me to the correct place to ask a question on such an issue? Thanks.

Re: Correct place for plugin development questions

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

Correct place for plugin development questions

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