Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Maxim Solodovnik
Hello Lin, We had this issue in this project: https://github.com/Red5/red5-server Here is the report: https://groups.google.com/d/msg/red5interest/EbVFdFkEGWE/1N_eqcz5K-UJ Somehow class was missing in runtime after building with Java8 rebuilding with Java7 fixes the problem On Mon, Mar 30, 2015

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Thanks Olivier, I am using JDK 1.8 for development and shall I change source and target to 1.8? I think the most popular version of Java are 1.7 or 1.8, not sure why Maven makes 1.5 as default? regards, Lin On Sun, Mar 29, 2015 at 10:53 PM, Olivier Lamy ol...@apache.org wrote: On 30 March

AW: AW: maven-release-plugin / SVN credentials

2015-03-30 Thread Sebastian Oerding
Hello Robert, svn works perfectly fine using the command line or the installed Tortoise SVN or using Subversion. If invoking maven from the command line I do not have to provide credentials (just committed something where a change was sent to the server to verify that). Hence the SVN must take

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Maxim Solodovnik
If I'm not mistaken compiler will not fail in this case BUT the application will fail in runtime (in case Java 1.5 is used) due to StringBuilder class is missing in JDK On Mon, Mar 30, 2015 at 1:20 PM, Lin Ma lin...@gmail.com wrote: Thanks Sebastian, 1. I am using JDK 1.7/1.8 for both

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Thanks Sebastian, In your case #1, I should use 1.5 as target and 1.8 as source in order to use TLS feature and compile class file to be 1.5 compatible? regards, Lin On Mon, Mar 30, 2015 at 12:34 AM, Sebastian Oerding sebastian.oerd...@robotron.de wrote: Hi Lin, 1) In general you should

AW: about source and target in maven-compiler-plugin

2015-03-30 Thread Sebastian Oerding
Hi Lin, 1) In general you should use Java 1.7 / 1.8. However you may have specific requirements which free you from the choice: For example the customer may explicitly request a specific Java version you have to support. Then the class files delivered by you must conform to this Java version

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Thanks Sebastian, 1. I am using JDK 1.7/1.8 for both development and deployment in runtime, shall I change 1.5 of source and target to 1.7/1.8? 2. In your example, for example you can write source code using a JDK 1.6 which is compliant to Java 1.5. However you can also use the StringBuilder

Git / Mercurial repository

2015-03-30 Thread Philipp Kraus
Hello, in my project I would like to use a Mercurial and Git repository of a library, so my project should use the master branch of a repository. Can I add a dependency in my pom.xml, which is point to the master branch of a repository, so on a mvm package / compile the local data is updated?

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Hi Maxim, Why compiler will not fail? Supposing StringBuilder is a class in JDK 1.6, but we force compiler to use 1.5 which has no such class? Please feel free to correct me if I am wrong. regards, Lin On Mon, Mar 30, 2015 at 12:33 AM, Maxim Solodovnik solomax...@gmail.com wrote: If I'm not

AW: about source and target in maven-compiler-plugin

2015-03-30 Thread Sebastian Oerding
source - The level (JDK version) to which the source code must be compliant to, for example you can write source code using a JDK 1.6 which is compliant to Java 1.5. However you can also use the StringBuilder class which does not exist in Java 1.5 target - The class version of the generated

AW: about source and target in maven-compiler-plugin

2015-03-30 Thread Sebastian Oerding
Hi Lin, I just tried my example and Maxim is right. I thought that the source should take the API compatibility into account it seems that it is not this way. Hence if the classes are successfully compiled (which requires a JDK 1.5) and you are executing them with Java 1.5 the StringBuilder

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Thanks all the same Sebastian. Your reply is very helpful and bring us further thoughts. regards, Lin On Mon, Mar 30, 2015 at 12:47 AM, Sebastian Oerding sebastian.oerd...@robotron.de wrote: Hi Lin, I just tried my example and Maxim is right. I thought that the source should take the API

AW: about source and target in maven-compiler-plugin

2015-03-30 Thread Sebastian Oerding
As I felt unfomfortable leaving it as it is I checked http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html where there was the following hint on the target tag: Note: Merely setting the target option does not guarantee that your code actually runs on

Maven and pre-emptive authentication

2015-03-30 Thread James Green
I am a little confused. According to: https://maven.apache.org/guides/mini/guide-http-settings.html Maven 3.0.4 defaults to pre-emptive authentication for HTTP PUTs. According to my haproxy logs, each PUT is done twice: 1. PUT happens, receives a 401 response from Nexus 2. PUT happens,

AW: about source and target in maven-compiler-plugin

2015-03-30 Thread Sebastian Oerding
Finally to finish this I tried a mini maven project containing the following class: package Test; public class Test { public void foo() { System.out.println(new StringBuilder(Hello world!)); assert true; } } Running mvn install gave me

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Thanks Maxim, Good point! I am not sure why Maven makes 1.5 as default, it seems a pretty old version of JDK. regards, Lin On Mon, Mar 30, 2015 at 12:44 AM, Maxim Solodovnik solomax...@gmail.com wrote: Hello Lin, We had this issue in this project: https://github.com/Red5/red5-server Here

AW: about source and target in maven-compiler-plugin

2015-03-30 Thread Sebastian Oerding
pom.xml uses inheritance. There is a so called 'super POM' provided with the maven installation from which all entries are inherited if not added / overwritten by you. Newer versions of Maven have Java 1.6 as default. With regards Sebastian -Ursprüngliche Nachricht- Von: Lin Ma

Running a specific intersection of tests using maven/spring/junit?

2015-03-30 Thread Leo Laskin
I have a number of tests identified using the Spring @IfProfileValue flag @IfProfileValue{a, c} @Test public void testA{ Do Stuff } @IfProfileValue{a, b} @Test public void testB{ Do Stuff } @IfProfileValue{a, b} @Test public void testC{ Do Stuff } @IfProfileValue{b} @Test public void testD{ Do

Re: Maven and pre-emptive authentication

2015-03-30 Thread Gordon Cody
Hello James It really does try twice. The first time it tries with no credentials supplied. This came to our attention when we upgraded from maven-2.0.9 to maven-3.0.5. We found out at that time that it had to do with being compliant to some web specification and there was no way to force it to

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Hi Sebastian, For your comments, Merely setting the target option does not guarantee that your code actually runs on a JRE with the specified version, I think you mean the code still runs on target JRE version as specified in pom.xml, but it will still fail when using a new version of API on an

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Hi Sebastian, The sample is interesting. In your sample, you are using source 1.5 in pom.xml? Thanks. regards, Lin On Mon, Mar 30, 2015 at 1:27 AM, Sebastian Oerding sebastian.oerd...@robotron.de wrote: Finally to finish this I tried a mini maven project containing the following class:

Re: about source and target in maven-compiler-plugin

2015-03-30 Thread Lin Ma
Thanks Sebastian, Where to find the super pom.xml? regards, Lin On Mon, Mar 30, 2015 at 1:18 AM, Sebastian Oerding sebastian.oerd...@robotron.de wrote: pom.xml uses inheritance. There is a so called 'super POM' provided with the maven installation from which all entries are inherited if not