db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6866) Add URLs to Maven pom files
Date Wed, 10 Feb 2016 01:25:18 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140163#comment-15140163
] 

ASF subversion and git services commented on DERBY-6866:
--------------------------------------------------------

Commit 1729514 from [~bryanpendleton] in branch 'code/trunk'
[ https://svn.apache.org/r1729514 ]

DERBY-6866: Add URLs to Maven POM files

This patch was contributed by Bindul Bhowmik ( bindulbhowmik at gmail dot com )

Maven POMs have a 'url' element, which is optional, but if not present Maven
automatically calculates the URL using the parent project POM's URL and
adding the child artifact's ID.

Because of this, Derby jar files in Maven repositories were being displayed
by Maven-related tools with URLs like

	http://db.apache.org/derby/derbyclient/

which is not a valid URL.

This change supplies the url element for each of the individual jar file
artifacts, using the preferred URL

	http://db.apache.org/derby/

in all case.

> Add URLs to Maven pom files
> ---------------------------
>
>                 Key: DERBY-6866
>                 URL: https://issues.apache.org/jira/browse/DERBY-6866
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>            Reporter: Bindul Bhowmik
>            Priority: Minor
>         Attachments: derby-code-pom-fix.diff
>
>
> Maven POMs have a <url> element, which is optional, but if not present Maven automatically
calculates the URL using the parent project POM's URL and adding /${project.artifactId}.
> The current Maven POMs in the Derby source only has a URL defined in the parent POM ({{./maven2/pom.xml}}),
but not in the other POMs. So, for any module of the project, the generated URLs are invalid.
> For, example, if you run the following in the {{./maven2/client}} directory the URL is
incorrect:
> {code}
> :~/projects/apache/svn/derby-code/maven2/client$ mvn help:effective-pom | grep '^  <url>'
>   <url>http://db.apache.org/derby/derbyclient/</url>
> {code}
> This information is also used by the Maven Project Info Report plugin to generate the
{{Dependencies}} report and the generated site causes {{404}} errors. For example, see http://www.deventropy.org/junit-helper/junit-helper-derby/dependencies.html#compile.
> The attached patch adds the URL element to all the POMs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message