New README.md

@seriousamlqz, @yzhang90, @grosu Please review

@grosu, please assign someone who knows better than me to write the Static Weaving Section: I don't use that option.
OK, I agree that we do not want to maintain/duplicate them.  So where are they located right now?  I think we should tell the people at least what -usedb does, and that it is completely equivalent to going to where these properties are located, copying them in a local machine and then executing javamop normally with their folder(s) as input.  Is there any simple command that grabs a folder at some URI and copy it locally?  Hm, or even better, it would be nice to also allow URI's, besides mop files and folders, and have javamop grab the properties from there.  Can you add this as a separate issue?

Thanks,
Grigore


________________________________
From: Owolabi Legunsen [notifications@github.com]
Sent: Saturday, September 27, 2014 3:47 PM
To: runtimeverification/javamop
Cc: Rosu, Grigore
Subject: Re: [javamop] New README.md (#89)


In README.md:

>
> -Example) javamop -d examples/FSM/ examples/FSM/HasNext.mop
> +```javamop -agent [-n agentName] [-v] [-d <target directory>] -usedb```


I have now explained what this -usedb option does. @grosu<https://github.com/grosu>, if you insist on keeping these properties as part of the JavaMOP, I can very easily do so. I don't think this is in our best interest, though, on the long term, as we'd be duplicating them in multiple place in our various repos. We currently don't have infrastructure to keep these various repos in synch, and that is why I prefer to pull them from a central location for now. We already had issues recently when multiple locations for the properties diverged independently.

—
Reply to this email directly or view it on GitHub<https://github.com/runtimeverification/javamop/pull/89/files#r18125718>.