Re: [VOTE] Release Apache Camel 2.10.3

[Jon Anstey]

+1


On Sun, Dec 2, 2012 at 11:36 PM, Hadrian Zbarcea  wrote:

> A new patch release candidate apache-camel-2.10.3 final is out with
> approximately 74 issues resolved so far: improvements and bug fixes [1].
>
> Please find the staging repo here:
> https://repository.apache.org/**content/repositories/**orgapachecamel-107/
>
> The tarballs are here
> https://repository.apache.org/**content/repositories/**
> orgapachecamel-107/org/apache/**camel/apache-camel/2.10.3/
>
> Tag:
> http://svn.apache.org/repos/**asf/camel/tags/camel-2.10.3/
>
> Please review, help out with testing and vote to approve this release
> binary. Your vote counts!
>
> [ ] +1 Release the binary as Apache Camel 2.10.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Here's my +1.
> Hadrian
>
> [1] https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
> projectId=12311211&version=**12323366
>
>
> --
> Hadrian Zbarcea
> Principal Software Architect
> Talend, Inc
> http://coders.talend.com/
> http://camelbot.blogspot.com/
>



-- 
Cheers,
Jon
---
Red Hat, Inc.
Email: jans...@redhat.com
Web: http://redhat.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen

Re: [VOTE] Release Apache Camel 2.10.3

[Claus Ibsen]

+1

On Mon, Dec 3, 2012 at 4:06 AM, Hadrian Zbarcea  wrote:
> A new patch release candidate apache-camel-2.10.3 final is out with
> approximately 74 issues resolved so far: improvements and bug fixes [1].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-107/
>
> The tarballs are here
> https://repository.apache.org/content/repositories/orgapachecamel-107/org/apache/camel/apache-camel/2.10.3/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.3/
>
> Please review, help out with testing and vote to approve this release
> binary. Your vote counts!
>
> [ ] +1 Release the binary as Apache Camel 2.10.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Here's my +1.
> Hadrian
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12323366
>
>
> --
> Hadrian Zbarcea
> Principal Software Architect
> Talend, Inc
> http://coders.talend.com/
> http://camelbot.blogspot.com/



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: [VOTE] Release Apache Camel 2.10.3

[Willem Jiang]

+1

Willem

On Tue, Dec 4, 2012 at 8:36 PM, Claus Ibsen  wrote:
> +1
>
> On Mon, Dec 3, 2012 at 4:06 AM, Hadrian Zbarcea  wrote:
>> A new patch release candidate apache-camel-2.10.3 final is out with
>> approximately 74 issues resolved so far: improvements and bug fixes [1].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-107/
>>
>> The tarballs are here
>> https://repository.apache.org/content/repositories/orgapachecamel-107/org/apache/camel/apache-camel/2.10.3/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.3/
>>
>> Please review, help out with testing and vote to approve this release
>> binary. Your vote counts!
>>
>> [ ] +1 Release the binary as Apache Camel 2.10.3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Here's my +1.
>> Hadrian
>>
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12323366
>>
>>
>> --
>> Hadrian Zbarcea
>> Principal Software Architect
>> Talend, Inc
>> http://coders.talend.com/
>> http://camelbot.blogspot.com/
>
>
>
> --
> Claus Ibsen
> -
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cib...@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen

Re: [DISCUSION] Adding Support For Gemini Blueprint

[Scott England-Sullivan]

When the Camel OSGi folks have a second, Claus asked that I get your input.

Thanks in advance.

Best Regards,
Scott ES

On Mon, Dec 3, 2012 at 4:03 PM, Scott England-Sullivan
wrote:

> Exactly.
>
> For that matter, any API that has Spring Namespace support, such as CXF,
> would work seamlessly with a Camel Gemini Blueprint component.
>
>
> On Mon, Dec 3, 2012 at 3:43 PM, Daniel Kulp  wrote:
>
>>
>> Also keep in mind that even just porting the camel-blueprint stuff
>> wouldn't provide 100% of the functionality.   For example, the CXF
>> blueprint stuff for camel-cxf relies heavily on the blueprint support in
>> CXF which is also highly tied to Aries.
>>
>> Dan
>>
>>
>> On Dec 3, 2012, at 1:00 PM, Scott England-Sullivan 
>> wrote:
>>
>> > It hasn't been forgotten, just on-hold while I have been out on
>> > assignments.  ;-)
>> >
>> > I will be back and able to continue this when I return next week.
>> >
>> > To stimulate discussion while I am out though, I still believe we will
>> need
>> > a dedicated Camel Gemini Blueprint component as the current Camel
>> Blueprint
>> > is tightly coupled to Aries Blueprint and there isn't a direct
>> translation
>> > to the same capabilities in Gemini Blueprint.
>> >
>> > Also, Gemini Blueprint is tightly coupled to Spring and folks that use
>> it
>> > also use Spring stuff (like the Spring Context namespace which Gemini
>> > supports).  It makes the most sense to develop a component for the two
>> > blueprint implementations independently.  Camel already has mature
>> Spring
>> > support so we should take advantage of it.
>> >
>> > I know it would be "cleaner" if the current Camel Blueprint component
>> could
>> > support either implementation but I believe the changes would be very
>> > extensive and make it difficult to, if not eliminate, the ability to
>> > support the extensions that both implementations provide that our users
>> > depend on.
>> >
>> > Just my two cents...
>> >
>> >
>> >
>> > On Sun, Dec 2, 2012 at 4:12 AM, Benjamin Graf 
>> wrote:
>> >
>> >> Hi,
>> >>
>> >> any new suggestions to this discussion? It seems the discussion has
>> been
>> >> forgotten. :-)
>> >>
>> >> Best,
>> >> Benjamin
>> >>
>> >> On 06.11.2012 17:25, Scott England-Sullivan wrote:
>> >>> That makes sense.  I will table it until next week.
>> >>>
>> >>> Thanks to you both Willem and Claus.
>> >>>
>> >>> On Tue, Nov 6, 2012 at 10:13 AM, Claus Ibsen 
>> >> wrote:
>> >>>
>>  Hi
>> 
>>  A number of the OSGi guys are at ApacheCon EU and thus not online as
>> >> much.
>>  I would like to give some time for them to give feedback, before any
>>  decision / commits is done on the codebase.
>> 
>> 
>>  On Tue, Nov 6, 2012 at 3:31 PM, Scott England-Sullivan
>>   wrote:
>> > If nobody has an issue with it I am proceeding with option 3.
>> >
>> > Any concerns?
>> >
>> > On Mon, Nov 5, 2012 at 3:02 PM, Benjamin Graf <
>> benjamin.g...@gmx.net>
>>  wrote:
>> >> Hi Scott,
>> >>
>> >> sounds reasonable. :-)
>> >>
>> >> Benjamin
>> >>
>> >>
>> >> On 05.11.2012 21:46, Scott England-Sullivan wrote:
>> >>
>> >>> Hi Benjamin,
>> >>>
>> >>> Its not that I found anything with Camel.  Its the documentation
>> from
>>  the
>> >>> Gemini Blueprint project that concerns me.  Reading the following:
>> >>>
>> >>> From the Gemini Blueprint Migration Document
>> >>>
>> http://www.eclipse.org/gemini/**blueprint/documentation/**migration/
>> >> <
>>  http://www.eclipse.org/gemini/blueprint/documentation/migration/>
>> >>> :
>> >>>
>> >>>
>> >>> {snip}
>> >>>
>> >>> ** Removed deprecated modules **
>> >>>
>> >>> As of Gemini Blueprint M1, not all modules or projects inside
>> Spring
>> >> DM
>> >>> have been moved. At the moment only the io, core, extender and
>> test
>> >>> modules
>> >>> have transitioned are provided in M1. With the up-coming release
>> of
>>  OSGi
>> >>> RFC-66, the web support is being discontinued. Existing users are
>> >>> encouraged to look at Eclipse Gemini Web project. The plans for
>> the
>>  Maven
>> >>> archetype and annotation extension are undefined for the moment
>> and
>>  these
>> >>> modules are NOT included in Gemini Blueprint project.
>> >>>
>> >>> {snip}
>> >>>
>> >>>
>> >>> While there may be minimal or small issues for Camel itself, Camel
>>  Users
>> >>> may have extended or used features based on Spring DM.  Given
>> that, I
>> >>> don't
>> >>> feel comfortable stating anything less than it can/will break
>> >> backwards
>> >>> compatibility.
>> >>>
>> >>> Make sense?
>> >>>
>> >>> On Mon, Nov 5, 2012 at 12:36 PM, Benjamin Graf <
>> >> benjamin.g...@gmx.net
>>  wrote:
>> >>> Hi,
>>  I would recommend Option 3a with an additional rename of
>>  camel-blueprint
>>  component to camel-aries-b

Re: [VOTE] Release Apache Camel 2.10.3

[Johan Edstrom]

+1
On Dec 4, 2012, at 5:36 AM, Claus Ibsen  wrote:

> +1
> 
> On Mon, Dec 3, 2012 at 4:06 AM, Hadrian Zbarcea  wrote:
>> A new patch release candidate apache-camel-2.10.3 final is out with
>> approximately 74 issues resolved so far: improvements and bug fixes [1].
>> 
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-107/
>> 
>> The tarballs are here
>> https://repository.apache.org/content/repositories/orgapachecamel-107/org/apache/camel/apache-camel/2.10.3/
>> 
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.3/
>> 
>> Please review, help out with testing and vote to approve this release
>> binary. Your vote counts!
>> 
>> [ ] +1 Release the binary as Apache Camel 2.10.3
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>> 
>> Here's my +1.
>> Hadrian
>> 
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12323366
>> 
>> 
>> --
>> Hadrian Zbarcea
>> Principal Software Architect
>> Talend, Inc
>> http://coders.talend.com/
>> http://camelbot.blogspot.com/
> 
> 
> 
> -- 
> Claus Ibsen
> -
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cib...@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen

Re: aws-s3 EndPoint and s3 Acl on created objects

[massyl]

His Christian,
The Patch is already commited and merged to the trunk before the wiki
modification,
but i didn't know if the patch will be included also in 2.10.x or not, this
is the reason why i didn't include the target version in the wiki.
cheers




--
View this message in context: 
http://camel.465427.n5.nabble.com/aws-s3-EndPoint-and-s3-Acl-on-created-objects-tp5722324p5723630.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: [VOTE] Release Apache Camel 2.10.3

[Daniel Kulp]

+1

Dan



On Dec 2, 2012, at 10:06 PM, Hadrian Zbarcea  wrote:

> A new patch release candidate apache-camel-2.10.3 final is out with 
> approximately 74 issues resolved so far: improvements and bug fixes [1].
> 
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-107/
> 
> The tarballs are here
> https://repository.apache.org/content/repositories/orgapachecamel-107/org/apache/camel/apache-camel/2.10.3/
> 
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.3/
> 
> Please review, help out with testing and vote to approve this release binary. 
> Your vote counts!
> 
> [ ] +1 Release the binary as Apache Camel 2.10.3
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
> 
> Here's my +1.
> Hadrian
> 
> [1] 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12323366
> 
> 
> -- 
> Hadrian Zbarcea
> Principal Software Architect
> Talend, Inc
> http://coders.talend.com/
> http://camelbot.blogspot.com/

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com