Compatibility shim for IDEA and NetBeans

[Sailsman63]

I've recently been working on migrating a project from an ancient set of ant scripts to mill. (There is an alternative gradle option from another community member - That's still an open discussion!)

The most substantial piece of pushback that I've gotten from the community was regarding the sub-par support for mill builds in common IDEs. So, I made a thing:

<?xml version="1.0"?>

<project name="ArtOfIllusion Full Suite" default="run" basedir=".">

    <condition property="MILL_COMMAND" value="millw.bat" else="./millw">
        <os family="windows"/>
    </condition>
    <!-- This is critical! Netbeans on Windows requires "false", Idea on Linux requires "true". Neither seems
           to care on the opposite platform. -->
    <condition property="VM_LAUNCHER" value="false" else="true">
        <os family="windows"/>
    </condition>

    <target name="compile" description="Compile project sourcefiles">
        <exec executable="${MILL_COMMAND}" failifexecutionfails="true" vmlauncher="${VM_LAUNCHER}">
            <arg value="__.compile"/>
        </exec>
    </target>

    <target name="test" description="Run project automated tests">
        <exec executable="${MILL_COMMAND}" failifexecutionfails="true" vmlauncher="${VM_LAUNCHER}">
            <arg value="__.test"/>
        </exec>
    </target>

    <target name="clean">
        <exec executable="${MILL_COMMAND}" failifexecutionfails="true" vmlauncher="${VM_LAUNCHER}">
            <arg value="clean"/>
        </exec>
    </target>

    <target name="run">
        <exec executable="${MILL_COMMAND}" failifexecutionfails="true" vmlauncher="${VM_LAUNCHER}">
            <arg value="Suite.launch"/>
        </exec>
    </target>

    <target name="run-debug" description="Run a local deployment. Suspends and waits for a debugger to attach.">
        <exec executable="${MILL_COMMAND}" failifexecutionfails="true" vmlauncher="${VM_LAUNCHER}">
            <arg value="Suite.launch"/>
            <arg value="-agentlib:jdwp=transport=dt_socket,server=y,address=8000,suspend=y"/>
        </exec>
    </target>

    <!--Netbeans has a weird debugger rule. When you first debug, it will generate a 'debug-nb' task in
	'nbproject/ide-targets.xml'. Delete the file. In the 'project.xml' change the debug action script
	value to 'build.xml'. After that, it will just run. This is modified from the target that Netbeans wants
        to generate for itself. -->
    <target name="debug-nb" description="Support for netBeans debug - all others ignore!">
        <nbjpdastart addressproperty="jpda.address" name="ArtOfIllusion Full Suite" transport="dt_socket"/>
        <exec executable="${MILL_COMMAND}" failifexecutionfails="true" vmlauncher="false">
            <arg value="Suite.localDeploy"/>
        </exec>
        <java jar="out/Suite/localDeploy.dest/ArtOfIllusion.jar" fork="true">
            <jvmarg value="-agentlib:jdwp=transport=dt_socket,address=${jpda.address}"/>
        </java>
    </target>
</project>

It's just a (thin) ant script -modify as appropriate for your specific mill build.
It works for IDEA - who's BSP support is kind of sad - and NetBeans - Where BSP is non-existent.

I've tested on Windows 10 and Arch Linux. No mac access, so I don't know what would happen there. I'm assuming something *nix-like.

You may have noticed that I haven't done anything with eclipse: When I loaded the project into eclipse, it just ran, including making plugins available. I suspect some weird Frankenstein classpath thing is being generated, but if it allows basic running and debugger access, why mess with it?

Thoughts?