Build failed in Hudson: Camel #1135

See Changes: [hadrian] Fix build issue due to duplicate dependency declarations [hadrian] CAMEL-3438. Fix for injected context [hadrian] CAMEL-3588. Use scope 'provided' for geronimo spec jars [hadrian] CAMEL-3603. Drop support for jdk

Build failed in Hudson: Camel » Camel :: AMQP #1135

See -- [INFO] [INFO] Building Camel :: AMQP [INFO]task-segment: [clean, install] [INFO] -

[jira] Updated: (CAMEL-3626) Upgrade qpid to version 0.8

[ https://issues.apache.org/jira/browse/CAMEL-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated CAMEL-3626: --- Fix Version/s: 2.7.0 > Upgrade qpid to version 0.8 > --- > >

[jira] Created: (CAMEL-3626) Upgrade qpid to version 0.8

Upgrade qpid to version 0.8 --- Key: CAMEL-3626 URL: https://issues.apache.org/jira/browse/CAMEL-3626 Project: Camel Issue Type: Task Affects Versions: 2.6.0 Reporter: Hadrian Zbarcea Currently camel

[jira] Resolved: (CAMEL-3438) JAXBDataFormatter should using Spring ApplicationContext's classLoader explicitly

[ https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved CAMEL-3438. Resolution: Fixed Patch applied in r1067385. Thanks Nick for spotting this and providing th

[jira] Updated: (CAMEL-3438) JAXBDataFormatter should using Spring ApplicationContext's classLoader explicitly

[ https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated CAMEL-3438: --- Fix Version/s: (was: 2.6.0) 2.7.0 Updated fix version to 2.7.0. A fix

[jira] Work started: (CAMEL-3438) JAXBDataFormatter should using Spring ApplicationContext's classLoader explicitly

[ https://issues.apache.org/jira/browse/CAMEL-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3438 started by Hadrian Zbarcea. > JAXBDataFormatter should using Spring ApplicationContext's classLoader > explicitly > --

[jira] Work started: (CAMEL-3588) JMS spec and JPA spec JARs should not be compile scoped by provided

[ https://issues.apache.org/jira/browse/CAMEL-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3588 started by Hadrian Zbarcea. > JMS spec and JPA spec JARs should not be compile scoped by provided > ---

[jira] Resolved: (CAMEL-3588) JMS spec and JPA spec JARs should not be compile scoped by provided

[ https://issues.apache.org/jira/browse/CAMEL-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved CAMEL-3588. Resolution: Fixed Done in r1067384. > JMS spec and JPA spec JARs should not be compile sco

[jira] Assigned: (CAMEL-3588) JMS spec and JPA spec JARs should not be compile scoped by provided

[ https://issues.apache.org/jira/browse/CAMEL-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea reassigned CAMEL-3588: -- Assignee: Hadrian Zbarcea > JMS spec and JPA spec JARs should not be compile scoped by

[jira] Closed: (CAMEL-3503) Camel-extra 2.6.0 release

[ https://issues.apache.org/jira/browse/CAMEL-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea closed CAMEL-3503. -- Resolution: Duplicate Duplicate of CAMEL-3615 > Camel-extra 2.6.0 release > --

[jira] Updated: (CAMEL-3590) New component: camel-hzlq

[ https://issues.apache.org/jira/browse/CAMEL-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated CAMEL-3590: --- Fix Version/s: 2.7.0 > New component: camel-hzlq > - > >

[jira] Commented: (CAMEL-3590) New component: camel-hzlq

[ https://issues.apache.org/jira/browse/CAMEL-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990887#comment-12990887 ] Hadrian Zbarcea commented on CAMEL-3590: I also believe camel-hazelcast is more ap

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

[ https://issues.apache.org/jira/browse/CAMEL-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated CAMEL-3618: --- Fix Version/s: 2.7.0 > Upgrade to Jackson 1.7 > -- > > Ke

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

CAMEL-3603 is done. What's next? Dropping Junit 3? Hadrian On Feb 4, 2011, at 2:54 AM, Claus Ibsen wrote: > 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

[jira] Updated: (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 ] Hadrian Zbarcea updated CAMEL-3603: --- Assignee: Hadrian Zbarcea (was: Claus Ibsen) > Upgrade to JDK 1.6 as minimum (eg drop suppor

[jira] Resolved: (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 ] Hadrian Zbarcea resolved CAMEL-3603. Resolution: Fixed Done in r1067381. Updated javadoc config as well for jdk 1.6. > Upgrade

[jira] Issue Comment Edited: (CAMEL-3624) camel-smpp should unbind from SMSC before disconnecting

[ https://issues.apache.org/jira/browse/CAMEL-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990875#comment-12990875 ] Alex MadMind edited comment on CAMEL-3624 at 2/5/11 1:55 AM: -

[jira] Issue Comment Edited: (CAMEL-3624) camel-smpp should unbind from SMSC before disconnecting

[ https://issues.apache.org/jira/browse/CAMEL-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990875#comment-12990875 ] Alex MadMind edited comment on CAMEL-3624 at 2/5/11 1:55 AM: -

[jira] Commented: (CAMEL-3624) camel-smpp should unbind from SMSC before disconnecting

[ https://issues.apache.org/jira/browse/CAMEL-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990875#comment-12990875 ] Alex MadMind commented on CAMEL-3624: - Added your chages to camel-smpp 2.6.0, recompil

[jira] Commented: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990849#comment-12990849 ] Guillaume Nodet commented on CAMEL-3519: Well, even with fixing the first exceptio

[jira] Assigned: (CAMEL-3625) Testing in Intellij IDEA

[ https://issues.apache.org/jira/browse/CAMEL-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edstrom Johan reassigned CAMEL-3625: Assignee: Edstrom Johan > Testing in Intellij IDEA > > >

[jira] Created: (CAMEL-3625) Testing in Intellij IDEA

Testing in Intellij IDEA Key: CAMEL-3625 URL: https://issues.apache.org/jira/browse/CAMEL-3625 Project: Camel Issue Type: Improvement Reporter: Edstrom Johan Priority: Minor When running cam

[jira] Issue Comment Edited: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990747#comment-12990747 ] Achim Nierbeck edited comment on CAMEL-3519 at 2/4/11 9:24 PM: -

[jira] Updated: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated CAMEL-3519: -- Attachment: Karaf-2.1.99-SNAPSHOT-walkthrough A complete list of steps to run this with the lat

[jira] Updated: (CAMEL-3622) Convert camel-jetty tests to use AvailablePortFinder

[ https://issues.apache.org/jira/browse/CAMEL-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tracy Snell updated CAMEL-3622: --- Attachment: jettyportpatch.txt Note camel-3593 must be installed first. > Convert camel-jetty tests

[jira] Issue Comment Edited: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990682#comment-12990682 ] Guillaume Nodet edited comment on CAMEL-3519 at 2/4/11 8:16 PM:

Re: [DISCUSS] - JMX - Enlisting MBeans only during starting routes

Sounds good. The only part I am not fond of is: > - Dynamic endpoints, producers and whatnot which is created after the > route is not enlisted. There are quite a few usecases that use dynamic endpoints, so jmx will effectively be useless for them. MBeans use a lot of memory for a large applicat

[jira] Commented: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990682#comment-12990682 ] Guillaume Nodet commented on CAMEL-3519: So the problem comes from the following e

[jira] Resolved: (CAMEL-3624) camel-smpp should unbind from SMSC before diconnecting

[ https://issues.apache.org/jira/browse/CAMEL-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-3624. - Resolution: Fixed Alex, thanks for reporting this. I applied a fix on trunk. Feel free to

[jira] Updated: (CAMEL-3624) camel-smpp should unbind from SMSC before disconnecting

[ https://issues.apache.org/jira/browse/CAMEL-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-3624: Summary: camel-smpp should unbind from SMSC before disconnecting (was: camel-smpp should u

[jira] Commented: (CAMEL-3624) camel-smpp should unbind from SMSC before diconnecting

[ https://issues.apache.org/jira/browse/CAMEL-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990647#comment-12990647 ] Christian Müller commented on CAMEL-3624: - Committed r1067240 > camel-smpp should

[jira] Created: (CAMEL-3624) camel-smpp should unbind from SMSC before diconnecting

camel-smpp should unbind from SMSC before diconnecting -- Key: CAMEL-3624 URL: https://issues.apache.org/jira/browse/CAMEL-3624 Project: Camel Issue Type: Improvement Components:

Re: [DISCUSS] - JMX - Enlisting MBeans only during starting routes

+1 Sounds good for me...

[jira] Issue Comment Edited: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990598#comment-12990598 ] Achim Nierbeck edited comment on CAMEL-3519 at 2/4/11 4:22 PM: -

[jira] Issue Comment Edited: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990598#comment-12990598 ] Achim Nierbeck edited comment on CAMEL-3519 at 2/4/11 4:20 PM: -

[jira] Commented: (CAMEL-3519) camel-web-console feature for Apache Karaf

[ https://issues.apache.org/jira/browse/CAMEL-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990598#comment-12990598 ] Achim Nierbeck commented on CAMEL-3519: --- I'll check with a pre-release version of Ka

[DISCUSS] - JMX - Enlisting MBeans only during starting routes

Hi I might as well have an email afternoon. I have though of writing this for a bit of time. Camel supports JMX, by enlisting various mbeans in the registry such as consumers, components, endpoints, routes, services, thread pools and so forth. This happens during creation of those resources on de

[jira] Commented: (CAMEL-3623) Allow to configure redelivery thread pool for error handler

[ https://issues.apache.org/jira/browse/CAMEL-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990569#comment-12990569 ] Claus Ibsen commented on CAMEL-3623: See nabble http://camel.465427.n5.nabble.com/Mess

[jira] Created: (CAMEL-3623) Allow to configure redelivery thread pool for error handler

Allow to configure redelivery thread pool for error handler --- Key: CAMEL-3623 URL: https://issues.apache.org/jira/browse/CAMEL-3623 Project: Camel Issue Type: Improvement

[jira] Created: (CAMEL-3622) Convert camel-jetty tests to use AvailablePortFinder

Convert camel-jetty tests to use AvailablePortFinder Key: CAMEL-3622 URL: https://issues.apache.org/jira/browse/CAMEL-3622 Project: Camel Issue Type: Improvement Components: came

Re: GenericFileOperationFailedException - Cannot rename file

Hi, I have tried using Camel 2.5 as well as 2.6 also. Both are giving me the same problem. On Fri, Feb 4, 2011 at 2:39 PM, Claus Ibsen wrote: > Hi > > Can you post on the Camel user forum, when its related to help or > issues using Camel. > > And try with Camel 2.6. Usually the issue on window

Re: GenericFileOperationFailedException - Cannot rename file

Hi, On Fri, Feb 4, 2011 at 2:39 PM, Claus Ibsen wrote: > Hi > > Can you post on the Camel user forum, when its related to help or > issues using Camel. > > And try with Camel 2.6. Usually the issue on windows is that the file > stream is "locked" somewhere. And you need to close that before it

Re: GenericFileOperationFailedException - Cannot rename file

Hi Can you post on the Camel user forum, when its related to help or issues using Camel. And try with Camel 2.6. Usually the issue on windows is that the file stream is "locked" somewhere. And you need to close that before it can rename the file. And sometimes its because windows is "slow" at det

[jira] Commented: (CAMEL-3621) Add OSGI-INF/bundle.info resource

[ https://issues.apache.org/jira/browse/CAMEL-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990553#comment-12990553 ] Jean-Baptiste Onofré commented on CAMEL-3621: - Here is an example of bundle.in

[jira] Created: (CAMEL-3621) Add OSGI-INF/bundle.info resource

Add OSGI-INF/bundle.info resource - Key: CAMEL-3621 URL: https://issues.apache.org/jira/browse/CAMEL-3621 Project: Camel Issue Type: Task Components: karaf Reporter: Jean-Baptiste Onofré

GenericFileOperationFailedException - Cannot rename file

Hi, I am trying to read an XML file, split it and move it to an error folder in case there is any failure. for that purpose, I have changed some of the tags in my XML file so that SAXParser will throw an exception and hence camel will move the file into error folder. The problem is that camel is

[jira] Resolved: (CAMEL-3601) Provide additional info for Karaf info command

[ https://issues.apache.org/jira/browse/CAMEL-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3601. Resolution: Fixed trunk: 1067174. Thanks for the patch. > Provide additional info for Karaf info

[jira] Assigned: (CAMEL-3601) Provide additional info for Karaf info command

[ https://issues.apache.org/jira/browse/CAMEL-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-3601: -- Assignee: Claus Ibsen > Provide additional info for Karaf info command > --

[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-tabpanel&focusedCommentId=12990536#comment-12990536 ] Claus Ibsen commented on CAMEL-3617: And this fixes a test on windows: 1067159 > Inco

[jira] Resolved: (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:all-tabpanel ] Claus Ibsen resolved CAMEL-3617. Resolution: Fixed Fix Version/s: 2.7.0 This should be fixed on trunk now. > Inconsistent fi

Build failed in Hudson: Camel maven 3 #1

See -- [...truncated 28858 lines...] at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)

Build failed in Hudson: Camel maven 3 » Camel :: Scala #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-velocity/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/m

Build failed in Hudson: Camel maven 3 » Camel :: MSV #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-mail/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/modules

Build failed in Hudson: Camel maven 3 » Camel :: XMLBeans #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-tagsoup/pom.xml to /home/hudson/hudson/jobs/Camel maven 3

Build failed in Hudson: Camel maven 3 » Camel :: QuickFIX/J #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-quartz/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/

Build failed in Hudson: Camel maven 3 » Camel :: JMX #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-jing/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/modules

Build failed in Hudson: Camel maven 3 » Camel :: JoSQL #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-jmx/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/module

Build failed in Hudson: Camel maven 3 » Camel :: Web #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-xstream/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/modu

Build failed in Hudson: Camel maven 3 » Camel :: AMQP #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-jms/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/modules

Build failed in Hudson: Camel maven 3 » Camel :: Nagios #1

See -- [HUDSON] Archiving /home/hudson/hudson-slave/workspace/Camel maven 3/camel-trunk/components/camel-netty/pom.xml to /home/hudson/hudson/jobs/Camel maven 3/mod

[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-tabpanel&focusedCommentId=12990497#comment-12990497 ] Claus Ibsen commented on CAMEL-3617: trunk: 1067124. > Inconsistent filename value wh

[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-tabpanel&focusedCommentId=12990490#comment-12990490 ] Claus Ibsen commented on CAMEL-3617: I found the problem, which happens when using abs

[Notice] Added hudson build with maven 3

Hi all, as I had a build failure that only appeared when using maven 3 I set up a hudson build that uses maven 3. The first build will probably fail at camel-web. Christian -- http://www.liquid-reality.de

[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-tabpanel&focusedCommentId=12990484#comment-12990484 ] Claus Ibsen commented on CAMEL-3617: Can you post an example of the paths from - ${que

[jira] Assigned: (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:all-tabpanel ] Claus Ibsen reassigned CAMEL-3617: -- Assignee: Claus Ibsen > Inconsistent filename value when move attribute is used with File compo

[jira] Updated: (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:all-tabpanel ] Jean-Michel Morel updated CAMEL-3617: - Affects Version/s: 2.6.0 this doesn't work either with 2.6.0. > Inconsistent filename va

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

Hi JB, yes that might be part of the problem. In #camel on irc Claus and I jsut discussed that it may be the combination of maven3 and slf4j that makes the build fail. Christian Am 04.02.2011 08:48, schrieb Jean-Baptiste Onofré: Hi Christian, Claus updated Camel trunk to use SLF4J as defa