[jira] Commented: (CAMEL-3615) Release Camel Extra 2.6.0

[ https://issues.apache.org/jira/browse/CAMEL-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990006#comment-12990006 ] Henryk Konsek commented on CAMEL-3615: -- Camel-extra 2.6.0 artifacts released. Now I

[jira] Resolved: (CAMEL-3609) Upgrade to jersey 1.5 in camel-web

[ https://issues.apache.org/jira/browse/CAMEL-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3609. Resolution: Fixed Upgrade to jersey 1.5 in camel-web --

[jira] Resolved: (CAMEL-3615) Release Camel Extra 2.6.0

[ https://issues.apache.org/jira/browse/CAMEL-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3615. Resolution: Fixed Release Camel Extra 2.6.0 - Key:

[jira] Resolved: (CAMEL-3608) HttpProducer should not eat up the content-type when working in proxy mode.

[ https://issues.apache.org/jira/browse/CAMEL-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3608. Resolution: Fixed Fix Version/s: 2.7.0 trunk: 1066039 HttpProducer should not eat up the

[jira] Resolved: (CAMEL-3602) camel xslt component should set the ErrorHandler when it uses Transformer to transform the message

[ https://issues.apache.org/jira/browse/CAMEL-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3602. Resolution: Fixed trunk: 1065540 camel xslt component should set the ErrorHandler when it uses

[jira] Commented: (CAMEL-3610) Use MDC for logging message id and/or transaction id

[ https://issues.apache.org/jira/browse/CAMEL-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990043#comment-12990043 ] Claus Ibsen commented on CAMEL-3610: Added documentation

Re: [jira] Commented: (CAMEL-3615) Release Camel Extra 2.6.0

It would have been better if you checked the issues first, this one in particular: http://code.google.com/p/camel-extra/issues/detail?id=22 As it is, camel-extra violates the ASF policies by using the apache package names. I am in the process of clarifying this. There was a discuss about that,

[jira] Created: (CAMEL-3617) Inconsistent filename value when move attribute is used with File component

Inconsistent filename value when move attribute is used with File component --- Key: CAMEL-3617 URL: https://issues.apache.org/jira/browse/CAMEL-3617 Project: Camel

[jira] Created: (CAMEL-3618) Upgrade to Jackson 1.7

Upgrade to Jackson 1.7 -- Key: CAMEL-3618 URL: https://issues.apache.org/jira/browse/CAMEL-3618 Project: Camel Issue Type: Task Reporter: Claus Ibsen Priority: Minor Jackson 1.7 has been

[jira] Created: (CAMEL-3619) Improve the Simple Expression Language parser to detect syntax errors

Improve the Simple Expression Language parser to detect syntax errors - Key: CAMEL-3619 URL: https://issues.apache.org/jira/browse/CAMEL-3619 Project: Camel Issue Type:

[jira] Commented: (CAMEL-3617) Inconsistent filename value when move attribute is used with File component

[ https://issues.apache.org/jira/browse/CAMEL-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990133#comment-12990133 ] Claus Ibsen commented on CAMEL-3617: Can you try with Camel 2.6 which has been

[jira] Resolved: (CAMEL-3610) Use MDC for logging message id and/or transaction id

[ https://issues.apache.org/jira/browse/CAMEL-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3610. Resolution: Fixed added transaction key: 1066836. Use MDC for logging message id and/or

Re: [jira] Commented: (CAMEL-3615) Release Camel Extra 2.6.0

And we will probably need to redo the release. With that change we could also publish to maven central. Can't we just keep the 2.6.0 release as it is and introduce new packing convention in 2.7-SNAPSHOT? 2.7.0 release will be then the first version to be released to public repo. -- Henryk

[jira] Commented: (CAMEL-3615) Release Camel Extra 2.6.0

[ https://issues.apache.org/jira/browse/CAMEL-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990238#comment-12990238 ] Henryk Konsek commented on CAMEL-3615: -- Migrated to SLF4J and upgraded version to

Hudson build is back to normal : Camel » Camel :: Spring #1134

See https://hudson.apache.org/hudson/job/Camel/org.apache.camel$camel-spring/1134/changes

Hudson build is back to normal : Camel #1134

See https://hudson.apache.org/hudson/job/Camel/1134/changes

Re: [jira] Commented: (CAMEL-3615) Release Camel Extra 2.6.0

On Thu, Feb 3, 2011 at 8:02 PM, Henryk Konsek hekon...@gmail.com wrote: And we will probably need to redo the release. With that change we could also publish to maven central. Can't we just keep the 2.6.0 release as it is and introduce new packing convention in 2.7-SNAPSHOT? 2.7.0 release

mvn -Pfastinsstall fails on my hudson at home (Linux)

I got a failure when building camel. Seems to have to do with slf4j Any ideas? Christian mavenExecutionResult exceptions not empty org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.sun.jersey.contribs:maven-wadl-plugin:1.4:generate (generate) on project

Re: mvn -Pfastinsstall fails on my hudson at home (Linux)

Hi Christian, Claus updated Camel trunk to use SLF4J as default logger. It looks like slf4j-api is in the classpath but not implementation (for instance slf4j-log4j12). Regards JB On 02/04/2011 08:36 AM, Christian Schneider wrote: I got a failure when building camel. Seems to have to do

[jira] Assigned: (CAMEL-3603) Upgrade to JDK 1.6 as minimum (eg drop support for JDK 1.5)

[ https://issues.apache.org/jira/browse/CAMEL-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-3603: -- Assignee: Claus Ibsen Upgrade to JDK 1.6 as minimum (eg drop support for JDK 1.5)

Re: [DISCUSS] Dropping support for java 1.5 from camel-2.7.0 onwards

Hi Camel 2.7 roadmap http://camel.apache.org/camel-27-roadmap.html The switching to slf4j logging is now complete on trunk. Are we ready for the next step? To drop JDK 1.5? https://issues.apache.org/jira/browse/CAMEL-3603 When we get started on this, there is no turning back. -- Claus