The NAR plugin for Maven allows you to compile native code (C++, C and Fortran) on a number of different architectures (Linux, Windows, MacOSX, Solaris, ...) and with a number of different compilers/linkers (g++, Microsoft Visual C++, CC, ...) The output produced is wrapped up in Native ARchive files (.nar) some of which are machine independent (-noarch), while others are machine specific and thus depend on a combination of machine architecture(A), operating-system(O) and linker(L) identified as AOL. These nar files can be installed in the local Maven repository and deployed to a standard Maven (web) server, using the standard maven-install-plugin and maven-deploy-plugin.

Links

• Documentation
• Mailing list
• Issues
• SCM
• Maven Repository coming soon

FAQ

Q: Is this repository (https://github.com/maven-nar/maven-nar-plugin) the official home of the NAR plugin?

A: Yes. @duns, the original author, donated the plugin (with Sonatype's approval) to the community, since he no longer has time to maintain it.

Q: Is the NAR project being actively maintained?

A: Yes, it is now. It was rather dormant for the past few years, but now has at least two active maintainers (@ctrueden and @dscho), with a few others participating in the development as well.

Q: Why was the plugin renamed to nar-maven-plugin?

A: To comply with the permitted usages of the Maven trademark. According to the Apache Project Management Committee:

The pmc is permitting persons who develop plugins for maven to use the mark maven in their plugin name provided the name and its usage meets certain criteria, amongst which is the "\_\_\_-maven-plugin" naming scheme.

The NAR plugin was previously named `maven-nar-plugin` because it was slated for adoption as an official Maven plugin, but that never happened. So the `artifactId` has been changed to `nar-maven-plugin`. (The `groupId` will need to change as well, but that is still pending.)

Q: Where is the official forum/list?

A: The maven-nar Google group.

Q: Where is the official issue tracker?

A: GitHub Issues. There was a category for NAR in the Sonatype JIRA, which was active until May 2013, but it has apparently been deleted, so we unfortunately cannot migrate those issues to GitHub. If you had filed an issue there which is still relevant to the latest master branch, please file a new GitHub issue for it. Thanks!

Q: When do you expect the 3.0.0 release? Will it be deployed to Central?

A: Yes, we plan to deploy to Central, but we have no set timeline for a release. If it is something you need urgently, please write to the list about it. All of the current NAR maintainers have day jobs, and so have limited time to spend on NAR. So this project is largely driven by A) submitted pull requests; B) the needs of the maintainers; and C) community complaints. ;-)