Maintainers: Update Plugins for Gephi 0.9.3

[mbastian]

Hi all, we're pleased to have just released the latest Gephi version! This release doesn't require major changes to plugins so we were able to already adapt and publish most of your plugins.

As maintainers, we would like however to ask you to test it to make it sure it still works in the 0.9.3 version.

Also, follow those instructions to adapt your code to the 0.9.3 changes. Make a Pull Request so we can then merge your changes to the master-forge branch. You can see an example of an up-to-date plugin on the geolayout-plugin branch.

If you're unsure what to do, don't hesitate to ask!

1. Merge from master branch

Before starting, make sure to merge with the master branch so you get the latest changes to the pom.xml.

2. Update parent pom

Make sure each of your modules use the latest version of the gephi-plugin-parent

<parent>
     <artifactId>gephi-plugin-parent</artifactId>
     <groupId>org.gephi</groupId>
     <version>0.9.3</version>
</parent>

Also make sure to also remove the modules/pom.xml file if you still have one. This old parent POM is no longer needed.

3. Update Netbeans's NBM plugin

This is an important change. The Netbeans NBM Maven Plugin we're using has a new groupId: org.apache.netbeans.utilities

Before:

 <build>
        <plugins>
            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>nbm-maven-plugin</artifactId>
                ....

Now:

 <build>
        <plugins>
            <plugin>
                <groupId>org.apache.netbeans.utilities</groupId>
                <artifactId>nbm-maven-plugin</artifactId>
                ....

4. Some modules have been merged

We did some cleanups as part of #2356. Some Gephi modules were merged together, which means you might need to update your dependencies.

If you depend to any of those Gephi dependencies, update as indicated:

• ui-propertyeditor -> ui-utils
• lib-validation -> ui-utils
• io-processor-plugin -> io-importer-plugin

5. Run validation

Before submitting a PR, make sure your plugin properly builds and validates.

There were a couple of API changes that you may need to adapt to. You can see the full list on the release notes.

Thank you!