{"issue":{"created_at":"2011-12-12T21:05:18Z","state":"open","updated_at":"2011-12-13T21:48:46Z","user":{"gravatar_id":"8ccf2bfccb6b570c4fae81e50dd80ed8","id":63777,"url":"https://api.github.com/users/caniszczyk","login":"caniszczyk","avatar_url":"https://secure.gravatar.com/avatar/8ccf2bfccb6b570c4fae81e50dd80ed8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":2,"body":"In Java land, it makes sense to move to a maven-based build. This would make the build simpler for pycascading and also make it easier for external contributors to build the project. At the moment, the build consists of a lot of hard-coded paths in Ant files which isn't good. Furthermore, moving to Maven would allow us to contribute the pycascading artifacts to Maven central which would make things even easier for potential consumers.","assignee":null,"id":2528512,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"number":1,"title":"Move to a maven-based build","closed_at":null,"html_url":"https://github.com/twitter/pycascading/issues/1","url":"https://api.github.com/repos/twitter/pycascading/issues/1","milestone":null},"action":"created","comment":{"created_at":"2011-12-13T21:48:46Z","updated_at":"2011-12-13T21:48:46Z","user":{"gravatar_id":"8ccf2bfccb6b570c4fae81e50dd80ed8","id":63777,"url":"https://api.github.com/users/caniszczyk","login":"caniszczyk","avatar_url":"https://secure.gravatar.com/avatar/8ccf2bfccb6b570c4fae81e50dd80ed8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Between maven central and conjars.org, I'm pretty sure the necessary libraries are available (even cascading 2.0 stream).\r\n\r\nThis is more of a nice to have at the moment until you decide to tag and release pycascading somewhere.","id":3130565,"url":"https://api.github.com/repos/twitter/pycascading/issues/comments/3130565"}}