I don’t think this is a problem in either Maven or Surefire plug-in. Else the surefire is behaving differently. It looks like now, when Surefire forks the JVM, will not take all the system properties from the parent JVM. That’s why you should pass whatever system properties you want for the tests, using argLine. So, … Read more
Environment variables are specific to the operating system. Properties are JVM only.
You may try. @Profile(“production”) @Component public class ProductionPropertySetter { @PostConstruct public void setProperty() { System.setProperty(“http.maxConnections”, “15”); } }
Scope of the System properties At least from reading the API Specifications for the System.setProperties method, I was unable to get an answer whether the system properties are shared by all instances of the JVM or not. In order to find out, I wrote two quick programs that will set the system property via System.setProperty, … Read more
In IntelliJ it works as follows: Go to configurations -> VM options and add the parameter/value pair: -DmyParameter=value Make sure you add a “D” after the “-“!
You will need InternetExplorer driver executable on your system. So download it from the hinted source (http://www.seleniumhq.org/download/) unpack it and place somewhere you can find it. In my example, I will assume you will place it to C:\Selenium\iexploredriver.exe Then you have to set it up in the system. Here is the Java code pasted from … Read more
Is there a way ( I mean how do I ) set a system property in a maven project? I want to access a property from my test […] You can set system properties in the Maven Surefire Plugin configuration (this makes sense since tests are forked by default). From Using System Properties: <project> […] … Read more
Answer is NO. You might have seen an example where somebody would have set something like : -DArguments=a=1,b=2,c=3,d=4,e=cow Then the application would parse value of Arguments property string to get individual values. In your main you can get the key values as(Assuming input format is guaranteed): String line = System.getProperty(“Arguments”); if(line != null) { String … Read more
cliff.meyers‘s original answer that suggested using <env-entry> will not help when using only System.getProperty() According to the Tomcat 6.0 docs <env-entry> is for JNDI. So that means it won’t have any effect on System.getProperty(). With the <env-entry> from cliff.meyers‘s example, the following code System.getProperty(“SMTP_PASSWORD”); will return null, not the value “abc123ftw”. According to the Tomcat … Read more