Hi Babak, most of those are assigned to me and is ongoing work. Since
then I discovered issues with uris in a few other components. My
intention is to resolve as many as I can in 2.9.1. The idea is to pick
up the low hanging fruits now and for the 3.0 release all camel uris to
be proper uris.
Hi
Currently there're 17 open tickets most of them were postponed to 2.9.1 as
there was the intention to bring 2.9.0 out the door, mostly regarding the
proper URI format/usage stuff, etc.
Would be the idea to postpone these tickets again to another 2.9.x release
or can it be managed to resolve th
I recently found that tortoise svn also manages the properties for
merged and blocked revisions.
So that may be another option at least on windows.
Christian
Am 08.02.2012 13:57, schrieb Babak Vahdat:
Hi Willem,
thanks for your feedback, so I will try to find a working copy of that
script an
Thanks for your answers,
vcheruvu : That's good idea but projects for GSoC have to be more technical
like extending core functionality of existing framework or integrating
frameworks. Maybe after this competition I'll try to integrate more business
projects like Bloomberg. Thanks for your idea.
C
Hi Willem,
thanks for your feedback, so I will try to find a working copy of that
script and will make use of that from now on.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Question-regarding-tooling-while-doing-svn-merge-tp5466224p5466426.html
Sent from the Camel D
Hi Babak,
svnmerge.py will set the svn properties with merged and blocked
reversion which can help us to trace if there is any patch which we
don't merged.
I'm not sure if the Eclipse merge tool can do the same thing.
On Wed Feb 8 19:03:29 2012, Babak Vahdat wrote:
Hi,
I make use of the fo
CXF's website is being moved over to a buildbot build with the results being
checked in to SVN. When that is complete (filed the initial INFRA request
yesterday), we'll at least be able to tag the docs that were "current" for any
release. It's a bit early to move the Camel site to the same
Hi,
I make use of the following tool inside Eclipse to merge my revisions back
to the branches:
http://desktop-eclipse.open.collab.net/servlets/ProjectProcess?pageID=MEuUjb&freeformpage=Merge%20Client
Are all O.K. with this or do you want me to make use of the Python script
mentioned here:
http
+1
Regards
JB
On 02/07/2012 04:53 PM, Hadrian Zbarcea wrote:
There are some 65 issues resolved for 2.9.1 and 6 weeks since the 2.9.0
release. I am planning on releasing 2.9.1 in a week or so.
Thoughts?
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.t
+1
Sounds good to me
Christian
Am 07.02.2012 16:53, schrieb Hadrian Zbarcea:
There are some 65 issues resolved for 2.9.1 and 6 weeks since the
2.9.0 release. I am planning on releasing 2.9.1 in a week or so.
Thoughts?
--
Christian Schneider
http://www.liquid-reality.de
Open Source Archi
If we just apply the bug patch on the branch, it will more easy for us
to maintain the document.
In this case, we can reuse the Camel 2.8.0 doc for all the other Camel
2.8.x ...
On Wed Feb 8 15:02:55 2012, Christian Schneider wrote:
I would also try to keep the documentation as simple as possi
11 matches
Mail list logo
