[
https://issues.apache.org/jira/browse/DERBY-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan reopened DERBY-5727:
------------------------------------
I looked into creating artifacts on the older branches. You can do this by
copying the built jars from the branch in question, and then build the Maven
artifacts from maven2 in trunk. However, since this was such an easy backport,
I backported the change to 10.8 (r1336063) and 10.7 (r1336066). It is unlikely
that we ever need to publish older builds to Maven, but if the need arise we
can do that by running the Maven process from trunk.
> Update POMs to deploy Maven artifacts to repository.apache.org and use ASF
> parent POM
> -------------------------------------------------------------------------------------
>
> Key: DERBY-5727
> URL: https://issues.apache.org/jira/browse/DERBY-5727
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Affects Versions: 10.9.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.7.1.4, 10.8.2.3, 10.9.0.0
>
> Attachments: derby-5727-1a-inherit_asf_pom.diff,
> derby-5727-1b-inherit_asf_pom.diff
>
>
> As per Apache infra's request Maven artifacts should be deployed to
> repository.apache.org.
> Derby is currently deploying to people.apache.org, for which Maven deployment
> will be disabled in Jan 2013.
> Additionally, the Derby POMs should refer to the ASF top-level POM as the
> parent. There are several advantages to doing this, see [1] for details.
> [1] http://www.apache.org/dev/publishing-maven-artifacts.html#inherit-parent
--
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
