|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
20/Jun/04 01:53 PM
|
|
<jboss3x> container does not support "external" JBoss configurations. It'll always look for them under [jbosshome]/server/. This is especially a problem for the maven cactus plugin because the maven JBoss plugin creates a custom, "external" jboss configuration for each maven project. It would be useful if the maven cactus plugin could be configured to point at this directory.
Hence, a maven cactus plugin property is needed which allows for the specification of the JBoss configuration directory in addition to the configuration name.
|
|
Description
|
<jboss3x> container does not support "external" JBoss configurations. It'll always look for them under [jbosshome]/server/. This is especially a problem for the maven cactus plugin because the maven JBoss plugin creates a custom, "external" jboss configuration for each maven project. It would be useful if the maven cactus plugin could be configured to point at this directory.
Hence, a maven cactus plugin property is needed which allows for the specification of the JBoss configuration directory in addition to the configuration name.
|
Show » |
| No work has yet been logged on this issue.
|
|
Improvement
Closed
Major
<jboss3x> container does not support "external" configurations
