You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jason Chaffee <jc...@ebates.com> on 2010/10/10 02:18:41 UTC
${version} in 3.0
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: ${version} in 3.0
Posted by Jason Chaffee <jc...@ebates.com>.
Nowhere. Searched my entire search tree. It cannot be found in any file.
-----Original Message-----
From: Niall Pemberton [mailto:niall.pemberton@gmail.com]
Sent: Sat 10/9/2010 5:35 PM
To: Maven Users List
Subject: Re: ${version} in 3.0
On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee <jc...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ${version} in 3.0
Posted by Stevo Slavić <ss...@gmail.com>.
Try help:effective-pom<http://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html>
Regards,
Stevo.
On Sun, Oct 10, 2010 at 11:15 PM, Jason Chaffee <jc...@ebates.com> wrote:
> I do have properties like this though:
>
> <spring.version>
>
> that I then use ${spring.version}
>
>
> -----Original Message-----
> From: Jason Chaffee [mailto:jchaffee@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:msa@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 <jc...@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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: ${version} in 3.0
Posted by Jason Chaffee <jc...@ebates.com>.
I have not checked my local. I will do that.
Yes, giving the location would be very helpful. It does seem to give the location for other errors/warnings, but not this one.
-----Original Message-----
From: Brett Porter on behalf of Brett Porter
Sent: Sun 10/10/2010 5:27 PM
To: Maven Users List
Subject: Re: ${version} in 3.0
It sounds like the warning in Maven needs to be updated to show the location.
Did you check your local repository as well?
On 11/10/2010, at 8:15 AM, Jason Chaffee wrote:
> I do have properties like this though:
>
> <spring.version>
>
> that I then use ${spring.version}
>
>
> -----Original Message-----
> From: Jason Chaffee [mailto:jchaffee@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:msa@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 <jc...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ${version} in 3.0
Posted by Brett Porter <br...@apache.org>.
It sounds like the warning in Maven needs to be updated to show the location.
Did you check your local repository as well?
On 11/10/2010, at 8:15 AM, Jason Chaffee wrote:
> I do have properties like this though:
>
> <spring.version>
>
> that I then use ${spring.version}
>
>
> -----Original Message-----
> From: Jason Chaffee [mailto:jchaffee@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:msa@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 <jc...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: ${version} in 3.0
Posted by Jason Chaffee <jc...@ebates.com>.
I do have properties like this though:
<spring.version>
that I then use ${spring.version}
-----Original Message-----
From: Jason Chaffee [mailto:jchaffee@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:msa@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 <jc...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: ${version} in 3.0
Posted by Jason Chaffee <jc...@ebates.com>.
checked every file. It does no exist anywhere.
-----Original Message-----
From: Marshall Schor [mailto:msa@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 <jc...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ${version} in 3.0
Posted by Marshall Schor <ms...@schor.com>.
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 <jc...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ${version} in 3.0
Posted by Niall Pemberton <ni...@gmail.com>.
On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee <jc...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: ${version} in 3.0
Posted by Brian Fox <br...@infinity.nu>.
Perhaps some -X debug output would help track down where this comes
from. If it's coming from processing of a dependency's pom, then I
would say that you should file a bug report since warning about a pom
you can't control just makes this noise and will cause people to
ignore valid warnings.
On Sat, Oct 9, 2010 at 8:18 PM, Jason Chaffee <jc...@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.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org