GitHub user pax95 opened a pull request:
https://github.com/apache/camel/pull/1129
Socket write should be thread safe
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pax95/camel Splunk-fix
Alternatively you can review and apply
GitHub user transamericamoon opened a pull request:
https://github.com/apache/camel/pull/1128
fixes for windows buid and maven proxy
These fixes make it possible to do a full build on windows.
This fix just appends .cmd to the maven command called from
"exec-maven-plugin" i
On Fri, Aug 19, 2016 at 3:54 PM, Claus Ibsen wrote:
> There is already CI jobs for this - they are the ones named notest,
> which ought to be configured to publish to staging m2 repo after
> success:
> https://builds.apache.org/view/A-D/view/Camel/
>
If I switch the current version to 2.18.0-SN
Hi
Maybe something went wrong but your posted half a stacktrace and nothing else.
If you want to get help with Camel then read
http://camel.apache.org/support.html
On Fri, Aug 19, 2016 at 4:44 PM, piaga wrote:
> at
> org.apache.camel.impl.DefaultEndpoint.getEndpointUri(DefaultEndpoint.java:184)
On Fri, Aug 19, 2016 at 4:27 PM, Raul Kripalani wrote:
> Not particularly with Camel, Claus, but I've seen this in other contexts.
>
> There are a variety of reasons why one might run a **controlled** snapshot
> in production: maybe it's a proof of concept with limited exposure, maybe
> one has a
at
org.apache.camel.impl.DefaultEndpoint.getEndpointUri(DefaultEndpoint.java:184)
at
org.apache.camel.processor.SendProcessor.(SendProcessor.java:76)
at
org.apache.camel.model.SendDefinition.createProcessor(SendDefinition.java:57)
at
org.apache.camel.model.ProcessorDefiniti
Not particularly with Camel, Claus, but I've seen this in other contexts.
There are a variety of reasons why one might run a **controlled** snapshot
in production: maybe it's a proof of concept with limited exposure, maybe
one has a full Continuous Delivery pipeline with Canary techniques where
yo
On Wed, Aug 17, 2016 at 4:12 PM, Raul Kripalani wrote:
> Hi Claus,
>
> I see your point, but the vast majority of Apache TLP projects are
> publishing SNAPSHOTs per-release, not per version line.
>
> Spark, Kafka, Zookeeper, Aries, Karaf, CXF, Maven, etc. publish per-version
> SNAPSHOTs. I've only
I pushed a fix because our CI server has the same problem so it cannot
do a build
https://github.com/apache/camel/commit/db1d9eb701b9fe8a93b5fd376d79ad5659912e47
Can you try with latest code again ?
On Fri, Aug 19, 2016 at 8:21 AM, Claus Ibsen wrote:
> Hi
>
> You are welcome to log a JIRA / prov
On Wed, Aug 17, 2016 at 4:12 PM, Raul Kripalani wrote:
> Hi Claus,
>
> I see your point, but the vast majority of Apache TLP projects are
> publishing SNAPSHOTs per-release, not per version line.
>
> Spark, Kafka, Zookeeper, Aries, Karaf, CXF, Maven, etc. publish per-version
> SNAPSHOTs. I've only
On Wed, Aug 17, 2016 at 4:22 PM, Raul Kripalani wrote:
> Also Claus, I found a mixture of per-release-line SNAPSHOTS and per-release
> SNAPSHOTs in our repo:
> https://repository.apache.org/content/groups/snapshots/org/apache/camel/camel-core.
> Not sure if this is intentional or not.
>
> This is
11 matches
Mail list logo
