Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2015880209.1251206999473.JavaMail.jira@brutus>
Date: Tue, 25 Aug 2009 06:29:59 -0700 (PDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4267) Investigate why Derby 10.5.1.1 is not
 available in the maven2 repositories
In-Reply-To: <1128834147.1244745187364.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-4267:
-----------------------------------

    Attachment: derby-4267-2a-using_ant_task.stat
                derby-4267-2a-using_ant_task.diff

Patch 2a uses an ant task to simply copy the Derby jar files. The jar generated by maven is overwritten. This isn't exactly elegant...

Note that you will get three warnings per artifact being built, and these are to be expected with the current patch. They can be ignored because these phases aren't needed, but I haven't found out how to suppress them:
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
...
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
...
[WARNING] JAR will be empty - no content was marked for inclusion!

To test, apply patch, make sure you have built the correct Derby jar files (insane by default), then go to maven2/ and type mvn <action>:
 - package  : builds the artifacts into the various target directories
 - install : builds the artifacts and installs into the local repository (~/.m2/repository/org/apache/derby/[artifactId] on *nix)

If you grep for "RELEASE_DATA" in the files in the maven2 dir, you can see the values you have to change to generate release artifacts.
Currently there are two occurences:
 - the Derby version
 - user credentials to deploy to Apache maven2 site

I still feel I don't have enough confidence in this patch, mostly based on the fact that I don't know Maven very well, so I'd like at least one other person to sanity check the patch (metadata, generated artifacts, deploy site, etc.).
Patch 2a ready for review.


> Investigate why Derby 10.5.1.1 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: 10.5.1.1, 10.6.0.0
>            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 10.4.2.0 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.