re. Étant
donné que les email peuvent facilement être sujets à la manipulation, nous ne
pouvons accepter aucune responsabilité pour le contenu fourni.
> From: baris...@w.cn
> To: dev@maven.apache.org
> Subject: About Maven3 M2Eclipse Plug-in Versioning Problem
> Date: Mon, 1
No worries... though I need to call a vote to get a 3.0-beta-1 compatible
version published
2010/5/17 Benjamin Bentmann
> Barışcan Güngör wrote:
>
> [...] we
>>
>> could specify a variable for the application version in the parent pom, so
>> that
>> in the child poms we could able to specify th
Barışcan Güngör wrote:
[...] we
could specify a variable for the application version in the parent pom, so that
in the child poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
Oh
You were relying on a bug.
the following xpath:/project/parent/groupId,
xpath:/project/parent/artifactId, xpath:/project/parent/version,
xpath:/project/groupId, xpath:/project/artifactId, xpath:/project/version
cannot ever reference a property as they are all evaluated before the model
is availabl
Barışcan Güngör wrote:
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”.
A POM deployed to a repository must be self-contained in the way that
all information required to process it (e.g. calculate the effective
POM) mus
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2 we
could specify a variable for the application version in the parent pom, so that
in the child
