Build failed in Hudson: Camel #1051

See Changes: [ningjiang] CAMEL-3310 updated the jaxws scope [davsclaus] Upgraded MVEL bundle [davsclaus] Upgraded to MVEL 2.0.18 [davsclaus] CAMEL-3314: Fixed property placehodler resolution on EIP in nested sub routes. [ningjiang] CA

Build failed in Hudson: Camel » Camel :: JMX #1051

See Changes: [davsclaus] Added missing license files. [davsclaus] CAMEL-3236: New camel-jmx component. Thanks to Mark Ford for donating to Apache. -- [...truncated 82 l

Build failed in Hudson: Camel » Camel : : Test Bundles: mock-javamail-1.7 #1051

See -- [INFO] [INFO] Building Camel :: Test Bundles: mock-javamail-1.

Hudson build is back to normal : Camel » Camel :: SOAP #1051

See

Hudson build is back to normal : Camel » Camel : : Example :: Report Incident :: WS-Security #1051

See

[jira] Commented: (CAMEL-3310) Update camel-soap to use 2.3.0 tooling

[ https://issues.apache.org/activemq/browse/CAMEL-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63110#action_63110 ] Willem Jiang commented on CAMEL-3310: - Just applied the patch that DanK provided, now the

[jira] Commented: (CAMEL-3172) Create forthcoming Camel-JMX component documentation page

[ https://issues.apache.org/activemq/browse/CAMEL-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63109#action_63109 ] Mark Ford commented on CAMEL-3172: -- Claus, Are you looking for some samples for the wiki? I

[jira] Updated: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3236: - Attachment: camel-jmx-timestamp.txt The timestamp error is likely due to the difference in our timezo

Build failed in Hudson: Camel.trunk.fulltest #28

See Changes: [davsclaus] Upgraded MVEL bundle [davsclaus] Upgraded to MVEL 2.0.18 [davsclaus] CAMEL-3314: Fixed property placehodler resolution on EIP in nested sub routes. [ningjiang] CAMEL-3126 Fixed the XsltRouteTest er

Hudson build is back to stable : Came l.trunk.fulltest » Camel :: Jetty #28

See

Hudson build became unstable: Camel .trunk.fulltest » Camel :: Spring #28

See

Build failed in Hudson: Camel.trunk.fulltest » Camel :: Test Bundles: mock-javamail-1.7 #28

See -- [INFO] [INFO] Building Camel :: Test Bundles: moc

Build failed in Hudson: Camel.tr unk.fulltest » Camel :: SOAP #28

See Changes: [ningjiang] CAMEL-3310 using the JAXWS API 2.2 to make camel-soap compile with JDK 1.5 -- [INFO] -

Build failed in Hudson: Camel.t runk.fulltest » Camel :: JMX #28

See Changes: [davsclaus] Added missing license files. [davsclaus] CAMEL-3236: New camel-jmx component. Thanks to Mark Ford for donating to Apache. -- [...t

[jira] Commented: (CAMEL-3309) Stepwise change of directory unfit for production (ftp/ftps/sftp)

[ https://issues.apache.org/activemq/browse/CAMEL-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63102#action_63102 ] Bengt Rodehav commented on CAMEL-3309: -- I've tested again using unaltered Camel 2.5 and

[jira] Created: (CAMEL-3317) HawtDB throws IOPagingException

HawtDB throws IOPagingException --- Key: CAMEL-3317 URL: https://issues.apache.org/activemq/browse/CAMEL-3317 Project: Apache Camel Issue Type: Bug Reporter: Glenn Moss When running Camel when the Ha

Camel test coverage in Hudson/Sonar

Hi, I was wondering, why isn't the test coverage of Camel measured during Hudson builds? This is easily done using Cobertura. I think we all agree that (unit)test coverage is very important. Monitoring this in Hudson and Sonar ( http://nemo.sonarsource.org) is convenient. It's not that Camel doesn

[jira] Commented: (CAMEL-3309) Stepwise change of directory unfit for production (ftp/ftps/sftp)

[ https://issues.apache.org/activemq/browse/CAMEL-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63101#action_63101 ] Bengt Rodehav commented on CAMEL-3309: -- I have now done a couple of recursive tests on S

Failing unit tests of spring-ws component in CI.

Hi, I've noticed that the unit tests of the spring-ws component failed in the latest Hudson build. Probably because there's no SAAJ jar on the classpath. The following dependencies (with scope 'provided') in pom.xml should resolve this: com.sun.xml.messagi

[jira] Commented: (CAMEL-3316) maven3 requires relativepaths to find parents

[ https://issues.apache.org/activemq/browse/CAMEL-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63100#action_63100 ] Daniel Kulp commented on CAMEL-3316: I honestly have no idea.However, it's still goo

[jira] Commented: (CAMEL-3316) maven3 requires relativepaths to find parents

[ https://issues.apache.org/activemq/browse/CAMEL-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63099#action_63099 ] Claus Ibsen commented on CAMEL-3316: Seems a bit odd? When there is such a major change

Re: Poms still broken with Maven 3....

On Thursday 04 November 2010 10:59:20 am Daniel Kulp wrote: > With the release and version number changes, the parent pom wasn't avail in > my repo and thus I discovered that the whole build is still broken with > Maven 3. I'll work on it. I attached a patch to: https://issues.apache.org/activemq

[jira] Created: (CAMEL-3316) maven3 requires relativepaths to find parents

maven3 requires relativepaths to find parents - Key: CAMEL-3316 URL: https://issues.apache.org/activemq/browse/CAMEL-3316 Project: Apache Camel Issue Type: Bug Reporter: Daniel Kulp

[jira] Updated: (CAMEL-3316) maven3 requires relativepaths to find parents

[ https://issues.apache.org/activemq/browse/CAMEL-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CAMEL-3316: --- Attachment: maven3.patch > maven3 requires relativepaths to find parents > --

[jira] Commented: (CAMEL-3310) Update camel-soap to use 2.3.0 tooling

[ https://issues.apache.org/activemq/browse/CAMEL-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63098#action_63098 ] Daniel Kulp commented on CAMEL-3310: The two new deps need to move to normal scope, not

[jira] Created: (CAMEL-3315) Upgrade to Jasypt 1.7

Upgrade to Jasypt 1.7 - Key: CAMEL-3315 URL: https://issues.apache.org/activemq/browse/CAMEL-3315 Project: Apache Camel Issue Type: Task Reporter: Claus Ibsen Priority: Minor Fix For:

[jira] Commented: (CAMEL-1353) add support for the spring EL from Spring 3 to the languages supported in Camel

[ https://issues.apache.org/activemq/browse/CAMEL-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63097#action_63097 ] Claus Ibsen commented on CAMEL-1353: Thanks Richard for donating. We will get it in Camel

[jira] Resolved: (CAMEL-3314) Property resolve in EIP does not work when in a sub route.

[ https://issues.apache.org/activemq/browse/CAMEL-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3314. Resolution: Fixed trunk: 1031566. Now its fixed. Thanks for reporting. > Property resolve in

[jira] Assigned: (CAMEL-3314) Property resolve in EIP does not work when in a sub route.

[ https://issues.apache.org/activemq/browse/CAMEL-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-3314: -- Assignee: Claus Ibsen > Property resolve in EIP does not work when in a sub route. > --

[jira] Created: (CAMEL-3314) Property resolve in EIP does not work when in a sub route.

Property resolve in EIP does not work when in a sub route. -- Key: CAMEL-3314 URL: https://issues.apache.org/activemq/browse/CAMEL-3314 Project: Apache Camel Issue Type: Bug Affects

Re: Camel 2.5 - Starts to look good for a relese

On Fri, Nov 5, 2010 at 11:45 AM, Henryk Konsek wrote: > On Tue, Oct 12, 2010 at 9:53 PM, Henryk Konsek wrote: >> When you release camel-apache, I'll release camel-extra 2.5 . > > This is my first time with Maven Release Plugin and it's tougher than > I expected. Actually release:prepare doesn't w

Re: Issue with Camel archetypes and m2eclipse...

Thanks! 2010/11/5 Hadrian Zbarcea > Brian Fox is at apachecon. I'll probably bump into him again tomorrow. > Hadrian > > On Nov 4, 2010, at 2:47 PM, Jon Anstey wrote: > > > Yeah I created https://issues.sonatype.org/browse/MVNCENTRAL-9 for > this... > > if someone knows the Maven folks well plea

Re: Camel 2.5 - Starts to look good for a relese

On Tue, Oct 12, 2010 at 9:53 PM, Henryk Konsek wrote: > When you release camel-apache, I'll release camel-extra 2.5 . This is my first time with Maven Release Plugin and it's tougher than I expected. Actually release:prepare doesn't work and I need to get deeper into the plugin to debug why this

[jira] Commented: (CAMEL-3309) Stepwise change of directory unfit for production (ftp/ftps/sftp)

[ https://issues.apache.org/activemq/browse/CAMEL-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63094#action_63094 ] Claus Ibsen commented on CAMEL-3309: What version of FTP Server are you using? And how is

[jira] Commented: (CAMEL-3310) Update camel-soap to use 2.3.0 tooling

[ https://issues.apache.org/activemq/browse/CAMEL-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63093#action_63093 ] Willem Jiang commented on CAMEL-3310: - When build the camel-soap with JDK 1.5, cxf will t

[jira] Issue Comment Edited: (CAMEL-3310) Update camel-soap to use 2.3.0 tooling

[ https://issues.apache.org/activemq/browse/CAMEL-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63091#action_63091 ] Christian Schneider edited comment on CAMEL-3310 at 11/5/10 5:15 AM: --

[jira] Commented: (CAMEL-3310) Update camel-soap to use 2.3.0 tooling

[ https://issues.apache.org/activemq/browse/CAMEL-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63091#action_63091 ] Christian Schneider commented on CAMEL-3310: I guess the dependency to the jaxb a

[jira] Commented: (CAMEL-3309) Stepwise change of directory unfit for production (ftp/ftps/sftp)

[ https://issues.apache.org/activemq/browse/CAMEL-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63090#action_63090 ] Claus Ibsen commented on CAMEL-3309: Yeah there are a lot of unit tests for camel-ftp. wi

[jira] Commented: (CAMEL-3309) Stepwise change of directory unfit for production (ftp/ftps/sftp)

[ https://issues.apache.org/activemq/browse/CAMEL-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63089#action_63089 ] Bengt Rodehav commented on CAMEL-3309: -- I have never used the recursive option before wh

Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?

Hi Is CXF 2.3 compatible with JDK 1.5. I had an issue compiling camel-soap with some recent CXF 2.3 tooling upgrade. See https://issues.apache.org/activemq/browse/CAMEL-3310 On Thu, Nov 4, 2010 at 3:47 PM, Daniel Kulp wrote: > On Thursday 04 November 2010 10:40:18 am William Tam wrote: >> Wil

[jira] Commented: (CAMEL-3310) Update camel-soap to use 2.3.0 tooling

[ https://issues.apache.org/activemq/browse/CAMEL-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63088#action_63088 ] Claus Ibsen commented on CAMEL-3310: Compiling with 1.6 works fine. > Update camel-soap

[jira] Reopened: (CAMEL-3310) Update camel-soap to use 2.3.0 tooling

[ https://issues.apache.org/activemq/browse/CAMEL-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-3310: This cannot compile with JDK 1.5 davsclaus:(svn)camel[trunk:1031468]/components/camel-soap$ mvn -

Build failed in Hudson: Camel.trunk.fulltest #27

See Changes: [ningjiang] Clean up the SuppressWarnings from camel-jpa [davsclaus] CAMEL-3313: Added some tests [davsclaus] CAMEL-3105: spring-ws component. Thanks to Richard Kettelerij for donating the component to Apache.

Hudson build is unstable: Camel.trunk.fu lltest » Camel :: Spring Web Services #27

See

Hudson build became unstable: Camel.tru nk.fulltest » Camel :: Example :: CXF #27

See

Hudson build is back to stable : Camel.trunk .fulltest » Camel :: Example :: CXF Proxy #27

See

Hudson build is back to stable : Came l.trunk.fulltest » Camel :: Netty #27

See

Build failed in Hudson: Camel.tr unk.fulltest » Camel :: SOAP #27

See Changes: [ningjiang] CAMEL-3310 using CXF 2.3.0 tooling in camel-soap -- [INFO]

Hudson build is back to stable : Cam el.trunk.fulltest » Camel :: MINA #27

See

Build failed in Hudson: Camel.trunk.fulltest » Camel :: Test Bundles: mock-javamail-1.7 #27

See -- [INFO] [INFO] Building Camel :: Test Bundles: moc

Hudson build is still unstable: Camel.trun k.fulltest » Camel :: Integration Tests #27

See

Hudson build became unstable: Camel .trunk.fulltest » Camel :: HawtDB #27

See

Hudson build became unstable: Camel .trunk.fulltest » Camel :: Jetty #27

See

Hudson build is back to stable : Cam el.trunk.fulltest » Camel :: Core #27

See

[jira] Commented: (CAMEL-3172) Create forthcoming Camel-JMX component documentation page

[ https://issues.apache.org/activemq/browse/CAMEL-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63085#action_63085 ] Claus Ibsen commented on CAMEL-3172: The documentation is here https://cwiki.apache.org/c

[jira] Commented: (CAMEL-3172) Create forthcoming Camel-JMX component documentation page

[ https://issues.apache.org/activemq/browse/CAMEL-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63083#action_63083 ] Claus Ibsen commented on CAMEL-3172: Thanks Tracy, do you mind creating an example as wel

[jira] Commented: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63082#action_63082 ] Claus Ibsen commented on CAMEL-3236: Added osgi feature: 1031466. > Camel JMX Component

[jira] Resolved: (CAMEL-2405) JMX notification listener to route JMX events to camel

[ https://issues.apache.org/activemq/browse/CAMEL-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-2405. Resolution: Duplicate Fix Version/s: (was: Future) 2.6.0

[jira] Commented: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63081#action_63081 ] Claus Ibsen commented on CAMEL-3236: Thanks Mark for the donation to Apache. trunk: 1031

[jira] Resolved: (CAMEL-3298) XmppPrivateChatProducer should close the connection when it is stopped.

[ https://issues.apache.org/activemq/browse/CAMEL-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-3298. - Resolution: Fixed Applied the patch into revision 1031458. > XmppPrivateChatProducer should