You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Brian Topping (JIRA)" <ji...@apache.org> on 2012/04/27 22:30:50 UTC
[jira] [Created] (KARAF-1421) Remove ${project.version} from POMs
Brian Topping created KARAF-1421:
------------------------------------
Summary: 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
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1421) Remove ${project.version} from POMs
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264568#comment-13264568 ]
Andreas Pieber commented on KARAF-1421:
---------------------------------------
sounds good to me. Feel free to provide a patch.
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-1421) Remove ${project.version} from POMs
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-1421:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira