On Jul 1, 2013, at 12:03 PM, Charles Oliver Nutter <head...@headius.com> wrote:

> Ok, things are slowly falling together, so he's another update.
> 
> New working:
> 
> * tzdata stuff (waiting on confirmation from Hiro)

I can confirm this now. `mvn -Ptzdata` generates the desired jruby.jar 
containing the latest tzdata. While `mvn` generates jruby.jar for release (with 
tzdata bundled with joda-time's release).

> Known remaining:
> 
> * tests passing (they're closer but embed tests and a couple main
> tests still fail)
> * OSGi bnd bundle stuff from jar-jruby-dist into maven (I tried using
> Apache Felix plugin but could not get it to work right. Maybe this
> doesn't need to happen during normal package...only in maven artifacts
> we actually push?)
> * Scrubbing of build.xml to continue removing things mvn is doing for us.
> 
> Is there any way to get tests to not run during package, but still
> work for "test" goal (i.e. hardcoding skipTests is NOT a solution)?
> It's a serious impediment to have to run tests every time we package
> up a new jar locally.
> 
> - Charlie

NEW -> IDE targets need work. (https://github.com/jruby/jruby/issues/842 is the 
ticket on NetBeans, but Eclipse and IntelliJ may need some love as well.)


> On Sat, Jun 29, 2013 at 2:01 PM, Charles Oliver Nutter
> <head...@headius.com> wrote:
>> Done:
>> 
>>> * From old jar building: install spi services stuff under meta-inf
>>> * From old test runs: compile test files. I'm hoping these can be run
>>> as part of the maven build and we won't actually need to add them to
>>> the rake test runs (i.e. these can be our smoke tests during
>>> packaging)
>> 
>> I added in surefire test configs so tests are running, but they don't
>> pass yet (environmental oddities mostly).
>> 
>> Good news... jar-jruby ant target is now empty! jar-jruby-dist
>> piggybacks off it but is not building correctly (just the osgi bnd
>> stuff).
>> 
>> Known items remaining to do:
>> 
>> * get tests passing ;-)
>>> * Eliminate build_lib artifacts. I've started removing references to
>>> build_lib but have not removed most jars yet.
>>> * dist confirmation: need to confirm dist artifacts are building properly
>>> * cext as its own submodule: I think we should move cext to its own
>>> ext/ module like openssl and readline rather than move out of the repo
>>> entirely (for now)
>>> * psych as its own module: this is going to be merged into upstream
>>> psych gem soon so we need to start building it as a separate jar
>> 
>> - Charlie
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>    http://xircles.codehaus.org/manage_email
> 
> 

Reply via email to