[
https://issues.apache.org/jira/browse/DERBY-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806275#comment-16806275
]
Rick Hillegas commented on DERBY-7040:
--------------------------------------
Attaching derby-7040-01-aa-addDependenciesToPOMs.diff. This patch adds hard
dependencies to the maven poms which are published at the end of a release. The
hard dependencies are the non-optional dependencies from the 10.15.1 module
diagrams.
It seems that these poms are consulted by projects which use maven as their
build tool. See the commentary on DERBY-7039.
Touches the following files:
{noformat}
M maven2/client/pom.xml
M maven2/engine/pom.xml
M maven2/net/pom.xml
M maven2/optionaltools/pom.xml
M maven2/tools/pom.xml
{noformat}
> Add dependency stanzas to maven poms
> ------------------------------------
>
> Key: DERBY-7040
> URL: https://issues.apache.org/jira/browse/DERBY-7040
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.15.1.3
> Reporter: Rick Hillegas
> Priority: Major
> Attachments: derby-7040-01-aa-addDependenciesToPOMs.diff
>
>
> Add hard dependencies (from the module diagrams) to the poms under maven2.
> The dependency stanza in the network server pom can be used as a template. In
> particular, dependencies on derbyshared.jar should be listed. This issue was
> raised by DERBY-7039.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
