Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <31359216.237431294568627874.JavaMail.jira@thor>
Date: Sun, 9 Jan 2011 05:23:47 -0500 (EST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Updated: (CAMEL-3503) Camel-extra 2.6.0 release
In-Reply-To: <1866834.165811294251885068.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen updated CAMEL-3503:
-------------------------------

    Affects Version/s:     (was: 2.5.0)
        Fix Version/s:     (was: 2.5.0)
                       2.6.0
              Summary: Camel-extra 2.6.0 release  (was: Camel-extra 2.5.0 release)

> Camel-extra 2.6.0 release
> -------------------------
>
>                 Key: CAMEL-3503
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3503
>             Project: Camel
>          Issue Type: Task
>            Reporter: Henryk Konsek
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> I wanted to release Camel-extra 2.5.0.
> I see that Claus updated all snapshots to 2.5.0. Can I just create SVN tag 2.5.0 from trunk and then change POMs version to 2.6-SNAPSHOT?
> There is a Maven:release configured but: 
> a) there where problems when I tried to use it on the Camel-extra some time ago
> b) we cannot use release plugin when there's no snapshot versions in the project POMs
> Actually I would be happy if we can just release camel-extra 2.5.0 "manually" (without release plugin) and try to get back it during the 2.6.0 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.