Wolfgang H�felinger wrote on Wednesday, April 20, 2005 5:55 PM:
> 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?
Yes, can't remember by heart, but definately yes. Look into genapp's Jelly code.
> 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".
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.
> I have the feeling that I can't do this. Am I correct?
All this might work if you write a plugin though. But you have to investigate
on your own ... can't say much about scope and evaluation time. You have to
investigate with a little sample :)
- J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
