9 Replies Latest reply on Aug 27, 2009 3:15 AM by Dinesh Reddy

    camel libraries in projects -  shouldn't deploy to server?

    Robert Yetman Newbie

      I've created a custom-bean to do some processing in my diagram/flow, and since that bean uses org.apache.camel.* methods/objects (such as Exchange), I have to add camel-core.jar to my project's classpath, which means it gets included into the final assembly which gets deployed to the server.   However, since camel-core.jar is already in the classpath, this is basically a duplicate copy.   So is there a way to tell eclipse to include it in the classpath for compilation in eclipse, but not to include it in the deployable object?

       

      What we're after is basically the equivalent of the maven  scope.

      Is this do-able?