After looking at this build file, I'm afraid I misspoke earlier. You've already got this thing building artifacts and publishing to a repository, which is what I thought was needed.
The actual process for getting a project key and submitting signed artifacts to maven central is something that I've never done, nor am I involved enough in the project to act as keymaster. Sorry y'all. On 11/16/10 1:52 PM, "Bryan Duxbury" <br...@rapleaf.com> wrote: >Everything we already have around Maven publishing can be found in our >build.xml file in lib/java. > >I'd be cool with putting a plugin into our contrib if that's the place for >it. Someone should reach out to that author and see if he wants it to be >included in our trunk. > >On Tue, Nov 16, 2010 at 10:49 AM, Florentine, Justin F. < >justin.f.florent...@espn.com> wrote: > >> I can help. Send me what you've got so far and I'll take a look at it >> later this week. I'd also be interested in the project blessing and >> maintaining a plugin to allow the thrift compiler to be integrated into >> Java and AS3 builds that use Maven. >> >> There is a plugin floating around here https://github.com/dtrott that >> hasn't had much movement. Can we approach the author about contributing >> it? We are already using it here at ESPN, and I for one would like to >>add >> AS3 bindings to it. >> >> On 11/16/10 1:41 PM, "Bryan Duxbury" <br...@rapleaf.com> wrote: >> >> >I've said it before, and I'll say it again: please, someone who knows >>how >> >this all works, help me figure this out. >> > >> >On Tue, Nov 16, 2010 at 10:10 AM, Ryan King <r...@twitter.com> wrote: >> > >> >> On Tue, Nov 16, 2010 at 1:11 AM, Luke Lu <thr...@vicaya.com> wrote: >> >> > I think THRIFT-363 (maven deploy?) is incorrectly marked as fixed. >> >> > HADOOP-6685 now depends on thrift. Without published maven >>artifacts, >> >> > it's quite annoying for any java projects that use ivy/maven for >> >> > external dependencies to use libthrift-<version>.jar >> >> >> >> Agreed. We've resorted to publishing to our own maven repo >> >> (maven.twttr.com) to get around this. I'd prefer to use a shared >>repo. >> >> >> >> -ryan >> >> >> > >> >Please consider the environment before printing this e-mail. >> >>
