Grassy Banana, Can't build the Project "You must define nbplatform"

Hello fellow monkeys ! It’s been a while since I posted on the forum (busy working on school project) but I really want to test the change from the 3.1 :stuck_out_tongue:.
I’ve got a problem with netbeans when I try to build my cloned project from the git depot (I have the developer plugin installed).

:rainbow: GitHub - jMonkeyEngine-Contributions/grassy-banana :rainbow:

Here is what I got from netbeans

D:\Projet\JMonkey_3_1\grassy-banana\build.xml:7: The following error occurred while executing this line:
D:\Projet\JMonkey_3_1\grassy-banana\nbproject\build-impl.xml:22: You must define 'nbplatform.${}.harness.dir'

And now the xml

<?xml version="1.0" encoding="UTF-8"?>
<project name="com.Stomrage.grassybanana-impl" basedir="..">
    <property file="nbproject/private/"/>
    <property file="nbproject/"/>
    <fail unless="suite.dir">You must set 'suite.dir' to point to your containing module suite</fail>
    <property file="${suite.dir}/nbproject/private/"/>
    <property file="${suite.dir}/nbproject/"/>
    <macrodef name="property" uri="">
        <attribute name="name"/>
        <attribute name="value"/>
            <property name="@{name}" value="${@{value}}"/>
    <property file="${}"/>
    <nbmproject2:property name="harness.dir" value="nbplatform.${}.harness.dir" xmlns:nbmproject2=""/>
    <nbmproject2:property name="netbeans.dest.dir" value="nbplatform.${}.netbeans.dest.dir" xmlns:nbmproject2=""/>
    <fail message="You must define 'nbplatform.${}.harness.dir'">
                <available file="${harness.dir}" type="dir"/>
    <import file="${harness.dir}/build.xml"/>

I tried to solve it myself, but I really can’t find where the problem come from. The only thing I know is that harness is supposed to be the destination platform ? I just realised that the plugin miss the “global” plugin project maybe a clue I don’t know.

Sorry to bother you with such a simple matter

The plugin has to be part of a suite, is that the case?

1 Like

Thanks @normen !

For those with the same issue, a module is included into a module suite and can’t work alone. The platform information is hold by the module suite. if you want the process to do so

to add an existing project to a module suite