Hi,
This depends on what you are intending to do with the change. If you just want
to do *test* the new feature with a released version you might build the
version locally without changing the version at all. Obviously you cannot push
that to any nexus or send it to anybody else without causing
Is there a best practice for bumping the version of a single component when
testing a new patch/feature?
I would like to be able to build and test the single component without
changing the entire version of the camel tree.
Right now, if I add a version element to a component sub-pom (say
2.16.1-m
GitHub user cjnygard opened a pull request:
https://github.com/apache/camel/pull/764
Fix erroneous logging when mapTemplate.size()==1
If mapTemplate.size()==1, the previous logic would still output the "Cannot
determine which one to use" message. Minor issue, but the structure of t
Github user tdiesler closed the pull request at:
https://github.com/apache/camel/pull/761
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Hi Luca,
Great job! I read the docs quickly and seems ok :-)
I'll read more thoroughlylater.
Anyway the docs looks good to me.
--
Andrea Cosentino
-
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
I've create the documentation
https://cwiki.apache.org/confluence/display/CAMEL/Braintree , can
someone have a look and tell me if I need to amend something ?
On Sun, Jan 10, 2016 at 12:36 PM, Claus Ibsen wrote:
> Hi Luca
>
> Thanks I have granted your user karma to edit the wiki docs.
>
> On Thu
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/762
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
