camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henryk Konsek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3503) Camel-extra 2.6.0 release
Date Sun, 09 Jan 2011 21:46:46 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979410#action_12979410
] 

Henryk Konsek commented on CAMEL-3503:
--------------------------------------

I've deployed version 2.5.0 of extra to extra-repo so now people can just use stable version
of Camel-extra 2.5.0 (after adding extra-repo to their POM files).

I've also created 2.5.0 tag and changed trunk version to 2.6-SNAPSHOT.

While releasing 2.6.0 version I'll figure out what's wrong with the release plugin configuration
to automatize the process.

> 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.


Mime
View raw message