well, I guess the important thing here is get it uniform among all the artifacts managed my the jruby team. whether all be codehaus or all be sonatype that is a matter of taste - I guess.
but be aware that maven central has mirrors and it can take even longer to get artifacts on those mirrors - and some mirrors are just faster than maven central ;) - christian On Mon, Jun 24, 2013 at 4:59 PM, Thomas E Enebo <tom.en...@gmail.com> wrote: > > > > On Sun, Jun 23, 2013 at 4:49 PM, Charles Oliver Nutter < > head...@headius.com> wrote: > >> On Sun, Jun 23, 2013 at 4:33 PM, kristian <m.krist...@web.de> wrote: >> >> A quick list, scanning build_lib... >> >> >> >> Already being published to Maven for releases (but not snapshots): >> >> >> >> bytelist >> >> invokebinder >> >> jcodings >> >> jffi >> >> jnr-constants >> >> jnr-enxio >> >> jnr-ffi >> >> jnr-netdb >> >> jnr-posix >> >> jnr-unixsocket >> >> jnr-x86asm >> >> joni >> >> >> > >> > as far I remember most of them are already on oss.sonatype.org and when >> > using the parent pom from sonatype then you have a snapshot repo (just >> > $ maven deploy >> > a snapshot) and a way to deploy them to maven central. and when using >> the >> > maven release plugin which is already configured then one just need to >> get >> > used to mantra >> > $ maven release:prepare >> > $ maven release:perform >> >> Some are released via codehaus. It might be worth moving everything to >> sonatype so it's all in the same place. >> > > Based on the fact it took sonatype over 3 days to push jnr-posix to maven > central I might question that goal. I at least would like to know what > went wrong. [I am not against moving them off of codehaus, but that issue > really dragged our last release out] > > -Tom > > >> >> >> Not in maven, but need to be: >> >> >> >> coro-mock (compile only) >> >> jsr292-mock (compile only) >> >> unsafe-mock (compile-only) >> >> yecht (1.8 yaml library...going away in 9k, but still needed in 1.7.x) >> >> yydebug >> >> >> > best use the same setup with sonatype >> >> coro-mock, unsafe-mock, and yecht I know we own. Tom can confirm the >> source of yydebug, but I assume it comes from the Jay codebase (we >> could just annex it and push to maven). jsr292-mock we don't own, but >> I can get permission to mavenize and publish it. >> >> > what about things like package rewriting which was/is done with >> ant-jarjar ? >> >> That will still need to happen somehow. I assume there's a similar >> plugin for maven, no? >> >> >> and ideally after the first build, >> >> you'd only need to run Rake. >> >> >> > ?? so rake is going to compile as well ? and jar packing ? >> >> No, Rake would call Maven if jruby.jar needs to be rebuilt. >> >> - Charlie >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > -- > blog: http://blog.enebo.com twitter: tom_enebo > mail: tom.en...@gmail.com >
