db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien HENRY (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4267) Investigate why Derby is not available in the maven2 repositories
Date Wed, 26 Aug 2009 07:06:59 GMT

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

Julien HENRY commented on DERBY-4267:

1) To sign the artifacts you can use the GPG plugin.
I think this is what is used for all Maven plugins themself.

2) To have your Maven artifacts ultimately on central there are several possibilities. Either
host yourself a server where you can put your files. Maven is able to deploy using ssh, ftp,
webdav, ... For example for JWebUnit project we are deploying next to Sourceforge site files
via ssh (http://jwebunit.sourceforge.net/m2-repo/). Then you can ask Maven team to replicate
your repo on the central.
The other option is to ask for a repo on Nexus OpenSource (http://nexus.sonatype.org/oss-repository-hosting.html)

> Investigate why Derby 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:,
>            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, maven2.zip
> Only 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.

View raw message