camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iandebeer <>
Subject Re: Contributing Stomp Component
Date Thu, 31 Jan 2013 08:04:07 GMT
Hi Henryk
That is a good approach. I have already contacted the Scomp developer and I am waiting for
a response. Should that not be forthcoming I shall follow your suggestion.

On 31 Jan 2013, at 9:55 AM, "hekonsek [via Camel]" <>

> Hi Ian, 
> > The original project has not been maintained for more than a year. 
> > ... 
> > I have tried to contact Dejan to get his input in this regard. 
> > ... 
> >  I am happy to collaborate with the original author but it might be simpler to work
of the branch 
> In my opinion core Camel components should be dependent only on the 
> stable 3rd party libraries. We violated this rule in the case of the 
> CSV [1] data format and once I run into some production issues at the 
> client site for this reason. Keeping local fork of the library in the 
> component is not the way to go, if you ask me. 
> I propose the following - try to settle an agreement with the Scomp 
> team. If in collaboration with the Scomp guys you could release new 
> version of the library, then use it in the Camel component. If not 
> (i.e. Scomp team explicitly tells you that the project will not be 
> released anymore), then fork Scomp on GitHub, fix it and distribute 
> your Camel component with your library. 
> Does it sound reasonable? 
> [1]
> -- 
> Henryk Konsek 
> If you reply to this email, your message will be added to the discussion below:
> To unsubscribe from Contributing Apollo Component, click here.

View this message in context:
Sent from the Camel Development mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message