RE: How would I read a non-standard property file?

[Wolfgang Häfelinger]

Jörg Schaible [EMAIL PROTECTED] 
21-04-2005 08:52
Please respond to
Maven Users List users@maven.apache.org




To
Maven Users List users@maven.apache.org
cc

Subject
RE: How would I read a non-standard property file?




Hello,

thanks for the feedback. Will try some proposals and given feedback later.

Cheers,
Wolfgang.

Arik Kfir wrote on Wednesday, April 20, 2005 8:23 PM:

 Jörg Schaible wrote:
 This won't work in general. E.g. a property like maven.repo.remote is
 evaluated before the first goal ever executed. Additionally if you
 load properties, they are nor available in the reactors e.g.
 inherited by the subprojects in multiproject. You'll have to play
 with this. 
 
 If you load your properties into the current context (via the
 properties tag), and then somehow translate that to a Map, you can
 put it into maven's POM context (or plugin context) via
 ${pom.context.setVariables(myMap)} 
 Wouldn't that work?

Try it and give feedback ;-)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How would I read a non-standard property file?

[Wolfgang Häfelinger]

Hello,

I understand that Maven tries to read the files project.properties and 
build.properties on
startup. How would I convince Maven to read other.props?? 

Does a tag like

 properties file=other.props/

or so exists?

I' m very well aware that Maven tries to read build.properties from 
${user.home}. So I could
simply append other.props into my user specific build.properties but 
that that's not what I
want. Basically I want to be able to do something like:

 maven -Dmy.prop.file=other.properties ..

Also, there should be no difference between properties taken from 
other.properties and 
project.properties.

I have the feeling that I can't do this. Am I correct?

Regards.