it is based on the pom.xml from two days ago - so the test part is not working as on master.
the main difference is the the java sources and tests went into the jruby-core directory (jruby-core/src/main/java, jruby-core/test). for eclipse project use jruby-core and activate maven on eclipse and run 'mvn' to generate Constants.java and the java annotation generated classes. clean build on eclipse does not recompile the java annotation generated classes. if you run 'mvn -Pall' then you will see have the maven aggregator works thorugh the different artifacts. some of them are still empty dummies: jruby-complete, jruby-stdlib, jruby-dist. all others are just from the old maven config. 'mvn -P test' does work as before. well, the big thing is the extra jruby-core directory where the sources are located. but without that I was not able to use the maven support of eclipse and with that the maven aggregator is just plain maven default. - christian On Wed, Jul 3, 2013 at 9:17 AM, kristian <m.krist...@web.de> wrote: > > On Wed, Jul 3, 2013 at 7:31 AM, Charles Oliver Nutter <head...@headius.com > > wrote: > >> What else? > > > > readline and openssl depends on jruby-core-1.7.4 from maven central which > is not really nice especially if I think of OS distribution trying to > bootstrap a jruby build. > > yesterday I tried to get the whole thing working with eclipse and its > build-in maven support. there are a quite some changes needed (mostly > shifting things around). it is already working but still a clean build from > within eclipse corrupts the setup (somehow). I do not know how well IDEA or > Netbeans support maven and how they like our current setup. > > calling 'mvn' from maven is not nice but practical - I guess I am purist > and would like to see things more maven way. and I am sure the more we > stick to maven defaults the better it works with IDEs. anyways I do push > some proposal hopefully today on a branch which also solves how to build > all the extra maven artifacts. > > - christian > > >
