1

I have a situation where we wrap a jar with JSmooth to get an suitable exe file.

This has traditionally been built by ant, and as part of our general mavenification the current, short-term solution has been to use maven-antrun-plugin to set a property and invoke ant.

Unfortunately this approach fails when building on Unix (as there is no X11 display available) and the solution is to invoke the JVM with -Djava.awt.headless=true. I would like to do this in my pom.xml but cannot identify where to do this.

<plugin>
    <artifactId>maven-antrun-plugin</artifactId>
    <version>1.7</version>
    <executions>
        <execution>
            <phase>package</phase>
            <configuration>
                <target>
                    <!-- create one-jar and exefy it -->
                    <property name="maven.project.build.finalName" value="${project.build.finalName}" />
                    <!-- note: fails on headless Linux for now -->
                    <ant />
                </target>
            </configuration>
            <goals>
                <goal>run</goal>
            </goals>
        </execution>
    </executions>
</plugin>

It is ok to fork a new JVM directly but not to rely on platform specifics.

How can I do this correctly?

M A
  • 71,713
  • 13
  • 134
  • 174
Thorbjørn Ravn Andersen
  • 73,784
  • 33
  • 194
  • 347

2 Answers2

5

As far as I know, the solution without forking JVM is to use MAVEN_OPT

export MAVEN_OPTS="-Djava.awt.headless=true"

Since -D is JVM option, you had to specify it to maven directly. You cannot (once again, from what I know) pass it as internal argument (and there isn't any configuration option that allow it)

So, using MAVEN_OPT parameter become the right way to do it.

EDIT 1:

You can have a glance here using better-maven2-antrun-plugin

http://code.google.com/p/better-maven2-antrun-plugin/wiki/Usage

EDIT 2: Can can maybe help maven-antrun developpement providing them a way to specify those parameters, like maven-compiler-plugin. This would be the best way if you really want to use pom informations.

kryger
  • 12,906
  • 8
  • 44
  • 65
Jean-Rémy Revy
  • 5,607
  • 3
  • 39
  • 65
  • @ThorbjørnRavnAndersen - I think the "Setting JVM options" section on the linked page describes exectly what you are looking for. – Attila Jun 14 '12 at 12:19
  • I do not want to use MAVEN_OPTS, I want this in my pom.xml. I'll have a look at the newer antrun. – Thorbjørn Ravn Andersen Jun 14 '12 at 12:25
  • After further googling, it seems that maven-ant-run plugin really don't have params to specify jvm option. I'm stil looking for, but I'm pretty sure there is no solution with this one. – Jean-Rémy Revy Jun 16 '12 at 21:44
  • thanks , initially added in JAVA_OPTS ,didn't help for maven build. but adding MAVEN_OPTS=-Djava.awt.headless=true, in environment varibale, it worked well. – chandu Nov 05 '20 at 08:44
2

The ant manual has a section titled "Running Ant via Java" that shows how to do just what you want. A slightly tweaked version of their example is reproduced below:

<java
        classname="org.apache.tools.ant.launch.Launcher"
        fork="true"
        failonerror="true"
        dir="${basedir}"
        taskname="headless-ant"
>
    <classpath>
        <pathelement location="${ant.home}/lib/ant-launcher.jar"/>
    </classpath>
    <arg value="-buildfile"/>
    <arg file="${ant.file}"/>
    <arg value="-Dbasedir=${basedir}"/>
    <jvmarg value="-Djava.awt.headless=true"/>
</java>

If you put that snippet in place of the <ant> element in your snippet, it should do the trick.

Matt McHenry
  • 20,009
  • 8
  • 65
  • 64