Thanks, but I have an issue with the way classpath is constructed.
Currently the classpath includes somelib-1.0.jar and when I pass in the
patched jar say 'somelib-2.0.jar' via --classpath option then the new
patched jar seems to be appended to the java classpath. I would like it to
be prepended so that the patch fixes the issue.


On Thu, Jan 15, 2015 at 11:14 AM, Mike Keane <[email protected]>
wrote:

>  Agh, I didn't read thoroughly.  I was assuming you had written custom
> implementations.  The flume-ng script uses the jars out of lib/
>
> I'm not sure if their is a mvn target like mvn
> dependency:copy-dependencies to copy the dependencies to
> ${FLUME_HOME}/lib/
>
> -Mike
>
>
>  ------------------------------
> *From:* Buntu Dev [[email protected]]
> *Sent:* Thursday, January 15, 2015 12:57 PM
> *To:* [email protected]
> *Subject:* How to override jars in java classpath
>
>   Hi -- I'm passing the jars that have patches and would like to use the
> patched jars instead of the ones in the java classpath. When I pass to
> 'flume-ng agent .. --classpath ..', I still see the old jars ahead of the
> patched jars. How can I override the default jars?
>
>  Thanks!
>
>  This email and any files included with it may contain privileged,
> proprietary and/or confidential information that is for the sole use
> of the intended recipient(s).  Any disclosure, copying, distribution,
> posting, or use of the information contained in or attached to this
> email is prohibited unless permitted by the sender.  If you have
> received this email in error, please immediately notify the sender
> via return email, telephone, or fax and destroy this original transmission
> and its included files without reading or saving it in any manner.
> Thank you.
>

Reply via email to