Good evening,
In this discussion, I would like to make a feature request that affects JBoss 7 deployment via the console.
At the moment, it is possible to deploy Java Applications using the console via the following command:
deploy C:\path\to\application --name="" --runtime-name=""
When providing a runtime-name, the application will be known by that name. This is important for example when defining dependencies in the jboss-deployment-structure.xml (we have automated the creation of that file to some degree and thus need consistent names for a deployment), because they are referenced against the runtime-name.
It is possible to define the following:
Approach A:
deploy C:\path\to\applicationA-1.0.0.jar --name=application-A-1.0.0.jar --runtime-name=application-A.jar
deploy C:\path\to\applicationA-1.0.1.jar --name=application-A-1.0.1.jar --runtime-name=application-A.jar
now, both modules are deployed and started ("enabled" is set to true), but I don't know which of them is used when a third deployment has a dependency to the application-A.jar. When writing the following:
Approach B:
deploy C:\path\to\applicationA-1.0.0.jar --name=application-A.jar
deploy C:\path\to\applicationA-1.0.1.jar --name=application-A.jar --force
it would work because the first deployment is overriden. However, the problem is that we lose the version information!
I would like to have a third option, some kind of human-readable description of a deployment. It could look like this:
Approach C:
deploy C:\path\to\applicationA-1.0.0.jar --name=application-A.jar --description=application-A-1.0.0.jar
deploy C:\path\to\applicationA-1.0.1.jar --name=application-A.jar --description=application-A-1.0.0.jar --force
With it, we would circumvent the problem we have when using the Approach A, but still contain version information.
Please let me know what you think of this or if I misunderstand some of the deployment processes.
Regards,
Sven
