[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757399#action_12757399
]
Kristian Waagan commented on DERBY-4267:
----------------------------------------
Hi m,
The placeholder will only exist in Derby's source code repository.
When a release is cut, it will be replaced by a specific Derby version number -
for instance 10.5.3.0.
The only purpose of the placeholder is to make it easier for the person
generating the Maven artifacts to do a search and replace to insert the correct
version number.
There are quite a few POMs, and doing it manually is a bit tedious.
The process above is generally what I would have expected the Maven install
plugin to do, using the ${derby.version} variable.
Instead of a placeholder, maybe we could just the current version number, but
it may incur a little extra work as we generate release candidates (that we
don't actually release).
Thanks for the feedback,
> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --------------------------------------------------------------------------
>
> Key: DERBY-4267
> URL: https://issues.apache.org/jira/browse/DERBY-4267
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.5.1.1, 10.6.0.0
> Reporter: H.-Dirk Schmitt
> Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat,
> derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat,
> derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat,
> maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
