|
I'm currently using the conf profiles to keep
different projects
and versions separate, but all the beans still go to the shared
deploy directory,
which means I need to blow away one
project's jars before starting another.
Is there something I'm missing that's meant to
address this?
If not, has there been any thought of supporting a
more WL-
style directory structure where a particular
configuration
profile can be linked to its own deploy directory and server
classes?
Erin
|
- Re: [JBoss-user] Managing multiple deploy sets Erin Mulder
- Re: [JBoss-user] Managing multiple deploy sets Erin Mulder
- Re: [JBoss-user] Managing multiple deploy sets David Jencks
