Hi. I am using maven cargo plugin to manage my JBoss 7 container. It works well, but when I try to change ports, I get a problem. The management default port (9999) and the remoting default port (4447) aren't changed.
I edit the standalone.xml file to use different ports, I set jvmargs in cargo to force use of this file (-Djboss.server.default.config=standalone.xml). But still nothing. Then I see that cargo makes it's own copy of the standalone.xml file that is used to start the container. The standalone.xml file I make lokks like this: But, the file that cargo uses, that is copied (I guess) to target/cargo/configurations/jboss71x looks like this: Why does cargo overwrite certain fields? Any way to force cargo not to do this? I know there is a "cargo.servlet.port" property, but is there one for the others? Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Question-about-maven-cargo-plugin-tp5635408p5635408.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
