Re: Barracuda: Howto build with 1.3.1 + a question

Hi Jake,

you are right, I didn't run the tests first...

So you need at least to uncomment the references to junit.jar in 
build.xml to run the 'jars' target,
BUT the best solution is indeed to copy junit.jar in $ANT_HOME/lib. This 
is needed if you want to run the 'test' target.

I also had to add j2ee.jar in the classpath, since 
src_tests/org/enhydra/barracuda/plankton/TestStringUtil imports javax.sql.*
But I don't think it actually uses it, does it ? (I tried to comment out 
the import statement, and it worked)
Jikes is very sensitive about undue import statements. Maybe javac 
doesn't even notice it.

Anyway, if it is useless, maybe we should just remove the import 
javax.sql.* statement in TestStringUtil.java.

I also needed to put xalan in the classpath to generate the test report 
(j2ee.jar also did the trick since there is a copy of xalan in it).

I then ran the tests.

Every test passed, but one :

testPackageDirBuildFullBaseFileNameFailureName 2 should be as expected 
expected:<......> but was:<...\...>

junit.framework.ComparisonFailure: Name 2 should be as expected 
expected:<......> but was:<...\...>
at 
org.enhydra.barracuda.taskdefs.TestFileNames.testPackageDirBuildFullBaseFileName(TestFileNames.java:160)
0.010

I don't know if this is such a big deal...
So I can say Barracuda builds and compile just fine on my system (Debian 
LinuxPPC / IBM JDK 1.3.1)

Franck







Jacob Kjome wrote:
> 
> Hi Franck,
> 
> Because, at least under j2sdk1.4.x, the JUnit jar must exist in 
> ANT_HOME/lib in order for things to work properly.  Putting it in a 
> custom build.xml specified classpath doesn't cut it.  Were you actually 
> able to run the unit tests with JUnit jar in WEB-INF/jars and only 
> reference via the custom build.xml classpath?  Try commenting that back 
> out and put the JUnit jar in ANT_HOME/lib.  That is really where it 
> should go anyway.  Let me know if the tests run properly.  Sorry, I have 
> no experience using Ant or Barracuda with IBM's JDK and haven't used 
> Sun's JDK 1 3.x for quite a while.  I currently use j2sdk1.4.1_01.
> 
> BTW, you are right to have downloaded Ant-1.5.1.  That is required for 
> the current CVS and you were also right to replace the XercesImpl.jar 
> with the Xerces that comes with Barracuda.  In j2sdk1.4.x you could 
> solve the Xerces issue by leaving the ones that come with Ant alone and 
> just put Xerces-1.4.1-xmlc-2.1.jar in JAVA_HOME/jre/lib/endorsed.
> 
> Jake
> 
> At 02:03 PM 11/30/2002 +0100, you wrote:
> 
>> Hi all,
>>
>> I just checked out a clean fresh CVS version of Barracuda, as my local 
>> directory was quite screwed up.
>>
>> I'm using jdk 1.3.1 from IBM.
>> So no endorsed directory...
>>
>> What I had to do is :
>>
>> 1) download and install ant's latest version (was 1.5.1).
>> 2) replace xercesImpl.jar in $ANT_HOME/lib with 
>> Barracuda/WEB-INF/jars/xerces-1.4.4-xmlc-2.1.jar
>> 3) uncomment references to junit.jar in Barracuda/src/build.xml
>>
>> I also created a build.properties file in Barracuda/src with 
>> build.compiler=jikes in it, but of course, this is only an option 
>> (although jikes is free and fast, mucu faster than sun's javac).
>>
>> Just a question, is there a reason why references to junit.jar are 
>> commented out in build.xml ?
>>
>>
>> Franck
>>
>> _______________________________________________
>> Barracuda mailing list
>> [email protected]
>> http://www.enhydra.org/mailman/listinfo.cgi/barracuda
>> FAQ - http://www.jguru.com/faq/Barracuda
> 


_______________________________________________
Barracuda mailing list
[email protected]
http://www.enhydra.org/mailman/listinfo.cgi/barracuda
FAQ - http://www.jguru.com/faq/Barracuda