the my current branch does almost everything like $ ant there are some naming issues: lib/jruby-ng.jar is the jar maven produces BUT it is difficult to get the "-ng" away :( same with lib/jni which contains the native libs unpacked from com.github.jnr:jffi:native:1.2.5
actually there following native jars missing in the above artifact: ppc-AIX sparcv9-SunOS x86_64-FreeBSD the lib/jruby-ng.jar is almost the same as lib/jruby.jar (from the ant build) but some little differences and yecht is still missing as an artifact. and the manifest did not see any attention, i.e. is just some default. regarding the joda timezones - that can be done similar as the ant script BUT it would be much easier to make its own maven module (jruby-timezones artifact) out of it, then it is just a simple dependency which gets embedded and the update is the same procedure as all other artifacts. - christian On Wed, Jun 26, 2013 at 10:27 AM, kristian <m.krist...@web.de> wrote: > > > > On Wed, Jun 26, 2013 at 12:06 AM, Charles Oliver Nutter < > head...@headius.com> wrote: > >> Ahh well *generating* the pom.xml from the ruby-maven sounds like a >> great solution! That would certainly be less work to maintain over >> time, and those of us maintaining it will have ruby-maven available >> anyway. >> >> Let me know if there's anything I can do to rework AnnotationBinder >> and the invoker stuff. Those pieces have bene in dire need of >> refactoring for quite some time, and I'll make any changes necessary >> to help the mavenization. >> >> > I did a crud patch to avoid error on the missing config file > > https://github.com/mkristian/jruby/commit/42fdb59851e6ed799a7a945e5b8e0e0884b66a3f > > but with the AnnotationBinder it will be very helpful indeed if it would > honour the "-s path/to/genreated/sources" option of javac. maven usese > target/generated-sources/annotations as default but allows me to > reconfigure it. > > currently I tweak maven to use the same directory structure as ant which > allows me to use both at the same time. but after ant is gone there is no > need to have a build directory and a target directory (which is hardcoded > by some plugins) and we should/could move to "target" only. that will > reduce a couple of tweaks from pom as well. > > - christian > > > - Charlie >> >> On Tue, Jun 25, 2013 at 1:47 PM, kristian <m.krist...@web.de> wrote: >> > ok, >> > >> > with tzdata I have better idea. the Constants.java is almost done >> already. >> > the next big thing is the populators and invokers. the >> AnnotationBinder.java >> > has hardcoded paths which makes life just a bit harder. overall the >> maven >> > stuff will be first less efficient than what ant does, like the ant >> build >> > has a lot of conditions which I just do not have in maven (maven just >> > executes one phase after the other). >> > >> > about ruby-maven: I usually check in the pom.xml which ruby-maven >> generates >> > as well, i.e. any user who has just maven installed can use the build >> > system. only when you need to work on the build system you need >> ruby-maven >> > to translate the pom.rb (Mavenfile) to pom.xml (and then ruby maven >> executes >> > proper maven with that pom.xml) - so to say it is just a thin wrapper >> with >> > ruby DSL around maven. >> > >> > starting jruby of the build is the tricky part - I guess I need to copy >> the >> > jars into the right place. >> > >> > - christian >> > >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >
