[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762665#action_12762665
]
Rick Hillegas commented on DERBY-4267:
--------------------------------------
Hi Kristian,
I can see that this could be a religious discussion. From your description of
how this element is used, the following answers make sense to me:
1) <scm> could be a pointer to the head of the development codeline. That is
what the element describes now.
2) <scm> could point at the svn tag for the release, the exact source code used
to build the artifacts.
Pointing <scm> at the head of the release branch falls somewhere between (1)
and (2) and seems to me to be harder to motivate than the options above.
In any event, I'm fine with your current solution, (1). And I know nothing. So
take my advice at your peril!
> 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,
> derby-4267-2c-using_ant_task.diff, 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.
