I'm interested in Jörg's experience. In the documentation, it appears that the NAR project artifact is always a jar and the native binaries are attached artifacts. I haven't seen a way to configure NAR to produce an a.out executable as the project artifact. Please inform me how that should be done.
Thanks! On Thu, Mar 5, 2009 at 10:48 AM, Jörg Schaible <joerg.schai...@gmx.de>wrote: > John Bito wrote at Donnerstag, 5. März 2009 19:26: > > > Thank you very much for pointing out the Jade Native Plugin for building > > native C/C++ applications with > > > Maven< > http://www.jfrog.org/sites/jade-plugins/1.3/jade-plugin-parent/jade-build-plugin-parent/jade-native-plugin/index.html > >. > > As you observe in the nabble thread, the mojo maven-native-plugin is > quite > > weak. Freehep's Maven plugin for native > > builds<http://java.freehep.org/freehep-nar-plugin/>entails overhead to > > enable multiple-architecture targets and distributable > > libraries which will not help my current project. > > Well, this is not really overhead. We also have just one AOL, but it works > out nicely, especially the dependency part. > > However, the only way to get some kind of support is the forum at FreeHEP > and there your questions normally simply rot. This is the only drawback. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
