Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1820320847.1254838351269.JavaMail.jira@brutus>
Date: Tue, 6 Oct 2009 07:12:31 -0700 (PDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=12762629#action_12762629 ] 

Kristian Waagan commented on DERBY-4267:
----------------------------------------

Hi Rick,

Your last reply confuses me slightly.
The derby.version element has to go away, because it doesn't work as intended. I don't think we should hold our breath for a solution to the problem either.
The person generating the artifacts will have to insert the correct Derby version number in each and every POM. This can be done easier by using for instance Perl or sed.

I'll rephrase my question.
When we deploy artifacts for the next 10.4 update release, should the scm tag point to the 10.4 branch?
When we deploy artifacts for the next 10.5 update release, should the scm tag point to the 10.5 branch?
Since we currently doesn't deploy artifacts for trunk (which would have had to be snapshots I suppose?), the scm tag of our official Maven artifacts will never point to trunk.

For an example on how the scm tag can be used, let's take NetBeans and a project where you have specified the Derby Maven artifacts as dependencies. In that case, you can choose to check out or browse the source code of Derby by right clicking the icon representing the Maven artifact. Do we want to point our users to the trunk (Derby development version), or to the branch of the official Derby version being used?


In any case, this is a rather minor matter :)

> 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, derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, derby-4267-2c-using_ant_task.diff, 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.