On Fri, Jun 28, 2013 at 9:03 PM, Charles Oliver Nutter <head...@headius.com>wrote:
> * 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. > so the maven way would be to copy the openssl and readline sources into their respective subdirectories and then we can copy them in their respective places. the question is whether they depend on jruby.jar ? anyways the problem of making modules is still a bit unclear to me. since we need have jruby-core, jruby-stdlib and jruby-complete and one aggregator project which needs to have packaging pom. simplest solution would be to have a pom-all.xml which builds all possible artifacts. or the other way around a pom-dev.xml (or Mavenfile) for development and pom.xml for building jars. after defining a default goal that means $ mvn -f pom-dev.xml or ruby-maven $ rmvn will build the jruby.jar to get the different jars with different profiles like $ mvn -Pjar-complete $ mvn -Pjar-core $ mvn -Pjar-openssl $ mvn -Pjar-readline etc. is easy. actually pom-dev.xml is something which stays local and will never be deployed as maven artifact as such. having said this making openssl and readline their own maven module/artifact is the better way to go. - christian
