You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Zoltan Haindrich (JIRA)" <ji...@apache.org> on 2017/05/19 14:37:04 UTC
[jira] [Updated] (MNG-6237) Property value during the same build
should not change
[ https://issues.apache.org/jira/browse/MNG-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltan Haindrich updated MNG-6237:
----------------------------------
Description:
I've encountered this problem in HIVE-14289.
But now I know more...and I think I probably understand what's going on.
Long story short, I would like to override some project property to use a different version of a dependency...however using
{code}
mvn install -Dhadoop.version=2.8.0
{code}
is not enough...that's what I've found out in that ticket.
The problem is:
* root project defines a property {{junit.version}}
* there is a lib project which pulls in a dependency with that property
* there is an app module which tries to use the lib in some way
in this setup even thru the developer would like to override the version of {{junit.version}}, he can't really do it; because maven references to it anyway.
I've created a samle project in which the root project contains a malformed version number; and in case it tries to use it, will end up with an artifact resolution error.
I'm not sure if the problem is within maven or in some of its plugins...
sample project:
https://github.com/kgyrtkirk/mng-6237
sample output:
https://api.travis-ci.org/jobs/234037973/log.txt?deansi=true
was:
I've encountered this problem in HIVE-14289.
But now I know more...and I think I probably understand what's going on.
Long story short, I would like to override some project property to use a different version of a dependency...however using
{code}
mvn install -Dhadoop.version=2.8.0
{code}
is not enough...that's what I've found out in that ticket.
The problem is:
* root project defines a property {{junit.version}}
* there is a lib project which pulls in a dependency with that property
* there is an app module which tries to use the lib in some way
in this setup even thru the developer would like to override the version of {{junit.version}}, he can't really do it; because maven references to it anyway.
I've created a samle project in which the root project contains a malformed version number; and in case it tries to use it, will end up with an artifact resolution error.
I'm not sure if the problem is within maven or in some of its plugins...
> Property value during the same build should not change
> ------------------------------------------------------
>
> Key: MNG-6237
> URL: https://issues.apache.org/jira/browse/MNG-6237
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.3
> Reporter: Zoltan Haindrich
>
> I've encountered this problem in HIVE-14289.
> But now I know more...and I think I probably understand what's going on.
> Long story short, I would like to override some project property to use a different version of a dependency...however using
> {code}
> mvn install -Dhadoop.version=2.8.0
> {code}
> is not enough...that's what I've found out in that ticket.
> The problem is:
> * root project defines a property {{junit.version}}
> * there is a lib project which pulls in a dependency with that property
> * there is an app module which tries to use the lib in some way
> in this setup even thru the developer would like to override the version of {{junit.version}}, he can't really do it; because maven references to it anyway.
> I've created a samle project in which the root project contains a malformed version number; and in case it tries to use it, will end up with an artifact resolution error.
> I'm not sure if the problem is within maven or in some of its plugins...
> sample project:
> https://github.com/kgyrtkirk/mng-6237
> sample output:
> https://api.travis-ci.org/jobs/234037973/log.txt?deansi=true
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)