[kepler-dev] Duplicated jar contents.

[Matt Jones]

Oh and another thing.  This is one reason why we NEED the automated 
tests for every actor and system component.  When a new jar is added, or 
the version of an existing jar is changed, running the tests should 
expose any runtime problems that might not show up at compile time.  So 
I can't emphasize enough: develop JUnit tests for your code, and develop 
effective workflow tests that exercise your actors.  We'll all be a lot 
better off in that scenario.

Matt

Kevin Ruland wrote:
> Jenny,
> 
> Can you please tell me which portions of the source tree compose scia so
> I can exclude it from my build and analysis?
> 
> Thanks
> 
> Kevin
> 
> 
> "Jenny" Guilian Wang wrote:
> 
> 
>>Hi,
>>
>>I agree with Shawn. I know that at least Jena uses a newer version of
>>xerces that is not compatible with the old xerces that Kweelt
>>requires. So I said, I am going to try the overlapping jars. If
>>another jar works for SCIA, I will get rid of the corresponding jar in
>>SCIA jar dir. I don't expect it is safe to simply remove them now,
>>instead I assume Kevin would just exclude the SCIA jars from build.
>>
>>Thanks,
>>
>>Jenny
>>
>> 
>>
> 
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matt Jones                                   Ph: 907-789-0496
jones at nceas.ucsb.edu                    SIP #: 1-747-626-7082
National Center for Ecological Analysis and Synthesis (NCEAS)
UC Santa Barbara     http://www.nceas.ucsb.edu/ecoinformatics
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~