"jmesnil" wrote:

src/config/non-clustered -> beans and configuration for (non-clustered) standalone
src/config/clustered -> beans and configuration for clustered standalone
src/config/jbossas/non-clustered/ -> beans for (non-clustered) AS 5 integration
src/config/jbossas/clustered -> beans for clustered AS 5 integration

For jbas, there is some stuff that could go on either clustered or non-clustered.

Shouldt we have a common dir?

I want to keep the configs completely separate.

Even if some things are the same now, such as beans files, they might not be in the future, and using a common dir just complicates things and makes them harder to change going ahead.

Is it possible that we just keep a single set of template configuration files and whoever needs a specific configuration could 'generate' it from the template?

We can consider 'velocity' for that purpose. or use ant filtered copy task.

There is a saying in Brazil that translates my feeling:

"The dog bitten by a snake fears sausage".


I had personally had hassles while handling auto-generated scripts based on a common template. At the end it took the team I was working at, more time to maintain the messy script than maintaining a few copies.


I could be a different experience now (Hence my reference to the brazilian saying)... but I feel a Dejavou when thinking about scripts like that.

That's true. :)

Chinese has a similar one, in English like:

Once got bitten by a snake, one will fear rope for ten years.

I have a saying:

"Developer who's task takes too long gets ass kicked by project lead".

And one specially for Clebert:

"Clebert gets ass kicked anyway"

;)