db-derby-dev mailing list archives

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

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

Rick Hillegas commented on DERBY-4267:

Thanks Kristian and Julien. I have applied Kristian's 2a patch and added the UTF-8 property
to pom.xml as Julien recommended. The following 2 commands produced no errors and reported
that they ran successfully:

mvn package
mvn install

This produced a tree of objects under ~/.m2/repository/org/apache/derby. Those artifacts are
jars, poms, and maven-metadata-local.xml files. The jars appear to be the correct size. The
poms and metadata files appear to be non-vacuous.

So far so good I think. Comparing this to the old maven1 process, I now expect that I am supposed
to do the following:

1) sign or generate checksums for these artifacts

2) upload the artifacts, signatures, and checksums somewhere

Is there a script or set of instructions for doing (1) and (2)?


> 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