The Apache Jenkins build system has built Camel.trunk.notest (build #1787)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1787/
to view the results.
Oh, I don't agree with that Scomp component is written in Scala we should find
other place to host it.
As an open source project we should alway encourage people to contribute, and
we can always find someone who willing to maintain the code, if we have lots of
users to use component.
--
Wi
Willem, I know all that. I understand it makes sense from the
contributor's point of view. It saves contributors time, effort and
costs. It ensures the their component will continue to work with future
versions of camel. That benefits the community too. Personally I applaud
that attitude.
How
Putting the components into Apache Camel umbral could save some work of
contributor when we release the Camel. We add the camel-extra due to the
license issue only. It is hard to say no for the contributing to Apache Camel
if the component has the ASF license already. That is way we have more th
Great work! Thanks,
Hadrian
On 02/07/2013 03:02 PM, Henryk Konsek wrote:
If everything will be in order, I'll start synchronization with the
Maven Central in a few days.
FYI I updated (rev980) ASF Camel to 2.10.2 in the current development
version of 2.10.x branch (as 2.10.2 will be the next v
Yeah, attaching the patch is sufficient.
Thanks again for pointing out this potential improvement.
Best,
Christian
On Thu, Feb 7, 2013 at 10:56 PM, Antoine DESSAIGNE <
antoine.dessai...@gmail.com> wrote:
> Hi,
>
> Thank you very much for creating this issue JIRA, I've just added the patch
> as a
+1
Best,
Christian
On Wed, Feb 6, 2013 at 11:02 PM, Henryk Konsek wrote:
> >> For Spring we have a broad version range
>
> Issue updated [1]. I'll handle this before the next release.
>
> > I'll try to stage the release this week.
>
> Camel Extra 2.10.1 release has been staged at Sonatype OSS r
I also believe Apache Camel the way it is organized now is not the place
for the scomp component. We are not debating the quality of the scomp
component. We know however from past experience that the community's
ability to support scala based code was not at par with the rest of the
code base.
Please find my comments inline.
Best,
Christian
On Thu, Feb 7, 2013 at 9:20 PM, Henryk Konsek wrote:
> > Because Camel and Camel-Extra are Java based projects, I don't think we
> > should integrate this component (even if it's a cool component for Scala
> > guys).
>
> I'm afraid I must disagree
> So once we have Scomp updated we are good to go.
First of all we need to figure out where the component should go, as
apparently there is some disagreement related to the proper place for
the Scala-related components.
BTW Camel Stomp definition made my day :P .
--
Henryk Konsek
http://henryk-
I have to say I kinda agree with this.
We could mark a component as possibly "less quickly patched",
but nixing contributions on a component level seems kinda wrong to me...
On Feb 7, 2013, at 1:20 PM, Henryk Konsek wrote:
>> Because Camel and Camel-Extra are Java based projects, I don't think
> Because Camel and Camel-Extra are Java based projects, I don't think we
> should integrate this component (even if it's a cool component for Scala
> guys).
I'm afraid I must disagree :) .
We support Scala as the 1st class citizen DSL language for Camel and I
don't see any reason why we should e
> If everything will be in order, I'll start synchronization with the
> Maven Central in a few days.
FYI I updated (rev980) ASF Camel to 2.10.2 in the current development
version of 2.10.x branch (as 2.10.2 will be the next version I'll
release).
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Ok.. yes that MutableInt is just a counter. I had it as AtomicInteger to
start but changed it. :)
I'll re-submit shortly without the commons-lang dependency..
Thanks!
On Thu, Feb 7, 2013 at 10:25 AM, Claus Ibsen (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/CAMEL-6039?page=co
Hello,
yes this works for me. I have created an issue and provided a patch. see
https://issues.apache.org/jira/browse/CAMEL-6045
Please let me know if I have done something wrong or could make something
better.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.n
On Thu, Feb 7, 2013 at 12:09 PM, cgiera wrote:
> Hello,
>
> I know this is an old post, but I'm facing the same problem.
>
> Could this be solved by simply adding a fileName check to the if statement?
>
I suggest to try patch the code and test it.
And if it helps, then we love contributions
http:
Hello,
I know this is an old post, but I'm facing the same problem.
Could this be solved by simply adding a fileName check to the if statement?
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Email-Component-Missing-Attachments-tp3386382p57
17 matches
Mail list logo
