Mercurial > hg > truffle
view visualizer/build.xml @ 12487:28d7a11ba008
revert attempt to avoid Eclipse build loops
"We need a way the refresh the created jar file in Eclipse. Doing it directly in Jar.launch does not work for some reasons I still do not completely understand. So Refresh.launch is the workaround for that problem. Unfortunately the Refresh.launch needs to be async and that causes the well known build loop. Setting the Refresh.launch not to be async does sadly not help." -Christian Humer
author | Doug Simon <doug.simon@oracle.com> |
---|---|
date | Fri, 18 Oct 2013 17:00:52 +0200 |
parents | ab4a47b6a187 |
children |
line wrap: on
line source
<?xml version="1.0" encoding="UTF-8"?> <!-- You may freely edit this file. See harness/README in the NetBeans platform --> <!-- for some information on what you could do (e.g. targets to override). --> <!-- If you delete this file and reopen the project it will be recreated. --> <project name="Graal Visualizer" basedir="."> <description>Builds the module suite Graal Visualizer.</description> <import file="nbproject/build-impl.xml"/> <target name="build-launchers" depends="suite.build-launchers"> <!-- Drop memory presets (-Xms, -Xmx) from default_options of packaged builds and let the executing VM choose reasonable defaults --> <replaceregexp file="${build.launcher.dir}/etc/${app.name}.conf" byline="true" match="^default_options=.*" replace='default_options="--branding graalvisualizer"' /> </target> <!-- Local (environment-specific) extensions/modifications to the build --> <import file="build-local.xml" optional="true" /> </project>