Ok, updates... I have done:
* remove all compile-related targets from ant build and shell out to maven for compile. We still use jar targets in ant build because of some missing pieces. We are missing from the mvn build: * building openssl and readline into their own jars (in stdlib), as in ant build. They're done this way so we can upgrade them. Will it be easier to do this if we make them their own artifacts? See jar-jopenssl and jar-readline in ant build. * exclude openssl and readline from jruby.jar * copying BC jars into stdlib location Other than these I think we're close to the point we could ditch build_lib. It's not used for much now other than the BC jar copying, native unpacking (which I think is in maven build) and maybe a couple other things. SO...we're moving along. - Charlie On Fri, Jun 28, 2013 at 1:43 PM, Thomas E Enebo <tom.en...@gmail.com> wrote: > yeah I was just not aware that sonatype gives us easy access to snapshots > repo. Knowing this makes me feel better about doing it the maven way. > > -Tom > > > On Fri, Jun 28, 2013 at 1:35 PM, kristian <m.krist...@web.de> wrote: >> >> >> On Fri, Jun 28, 2013 at 7:16 PM, Thomas E Enebo <tom.en...@gmail.com> >> wrote: >>> >>> We frequently update a library in build_lib today with the intention to >>> release it before our next jruby release. >> >> >> >> @Tom I am sure you know this: the usual maven procedure is using snapshots >> - assuming that all of you can deploy snapshots releases for those >> frequently updated library. the maven-release-plugin is making sure that you >> do not release with any snapshot reference. but it might not turn into >> shapshots again after the release is done. at least with those frequently >> updated library if they have a sonatype setup it is straight forward to >> deploy a release: $ mvn deploy >> >> - christian >> > > > > -- > blog: http://blog.enebo.com twitter: tom_enebo > mail: tom.en...@gmail.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
