AUTO: Warren Cook is out of the office (returning 08/10/2015)
I am out of the office until 08/10/2015. Hello, I am returning to the office on Aug. 11th from vacation. Please forward any requests to Erwin Mendoza.. thx, Warren Note: This is an automated response to your message maven release plugin: help page is showing a deprecated version 2.5 sent on 7/31/2015 8:56:31 AM . This is the only notification you will receive while this person is away.
maven release plugin: help page is showing a deprecated version 2.5
Hi all, not sure to be on the good ML but I would like to ask to one of the maven-release-plugin leader/owner to update some help page about the plugin version to use. for example, this help page is up-to-date and refers to the latest plugin vrersion : 2.5.2 http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html (others overviews pages are ok) but this one is not (refers to : 2.5) https://maven.apache.org/guides/mini/guide-releasing.html maybe this is the only one but that page was my starting point I m trying to check but I have an issue when releasing with 2.5 version : on release:perform target, maven release plugin is deploying on snapshot repo instead of release one. this issue has been discussed here: http://stackoverflow.com/questions/7332580/maven-deploys-to-snapshot-instead-of-release and rely on this bug: http://jira.codehaus.org/browse/MRELEASE-875 Is it possible to update the maven site to show only to the latest version on each page to avoid confusing (unlucky) end-users like me ;) Regards Thanks Brice Vandeputte
Re: maven release plugin: help page is showing a deprecated version 2.5
Hi Brice, On 7/31/15 3:56 PM, Brice Vandeputte wrote: Hi all, not sure to be on the good ML but I would like to ask to one of the maven-release-plugin leader/owner to update some help page about the plugin version to use. It is very good to get in contact with us to show there is something wrong/could be made better...and yes use the mailing list for this... Those pages are independent documentation from the maven-release-plugin...but for example, this help page is up-to-date and refers to the latest plugin vrersion : 2.5.2 http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html (others overviews pages are ok) Those pages are generated during the release of a version of the plugin...so shouldn't be a problem..but this should not mean to check if see issues etc. please report them... but this one is not (refers to : 2.5) https://maven.apache.org/guides/mini/guide-releasing.html maybe this is the only one but that page was my starting point I have fixed the page content to use the most uptodate version. Thanks for reporting this issue.. Kind regards Karl Heinz Marbaise I m trying to check but I have an issue when releasing with 2.5 version : on release:perform target, maven release plugin is deploying on snapshot repo instead of release one. this issue has been discussed here: http://stackoverflow.com/questions/7332580/maven-deploys-to-snapshot-instead-of-release and rely on this bug: http://jira.codehaus.org/browse/MRELEASE-875 Is it possible to update the maven site to show only to the latest version on each page to avoid confusing (unlucky) end-users like me ;) Regards Thanks Brice Vandeputte - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Automating the build of a JNI based application
Hi, I'm creating a JNI wrapper on top of a C++ library. I'd like to have a one-click Maven build for the whole application. When building it manually, I need to do the following: javac ... (compile the Java source files) javah ... (generate JNI header files from Java class files) g++ ... (compile the JNI source files + link them with the static library) I'm looking for a way to have these commands executed by Maven. I looked at the native-maven-plugin ( http://maven.apache.org/archives/maven-1.x/plugins/native/index.html) and I'm afraid it will not work for me. * The documentation is extremely insufficient (there is literally no official documentation on the plugin site and nor is there any information elsewhere on the Internet). * I cannot even look at the source-code as it isn't there in the SVN repository linked from the plugin site. * I tried to make it work based on the two SO posts I discovered but I couldn't. I'm thinking about the following project layout: /src /src/main /src/main/java... the Java interfaces with native methods /src/main/native ... the C++ implementation of the generated header files The static library itself is a product of a different project and will be installed on my system in a standard location (i.e. outside of this project). What I need is essentially to call the javah and g++ commands after the Java .class files have been generated. The g++ command is non-trivial, there are quite a few compiler and linker options that need to be applied. The generated library file should not be a part of the generated JAR file, it should be a separate artifact. I was thinking maybe I'll need to use the exec-maven-plugin ( http://www.mojohaus.org/exec-maven-plugin/index.html) and run the commands manually? Or is there a better way to do this? Also, once the library is generated, I'd like to have Maven run some test cases using the generated JNI wrapper to make sure it works correctly. Thanks very much for your help. Kind regards, Dusan
Re: Automating the build of a JNI based application
Hi, On 7/31/15 6:51 PM, Dušan Rychnovský wrote: Hi, I'm creating a JNI wrapper on top of a C++ library. I'd like to have a one-click Maven build for the whole application. When building it manually, I need to do the following: javac ... (compile the Java source files) javah ... (generate JNI header files from Java class files) g++ ... (compile the JNI source files + link them with the static library) I'm looking for a way to have these commands executed by Maven. I looked at the native-maven-plugin ( http://maven.apache.org/archives/maven-1.x/plugins/native/index.html) and I'm afraid it will not work for me. Nor should it cause Maven 1 is simply dead.. * The documentation is extremely insufficient (there is literally no official documentation on the plugin site and nor is there any information elsewhere on the Internet). which is not really astonishing... * I cannot even look at the source-code as it isn't there in the SVN repository linked from the plugin site. * I tried to make it work based on the two SO posts I discovered but I couldn't. I'm thinking about the following project layout: /src /src/main /src/main/java... the Java interfaces with native methods /src/main/native ... the C++ implementation of the generated header files The static library itself is a product of a different project and will be installed on my system in a standard location (i.e. outside of this project). What I need is essentially to call the javah and g++ commands after the Java .class files have been generated. The g++ command is non-trivial, there are quite a few compiler and linker options that need to be applied. The generated library file should not be a part of the generated JAR file, it should be a separate artifact. I was thinking maybe I'll need to use the exec-maven-plugin ( http://www.mojohaus.org/exec-maven-plugin/index.html) and run the commands manually? Or is there a better way to do this? Also, once the library is generated, I'd like to have Maven run some test cases using the generated JNI wrapper to make sure it works correctly. Thanks very much for your help. Kind regards, Dusan I woudl suggest to take a look into the nar-maven-plugin: http://maven-nar.github.io/ which might be better fit your needs.. Kind Regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
