Eliminating the ned to have certain jars in path while running agent

packaging rvmonitorrt.jar and aspectjweaver.jar with the generated agent.jar.

@seriousamlqz, @yzhang90, please review
Can you throw an exception and stop the generation process?

Best,

Yi

> On Sep 15, 2014, at 9:35 PM, Owolabi Legunsen <notifications@github.com> wrote:
> 
> In src/main/java/javamop/GenerateAgent.java:
> 
> >              // directory to hold compiled library files
> >              // Copy in all the .class files for all the monitor libraries
> >              new File(outputDir, "mop").renameTo(new File(agentDir, "mop"));
> > -            
> > +
> > +            //remove extracted jars to make agent lighter weight
> > +            if (!actualWeaverFile.delete()) {
> > +                System.err.println("(delete) Failed to delete weaver jar");
> > +                return;
> Good point. One reason it might fail to delete is if the user doesn't have the right permissions. If this is is the case, who knows what else might not work properly after the agent is generated due to permissions. With the way the code is written, it's hard for me to give an example of how that might happen but you never know. Let me know if I should go ahead and let the agent be generated if this step fails.
> 
> —
> Reply to this email directly or view it on GitHub.