Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread Thomas E Enebo
On Sun, Jun 23, 2013 at 4:49 PM, Charles Oliver Nutter wrote: > On Sun, Jun 23, 2013 at 4:33 PM, kristian wrote: > >> A quick list, scanning build_lib... > >> > >> Already being published to Maven for releases (but not snapshots): > >> > >> bytelist > >> invokebinder > >> jcodings > >> jffi > >>

Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread Thomas E Enebo
I only have one inline comment below. We both largely have the same organizing desires. -Tom On Sun, Jun 23, 2013 at 12:09 PM, Charles Oliver Nutter wrote: > Ok folks...the branching off of 1.7 is coming very soon, and I think > one of the biggest ticket items we need to do before then is reo

Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread Thomas E Enebo
On Sun, Jun 23, 2013 at 4:49 PM, Charles Oliver Nutter wrote: > On Sun, Jun 23, 2013 at 4:33 PM, kristian wrote: > >> A quick list, scanning build_lib... > >> > >> Already being published to Maven for releases (but not snapshots): > >> > >> bytelist > >> invokebinder > >> jcodings > >> jffi > >>

Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread Thomas E Enebo
Yoko, There are two goals I would like to see for 9k with these platforms in mind. I would like looser coupling so that conditionally only part of our codebase can be compiled. So if you are on a limited platform with no socket support you should be able to omit it and our codebase will still

Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread Joseph Athman
One thing I'd like to say in response to some of the negatives of Gradle is that by using the gradle wrapper ( http://www.gradle.org/docs/current/userguide/gradle_wrapper.html) you get the very nice benefit of being able to version your build tool along with your code. You won't have to deal with i

Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread kristian
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 - an

Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread Charles Oliver Nutter
On Mon, Jun 24, 2013 at 10:51 AM, Thomas E Enebo wrote: > yydebug did come from jay but I agree we should probably just publish it. > Probably for jay itself too even though it is not a Java library :) Ok, so that should be added to the "yet to be mavenized" list. Hopefully we would do it once an

Re: [jruby-dev] Pre-branch (1.7) reorg of codebase

2013-06-24 Thread Thomas E Enebo
It sounds we both have the same basic questions to answer. We can talk about this more over this week and maybe take something completely new like ripper and explore how we can re-org this into fitting our goals while not boiling the Maven ocean. -Tom On Mon, Jun 24, 2013 at 5:38 PM, Charles Ol