-
Notifications
You must be signed in to change notification settings - Fork 76
Should master be compilable? #15
Comments
Post conversion to maven, this builds now, but doesn't produce a runnable jar. README still talks about building with ant as well. |
It's all in progress. I'll be adding maven jazz to build a binary On Wed, 26 Aug 2015 at 16:54 Jason Dillon [email protected] wrote:
|
@cgruber okay good to get a reply back and know folks are on it. We are really interested to start using this. If you guys need any help with any of the maven bits, I'm more than willing to lend a hand, but doesn't seem to complex for what you are after. But still. |
I've got it. It's just been a matter of time, while I do other things On Fri, 28 Aug 2015 at 17:50 Jason Dillon [email protected] wrote:
|
Aaaand alot of time has gone by, and I apologize, but we're re-owrkign a lot of our internal open-source infrastructure and I got roped in. I will be attempting to fix all this and get #26 done this and next week. |
Part of what I need to do is move the external build bits into the internal repository so we can test it in eihter place, so changes that can't be built don't sneak in. |
mkay, offer to help still stands if you guys need help to get the mvn side of the config sorted |
@cgruber I see its compiling now, and the jar executes yay... but what is the state of the tool generally? I have a very simple internal git project that needs to be exposed as a public git repo, with very minor changes (omit the entire private/** tree) and replace the top-level README.md. Is MOE in its current state able to do that? If so can you point me at some current docs or an example of how that works? Thanks! |
Sorry - it's been a while, and I apologize. I've made strides. We decidedly use it a lot internally, so the state of it is good, but I have to sync out the docs and scrub them. (And fix the README.md obviously). Since this is compiling now, I"m going to close this issue, and open a few others. As to how it works, ping me ([email protected]) directly, and I can talk you through it. I'll be honest, I've simply not used it outside of google, and our integration tests are not yet open-sourced, so there may be rough edges. |
س![Uploading 94361897...] |
سك![Uploading 94361927...] |
Doesn't appear to work for me :-(
Ran into a problem a bit before when the ant build said it succeeded but the google auto-value processor actually aborted the build, generating a single .java file. Today though, looks like its failing for other reasons, but unsure if its related or not.
The text was updated successfully, but these errors were encountered: