The Apache Jenkins build system has built Camel.trunk.notest (build #3055)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3055/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest.java9 (build #32)
Status: Failure
Check console output at
https://builds.apache.org/job/Camel.trunk.notest.java9/32/ to view the results.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1542
---
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 enab
GitHub user johnpoth opened a pull request:
https://github.com/apache/camel/pull/1542
Camel-10141 Make more Java 9 tests pass
https://issues.apache.org/jira/browse/CAMEL-10141
Make more Java 9 tests pass
You can merge this pull request into a Git repository by running:
Hi,
for instance in BeanLookupUsingJndiRegistryIssueTest.java:34[1], the
warrning I get in Eclipse is:
"Resource leak: 'camel' is never closed"
this is because the resource leak detection code in IDE is looking for
close(), but we have stop()
zoran
[1]
https://github.com/apache/camel/blob/mast
Hi
Is there an example you can point we can open in our IDEs to see ?
On Wed, Mar 15, 2017 at 9:49 AM, Zoran Regvart wrote:
> Hi,
> just giving the discussion on the PR#1537[1], CAMEL-11011[2] more
> visibility here if anyone would like to comment.
> The downside I found was that the IDE issues
Hi
Just wanted to bring up that we are closing in on a good time for
doing a new release.
For example in mid April it would be around 6 months since the last
2.18.0 release.
Therefore we should start closing down and fixing bugs, and make sure
the CI servers and tests are in good shape.
This mor
Hi,
just giving the discussion on the PR#1537[1], CAMEL-11011[2] more
visibility here if anyone would like to comment.
The downside I found was that the IDE issues a warning about
'Potential resource leak'. I don't know if this would be reason enough
to revert this?
zoran
[1] https://github.com/a
Hi,
As per my observations, unless zipdataformat does not get the filename of
such empty directory from the file consumer. that's there is no need any
such change in ZipAggregationStrategy.
However, with a bit of hacking on file consumer in camel-core as well and i
could have passed empty folder
