Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <3805736.181951294300365565.JavaMail.jira@thor>
Date: Thu, 6 Jan 2011 02:52:45 -0500 (EST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-3503) Camel-extra 2.5.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:comment-tabpanel&focusedCommentId=12978200#action_12978200 ] 

Claus Ibsen commented on CAMEL-3503:
------------------------------------

Yeah actually I don't know how camel-extra 1.0 was released in aug 2008.
http://code.google.com/p/camel-extra/source/browse/#svn%2Fmaven2%2Freleases%2Forg%2Fapache%2Fcamel%2Fextra%2Fcamel-esper

I think the maven pom.xml file have some settings for _releasing_ to that repo at google code. So if we can get version 2.5 out, that would be great.
Later we can work on having those JARs synced to central maven repo, or fusesource repo.


> Camel-extra 2.5.0 release
> -------------------------
>
>                 Key: CAMEL-3503
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3503
>             Project: Camel
>          Issue Type: Task
>    Affects Versions: 2.5.0
>            Reporter: Henryk Konsek
>            Priority: Minor
>             Fix For: 2.5.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.