I do have properties like this though:

<spring.version>

that I then use ${spring.version}


-----Original Message-----
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Sun 10/10/2010 2:12 PM
To: Maven Users List; Maven Users List
Subject: RE: ${version} in 3.0
 
checked every file.  It does no exist anywhere.


-----Original Message-----
From: Marshall Schor [mailto:m...@schor.com]
Sent: Sat 10/9/2010 7:18 PM
To: Maven Users List
Subject: Re: ${version} in 3.0
 
 also check parent poms.

-Marshall Schor

On 10/9/2010 8:35 PM, Niall Pemberton wrote:
> On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee <jchaf...@ebates.com> wrote:
>> I am getting this warning for every module, yet I am not using this variable 
>> any of the poms.  Some poms do have ${project.version} but some of them 
>> don't have any variable expressions at all and it is still outputting this 
>> warning.
>>
>> Does this warning just get output regardless of what is the the pom?
>>
>> [WARNING] The expression ${version} is deprecated. Please use 
>> ${project.version} instead.
> What about other places like assembly plugin config files?
>
> Niall
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to