Question

I have a java project consisting of three modules

• project-common
• project-a
• project-b

Project a and b use -common as dependency.

I use a simple assembly configuration to put project-a, project-b and all dependent libraries (spring and so on) in a single archive.

I also want to provide startscripts for different platforms (windows32, windows64, linux32, linux64 and macosx).
For example I will use for windows winrun4j and sh-scripts for linux.

What is the best approach to manage these files (as they don’t need any compilation etc. like native libraries)?

Currently I placed the startfiles for every project in its /main/resources/bin folder resulting in an assembly were all startscripts for alle platforms end up.

Is there some clevery why to move these startfiles into dedicated modules and manage them somewhow to be able to build “platform specific” assemblies including only the startfiles for a given platform?

Answer 1

You can use profiles activation and OS detection :

<profiles>
    <profile>
        <activation>
            <os>
                <family>windows</family>
                <arch>x86</arch>
            </os>
        </activation>
        ....
    </profile>
</profiles>

---

Resources :

• Introduction to build profiles
• Maven enforcer plugin – Require OS Version

On the same topic :

• Maven: Finding out whether running in a 32 or a 64 bit JVM