We're updating the issue view to help you get more done. 

Set properties for JBoss configuration changes instead of using cargo-specific config files

Description

While looking into using Cargo for setting up dev environments of JBoss, I see that Cargo has some altered config files that are used instead of the default JBoss ones (for a standalone configuration). This is because we use token replacements. One problem that I now run into is that these config files are slightly different from the Jboss default ones. As JBoss supports system property resolution for most configuration I'm wondering if we cannot use that?

One example is the log4j config file where we use token replacement to set the logging level. The JBoss way of doing that would be to set the jboss.server.log.threshold property instead when starting the container.

Status

Assignee

Anders Hammar

Reporter

Anders Hammar

Components

Fix versions

Affects versions

1.0.2

Priority

Major