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:
>
>
>
> that I then use $
t; -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-
> Fr
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 Sa
--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-
> F
I do have properties like this though:
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
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:
>
Nowhere. Searched my entire search tree. It cannot be found in any file.
-Original Message-
From: Niall Pemberton [mailto:niall.pember...@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 wrote
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 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 the
On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee 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.
>
>
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
10 matches
Mail list logo
