[
https://issues.apache.org/jira/browse/KARAF-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-1421.
-----------------------------------------
Resolution: Won't Fix
Not sure to understand what you mean. I don't see (but maybe I misunderstood)
any issue on master.
> Remove ${project.version} from POMs
> -----------------------------------
>
> Key: KARAF-1421
> URL: https://issues.apache.org/jira/browse/KARAF-1421
> Project: Karaf
> Issue Type: Task
> Affects Versions: 3.0.0
> Reporter: Brian Topping
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> In situations where a local release of a snapshot must be made (i.e. for
> someone who does not have commit rights and needs to create a version that
> does not get clobbered every time Hudson runs), the use of
> {{$\{project.version\}}} in POMs causes problems. This is because parent
> POMs (and their descendants) will substitute the version of the locally
> released version throughout the ancestor tree, and obviously those versions
> do not exist.
> I can't think of a way around this other than to not use
> {{$\{project.version\}}}. Release plugin should be able to manage this
> properly, no?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
