Giters

cgdecker / vogar

Automatically exported from code.google.com/p/vogar

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Don't push extra copies of JUnit & KXML to the device

GoogleCodeExporter opened this issue · comments

commented 
The current build strategy sends the whole vogar.jar to the device for runtime. 
Although 
convenient, it may cause pain when there's multiple copies of the same code on 
the classpath.

Original issue reported on code.google.com by jessewil...@google.com on 23 Apr 2010 at 11:56

commented

Original comment by jessewil...@google.com on 17 Jun 2010 at 9:31

commented 
The device is using a different JUnit than the version bundled with vogar. This 
is causing problems. In particular, different versions of JUnit present string 
mismatches differently:
    junit.framework.ComparisonFailure: null expected:<[ISO-8859-1]> but was:<[UTF-8]>
vs.
    junit.framework.ComparisonFailure: expected:<ISO-8859-1> but was:<UTF-8>

The difference isn't major, but it makes our expectations files ugly. We should 
always use vogar's copy of JUnit.

Original comment by jessewil...@google.com on 8 Dec 2010 at 1:35