Pushing systemproperties to remote container

Question

I have a bunch of systemproperties defined in my maven pom.xml, that i need to acccess from Arquillian-tests, running on a remote glassfish instance.

What's the easiest way to push the systemproperties to the container?

Did you get any solution for this ?. Seems to be same as https://stackoverflow.com/questions/26358790/jvm-parameters-not-visible-with-in-arquillian-testcase-on-jboss — Abdul Razak AK, Nov 15 '17 at 12:41

score 4 · Accepted Answer · answered Dec 07 '12 at 10:28

4

There is an Arquillian Extension in the Arquillian Showcase that demo how this could be done 'automatically'.

https://github.com/arquillian/arquillian-showcase/tree/master/extensions/systemproperties

answered Dec 07 '12 at 10:28

Aslak Knutsen

706
3
4

Will this be included into Arquillian? It's an important feature for adding dynamic configurations to the deploy artifact, e.g., a randomly selected port of a mocked dependency – stackoverflower Jul 15 '16 at 09:14
Indeed the arquillian extension systemproperties actually uses some classes into main/java. The ideal situation would be to include it into Arquillian – Fabrizio Stellato Oct 14 '16 at 08:34

score 2 · Answer 2 · answered Dec 06 '12 at 10:53

You could write these properties out to a file that is added to your ShrinkWrap @Deployment.

You could then read this file in your @Before setup method that executes server-side, and set the System properties using System.setProperty(...). This assumes the SecurityManager on the server will allow you to set the properties.

If you don't want to pollute your test code with all of this, you could write this harness into an Arquillian extension that does something similar.

Pushing systemproperties to remote container

2 Answers2