You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Pop Qvarnström <po...@gmail.com> on 2015/02/25 14:17:48 UTC
Cannot find deprecated expressions reported by maven
Hi,
I've searched the best I can, but have not been able to find a solution.
When running maven 3 to build an older project I get what seems like
self-explanatory warnings:
"[WARNING] The expression ${artifactId} is deprecated. Please use
${project.artifactId} instead." and
"[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead."
Problem: I cannot find a single instance of either of the expressions in
any of my pom files. Even the effective pom generated by running "mvn
help:effective-pom" contains no instances of either expression. How can I
fix whatever is causing these warnings? Any help appreciated.
Kind regards,
Pop Qvarnström
Re: Cannot find deprecated expressions reported by maven
Posted by Pop Qvarnström <po...@gmail.com>.
OT: It is! (Noticed the sig as soon as I hit send, i.e. as soon as it was
to late to remove.) Thanks again!
Cheers,
Pop
2015-02-25 15:46 GMT+01:00 Anders Hammar <an...@hammar.net>:
> > Tried without dependencies, to no avail. However, when that made no
> > difference, I started searching the local repo and found a grandparent
> pom
> > using these expressions.
>
>
> Ok, great that you found the issue. Thinking harder I don't think Maven
> would warn about this type of issues in dependencies.
>
> /Anders
>
> PS. I guess Falun is a good place to be today (and yesterday)...:-)
>
>
> > Searching in files based on extensions (*.xml)
> > made me miss that one during the first round, since it is named .pom.
> > Effective pom shows (which seems reasonable, when you think about it) the
> > values, not the expressions. Doh.
> >
> > Thanks for your help!
> >
> > /Pop
> >
> >
> >
> ------------------------------------------------------------------------------------------------
> > *Ju-jutsu i Falun! Kom och träna! *
> > *Vi tar emot nybörjare löpande - oömma kläder är allt du behöver!*
> > *Vuxna (15-150 år):* tisdagar 19-20, torsdagar 18-19
> > *Barn (9-14 år):* torsdagar 17-18.
> > *Knattar (6-8 år):* torsdagar 17-18.
> > https://www.facebook.com/groups/falujjk/
> > http://falujjk.se/
> > info@falujjk.se
> > 0709-390614
> >
> >
> ------------------------------------------------------------------------------------------------
> >
> > Gammal husblogg: popochjennybyggerhus.blogspot.com
> >
> > Tekniktråk och lite annat (typ mat): popq.se
> >
> >
> >
> > 2015-02-25 14:44 GMT+01:00 Anders Hammar <an...@hammar.net>:
> >
> > > It could be interesting to know if that is the reason. Try removing the
> > > dependencies and see if Maven still complains.
> > >
> > > /Anders
> > >
> > > On Wed, Feb 25, 2015 at 2:34 PM, Pop Qvarnström <
> > pop.qvarnstrom@gmail.com>
> > > wrote:
> > >
> > > > If maven warns for dependencies I'm good, did - for no good reason -
> > not
> > > > think that was the case. Thanks.
> > > >
> > > > Slightly edited console output before, including and after warnings:
> > > >
> > > > [INFO] Scanning for projects...
> > > > [WARNING]
> > > > [WARNING] Some problems were encountered while building the effective
> > > model
> > > > for <myproject>
> > > > [WARNING] 'build.plugins.plugin.version' for
> > > > org.apache.maven.plugins:maven-ejb-plugin is missing. @ <line no etc>
> > > > [WARNING] The expression ${artifactId} is deprecated. Please use
> > > > ${project.artifactId} instead.
> > > > [WARNING] The expression ${version} is deprecated. Please use
> > > > ${project.version} instead.
> > > > [WARNING]
> > > > [WARNING] It is highly recommended to fix these problems because they
> > > > threaten the stability of your build.
> > > > [WARNING]
> > > > [WARNING] For this reason, future Maven versions might no longer
> > support
> > > > building such malformed projects.
> > > > [WARNING]
> > > >
> > > > /Pop
> > > >
> > > > 2015-02-25 14:27 GMT+01:00 Anders Hammar <an...@hammar.net>:
> > > >
> > > > > Could it be that it declared in one of your dependencies? Just a
> > guess
> > > > as I
> > > > > don't know if Maven warns for that or not.
> > > > >
> > > > > What are the console output just before and after these two
> warnings?
> > > > >
> > > > > /Anders
> > > > >
> > > > > On Wed, Feb 25, 2015 at 2:17 PM, Pop Qvarnström <
> > > > pop.qvarnstrom@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I've searched the best I can, but have not been able to find a
> > > > solution.
> > > > > > When running maven 3 to build an older project I get what seems
> > like
> > > > > > self-explanatory warnings:
> > > > > >
> > > > > > "[WARNING] The expression ${artifactId} is deprecated. Please use
> > > > > > ${project.artifactId} instead." and
> > > > > > "[WARNING] The expression ${version} is deprecated. Please use
> > > > > > ${project.version} instead."
> > > > > >
> > > > > > Problem: I cannot find a single instance of either of the
> > expressions
> > > > in
> > > > > > any of my pom files. Even the effective pom generated by running
> > "mvn
> > > > > > help:effective-pom" contains no instances of either expression.
> How
> > > > can I
> > > > > > fix whatever is causing these warnings? Any help appreciated.
> > > > > >
> > > > > > Kind regards,
> > > > > > Pop Qvarnström
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Cannot find deprecated expressions reported by maven
Posted by Anders Hammar <an...@hammar.net>.
> Tried without dependencies, to no avail. However, when that made no
> difference, I started searching the local repo and found a grandparent pom
> using these expressions.
Ok, great that you found the issue. Thinking harder I don't think Maven
would warn about this type of issues in dependencies.
/Anders
PS. I guess Falun is a good place to be today (and yesterday)...:-)
> Searching in files based on extensions (*.xml)
> made me miss that one during the first round, since it is named .pom.
> Effective pom shows (which seems reasonable, when you think about it) the
> values, not the expressions. Doh.
>
> Thanks for your help!
>
> /Pop
>
>
> ------------------------------------------------------------------------------------------------
> *Ju-jutsu i Falun! Kom och träna! *
> *Vi tar emot nybörjare löpande - oömma kläder är allt du behöver!*
> *Vuxna (15-150 år):* tisdagar 19-20, torsdagar 18-19
> *Barn (9-14 år):* torsdagar 17-18.
> *Knattar (6-8 år):* torsdagar 17-18.
> https://www.facebook.com/groups/falujjk/
> http://falujjk.se/
> info@falujjk.se
> 0709-390614
>
> ------------------------------------------------------------------------------------------------
>
> Gammal husblogg: popochjennybyggerhus.blogspot.com
>
> Tekniktråk och lite annat (typ mat): popq.se
>
>
>
> 2015-02-25 14:44 GMT+01:00 Anders Hammar <an...@hammar.net>:
>
> > It could be interesting to know if that is the reason. Try removing the
> > dependencies and see if Maven still complains.
> >
> > /Anders
> >
> > On Wed, Feb 25, 2015 at 2:34 PM, Pop Qvarnström <
> pop.qvarnstrom@gmail.com>
> > wrote:
> >
> > > If maven warns for dependencies I'm good, did - for no good reason -
> not
> > > think that was the case. Thanks.
> > >
> > > Slightly edited console output before, including and after warnings:
> > >
> > > [INFO] Scanning for projects...
> > > [WARNING]
> > > [WARNING] Some problems were encountered while building the effective
> > model
> > > for <myproject>
> > > [WARNING] 'build.plugins.plugin.version' for
> > > org.apache.maven.plugins:maven-ejb-plugin is missing. @ <line no etc>
> > > [WARNING] The expression ${artifactId} is deprecated. Please use
> > > ${project.artifactId} instead.
> > > [WARNING] The expression ${version} is deprecated. Please use
> > > ${project.version} instead.
> > > [WARNING]
> > > [WARNING] It is highly recommended to fix these problems because they
> > > threaten the stability of your build.
> > > [WARNING]
> > > [WARNING] For this reason, future Maven versions might no longer
> support
> > > building such malformed projects.
> > > [WARNING]
> > >
> > > /Pop
> > >
> > > 2015-02-25 14:27 GMT+01:00 Anders Hammar <an...@hammar.net>:
> > >
> > > > Could it be that it declared in one of your dependencies? Just a
> guess
> > > as I
> > > > don't know if Maven warns for that or not.
> > > >
> > > > What are the console output just before and after these two warnings?
> > > >
> > > > /Anders
> > > >
> > > > On Wed, Feb 25, 2015 at 2:17 PM, Pop Qvarnström <
> > > pop.qvarnstrom@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I've searched the best I can, but have not been able to find a
> > > solution.
> > > > > When running maven 3 to build an older project I get what seems
> like
> > > > > self-explanatory warnings:
> > > > >
> > > > > "[WARNING] The expression ${artifactId} is deprecated. Please use
> > > > > ${project.artifactId} instead." and
> > > > > "[WARNING] The expression ${version} is deprecated. Please use
> > > > > ${project.version} instead."
> > > > >
> > > > > Problem: I cannot find a single instance of either of the
> expressions
> > > in
> > > > > any of my pom files. Even the effective pom generated by running
> "mvn
> > > > > help:effective-pom" contains no instances of either expression. How
> > > can I
> > > > > fix whatever is causing these warnings? Any help appreciated.
> > > > >
> > > > > Kind regards,
> > > > > Pop Qvarnström
> > > > >
> > > >
> > >
> >
>
Re: Cannot find deprecated expressions reported by maven
Posted by Pop Qvarnström <po...@gmail.com>.
Tried without dependencies, to no avail. However, when that made no
difference, I started searching the local repo and found a grandparent pom
using these expressions. Searching in files based on extensions (*.xml)
made me miss that one during the first round, since it is named .pom.
Effective pom shows (which seems reasonable, when you think about it) the
values, not the expressions. Doh.
Thanks for your help!
/Pop
------------------------------------------------------------------------------------------------
*Ju-jutsu i Falun! Kom och träna! *
*Vi tar emot nybörjare löpande - oömma kläder är allt du behöver!*
*Vuxna (15-150 år):* tisdagar 19-20, torsdagar 18-19
*Barn (9-14 år):* torsdagar 17-18.
*Knattar (6-8 år):* torsdagar 17-18.
https://www.facebook.com/groups/falujjk/
http://falujjk.se/
info@falujjk.se
0709-390614
------------------------------------------------------------------------------------------------
Gammal husblogg: popochjennybyggerhus.blogspot.com
Tekniktråk och lite annat (typ mat): popq.se
2015-02-25 14:44 GMT+01:00 Anders Hammar <an...@hammar.net>:
> It could be interesting to know if that is the reason. Try removing the
> dependencies and see if Maven still complains.
>
> /Anders
>
> On Wed, Feb 25, 2015 at 2:34 PM, Pop Qvarnström <po...@gmail.com>
> wrote:
>
> > If maven warns for dependencies I'm good, did - for no good reason - not
> > think that was the case. Thanks.
> >
> > Slightly edited console output before, including and after warnings:
> >
> > [INFO] Scanning for projects...
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> model
> > for <myproject>
> > [WARNING] 'build.plugins.plugin.version' for
> > org.apache.maven.plugins:maven-ejb-plugin is missing. @ <line no etc>
> > [WARNING] The expression ${artifactId} is deprecated. Please use
> > ${project.artifactId} instead.
> > [WARNING] The expression ${version} is deprecated. Please use
> > ${project.version} instead.
> > [WARNING]
> > [WARNING] It is highly recommended to fix these problems because they
> > threaten the stability of your build.
> > [WARNING]
> > [WARNING] For this reason, future Maven versions might no longer support
> > building such malformed projects.
> > [WARNING]
> >
> > /Pop
> >
> > 2015-02-25 14:27 GMT+01:00 Anders Hammar <an...@hammar.net>:
> >
> > > Could it be that it declared in one of your dependencies? Just a guess
> > as I
> > > don't know if Maven warns for that or not.
> > >
> > > What are the console output just before and after these two warnings?
> > >
> > > /Anders
> > >
> > > On Wed, Feb 25, 2015 at 2:17 PM, Pop Qvarnström <
> > pop.qvarnstrom@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I've searched the best I can, but have not been able to find a
> > solution.
> > > > When running maven 3 to build an older project I get what seems like
> > > > self-explanatory warnings:
> > > >
> > > > "[WARNING] The expression ${artifactId} is deprecated. Please use
> > > > ${project.artifactId} instead." and
> > > > "[WARNING] The expression ${version} is deprecated. Please use
> > > > ${project.version} instead."
> > > >
> > > > Problem: I cannot find a single instance of either of the expressions
> > in
> > > > any of my pom files. Even the effective pom generated by running "mvn
> > > > help:effective-pom" contains no instances of either expression. How
> > can I
> > > > fix whatever is causing these warnings? Any help appreciated.
> > > >
> > > > Kind regards,
> > > > Pop Qvarnström
> > > >
> > >
> >
>
Re: Cannot find deprecated expressions reported by maven
Posted by Anders Hammar <an...@hammar.net>.
It could be interesting to know if that is the reason. Try removing the
dependencies and see if Maven still complains.
/Anders
On Wed, Feb 25, 2015 at 2:34 PM, Pop Qvarnström <po...@gmail.com>
wrote:
> If maven warns for dependencies I'm good, did - for no good reason - not
> think that was the case. Thanks.
>
> Slightly edited console output before, including and after warnings:
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for <myproject>
> [WARNING] 'build.plugins.plugin.version' for
> org.apache.maven.plugins:maven-ejb-plugin is missing. @ <line no etc>
> [WARNING] The expression ${artifactId} is deprecated. Please use
> ${project.artifactId} instead.
> [WARNING] The expression ${version} is deprecated. Please use
> ${project.version} instead.
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
>
> /Pop
>
> 2015-02-25 14:27 GMT+01:00 Anders Hammar <an...@hammar.net>:
>
> > Could it be that it declared in one of your dependencies? Just a guess
> as I
> > don't know if Maven warns for that or not.
> >
> > What are the console output just before and after these two warnings?
> >
> > /Anders
> >
> > On Wed, Feb 25, 2015 at 2:17 PM, Pop Qvarnström <
> pop.qvarnstrom@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I've searched the best I can, but have not been able to find a
> solution.
> > > When running maven 3 to build an older project I get what seems like
> > > self-explanatory warnings:
> > >
> > > "[WARNING] The expression ${artifactId} is deprecated. Please use
> > > ${project.artifactId} instead." and
> > > "[WARNING] The expression ${version} is deprecated. Please use
> > > ${project.version} instead."
> > >
> > > Problem: I cannot find a single instance of either of the expressions
> in
> > > any of my pom files. Even the effective pom generated by running "mvn
> > > help:effective-pom" contains no instances of either expression. How
> can I
> > > fix whatever is causing these warnings? Any help appreciated.
> > >
> > > Kind regards,
> > > Pop Qvarnström
> > >
> >
>
Re: Cannot find deprecated expressions reported by maven
Posted by Pop Qvarnström <po...@gmail.com>.
If maven warns for dependencies I'm good, did - for no good reason - not
think that was the case. Thanks.
Slightly edited console output before, including and after warnings:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for <myproject>
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-ejb-plugin is missing. @ <line no etc>
[WARNING] The expression ${artifactId} is deprecated. Please use
${project.artifactId} instead.
[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead.
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
/Pop
2015-02-25 14:27 GMT+01:00 Anders Hammar <an...@hammar.net>:
> Could it be that it declared in one of your dependencies? Just a guess as I
> don't know if Maven warns for that or not.
>
> What are the console output just before and after these two warnings?
>
> /Anders
>
> On Wed, Feb 25, 2015 at 2:17 PM, Pop Qvarnström <po...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I've searched the best I can, but have not been able to find a solution.
> > When running maven 3 to build an older project I get what seems like
> > self-explanatory warnings:
> >
> > "[WARNING] The expression ${artifactId} is deprecated. Please use
> > ${project.artifactId} instead." and
> > "[WARNING] The expression ${version} is deprecated. Please use
> > ${project.version} instead."
> >
> > Problem: I cannot find a single instance of either of the expressions in
> > any of my pom files. Even the effective pom generated by running "mvn
> > help:effective-pom" contains no instances of either expression. How can I
> > fix whatever is causing these warnings? Any help appreciated.
> >
> > Kind regards,
> > Pop Qvarnström
> >
>
Re: Cannot find deprecated expressions reported by maven
Posted by Anders Hammar <an...@hammar.net>.
Could it be that it declared in one of your dependencies? Just a guess as I
don't know if Maven warns for that or not.
What are the console output just before and after these two warnings?
/Anders
On Wed, Feb 25, 2015 at 2:17 PM, Pop Qvarnström <po...@gmail.com>
wrote:
> Hi,
>
> I've searched the best I can, but have not been able to find a solution.
> When running maven 3 to build an older project I get what seems like
> self-explanatory warnings:
>
> "[WARNING] The expression ${artifactId} is deprecated. Please use
> ${project.artifactId} instead." and
> "[WARNING] The expression ${version} is deprecated. Please use
> ${project.version} instead."
>
> Problem: I cannot find a single instance of either of the expressions in
> any of my pom files. Even the effective pom generated by running "mvn
> help:effective-pom" contains no instances of either expression. How can I
> fix whatever is causing these warnings? Any help appreciated.
>
> Kind regards,
> Pop Qvarnström
>