On 6/15/07, Libor Kramoliš <[EMAIL PROTECTED]> wrote:
Thanks for your answer. But this solution does not satisfy.
It satisfies for the example the gave. If you want to use the properties to specify, for example, a version of another dependency - then you're out of luck, since yes, versions must be resolved before the lifecycle begins. It seems variables (expresions) in pom are resolved earlier than any plugin
is executed. Suggested solution works just for filtering of resources. And also I do not know how to assign such plugin to *site* life-cycle.
bind it to the pre-site phase. Eric Libor
On 6/14/07, Steven Rowe <[EMAIL PROTECTED]> wrote: > > Hi Libor, > > Libor Kramoliš wrote: > > Is it possible to make some properties hook to enhance set of > > properties after pom reading and before starting of first goal > > execution of any lifecycle/phase? > > You could take a look at the source for the properties-maven-plugin, > which injects properties read from files: > > <http://arsenalist.com/2007/02/07/maven-properties-plugin-download/> > > If you bind this (or rahter your version of it) to an early phase, say, > "initialize", it should achieve the desired effect. > > As far as version string parsing, this has to be implemented somewhere > in the Maven source code, since Maven has to do version comparisons all > the time. > > Anybody know in what source module Maven does this kind of decomposition? > > Steve >
-- Eric Redmond http://www.sonatype.com
