You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Henryk Konsek (JIRA)" <ji...@apache.org> on 2011/01/05 19:24:45 UTC
[jira] Created: (CAMEL-3503) Camel-extra 2.5.0 release
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.
[jira] Commented: (CAMEL-3503) Camel-extra 2.5.0 release
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CAMEL-3503) Camel-extra 2.6.0 release
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CAMEL-3503) Camel-extra 2.6.0 release
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3503:
-------------------------------
Fix Version/s: (was: 2.6.0)
2.7.0
We will release camel-extra *after* Camel 2.6 has been released, so I set the fix version to the next 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.7.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.
[jira] Closed: (CAMEL-3503) Camel-extra 2.6.0 release
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea closed CAMEL-3503.
----------------------------------
Resolution: Duplicate
Duplicate of CAMEL-3615
> 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.7.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CAMEL-3503) Camel-extra 2.6.0 release
Posted by "Henryk Konsek (JIRA)" <ji...@apache.org>.
[ 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.