I have this same need. OK, it's a little different, but it's still
the hibernate.properties issue (in my case, JNDI name is directly
associated with the artifact version). Also, since I have to deploy
to two different OS platforms (Win and Linux), I need to change
pathing information in a variety of places.
The proposed properties filter plugin does sound like a winner. If it
works the way I think you're describing, it sounds like it would
totally trivialize my issues.
I could define base level property (like build.OS=win ) and have
references to that be substituted throughout my filtering (
datasources locations could then be
build.OS=win
datasource.url.win=C:\windatasourceloc\myHSQLdb
datasource.url.linux=/opt/lindatasource/myHSQLdb
datasource.url=${datasource.url.${build.OS}
and then filter for ${datasource.url}. This didn't work for me in
maven1, and I really never expected it to. The filtering probably
won't work very much like that, but the effect might be the same.
Unfortunately, I'm probably stuck with m1 for all practical purposes.
Oddly enough, most enterprise managers dont' seem exactly eager to
jump at alpha software. :)
On 4/12/05, John Casey <[EMAIL PROTECTED]> wrote some stuff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
