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 mu
And what about Maven ? What is extension? Does it implement any
interface? What is contract for extensions? Is it executed during each maven
run (e.g. install, clean , site)? Is it possible to get instance of current
MavenProject?
It looks I need something Maven was designed for. Or am I thinking
Thanks for your answer. But this solution does not satisfy.
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.
Libor
On 6/14/07
Scratch that - I see it has a compareTo all nice and built in ;-)
On 6/15/07, Mark Derricutt <[EMAIL PROTECTED]> wrote:
Excellent - I was about to ask something similar for another project I'm
working on. Not having looked at maven-artifact yet I suppose theres
support utils/methods for sortin
Excellent - I was about to ask something similar for another project I'm
working on. Not having looked at maven-artifact yet I suppose theres
support utils/methods for sorting and determining which version is higher in
here?
*hunts out javadoc*
On 6/15/07, Eric Redmond <[EMAIL PROTECTED]> wrote
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 pr
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 f
Hello.
I would like to get to single version numbers of whole artifact version, i.e.
I would like to parse ${pom.version} and store each number in different
property, e.g. ${version.major}, ${version.middle}, ${version.minor} or more
generally: ${pom.versions[0], ${pom.versions[1], etc.
Reason?