So I got SEAM from CVS (the jboss-seam module; Gavin said he uses 
jboss-seam-head but I'm assuming there's no meaningful difference).  I built it 
and ran the noejb example under Tomcat absolutely the very first time I tried 
it.  Woohoo!  Nice one, Gavin et al.!

Now I'm trying to run the TestNG tests.  And I get this:

C:\robj\dev\seam\jboss-seam\examples\noejb>ant testexample
  | Buildfile: build.xml
  | 
  | init:
  |      [echo] Build Seam on JBoss Hibernate3 Example 1.0
  | 
  | compile:
  | 
  | testexample:
  |      [copy] Copying 67 files to 
C:\robj\dev\seam\jboss-seam\examples\noejb\build\test
  | 
  | BUILD FAILED
  | C:\robj\dev\seam\jboss-seam\build.xml:176: No sourceDir is specified.
  | 
  | Total time: 0 seconds
  | C:\robj\dev\seam\jboss-seam\examples\noejb>ant -f build.tomcat.xml 
testexample
  | Buildfile: build.tomcat.xml
  | 
  | init:
  |      [echo] Build Seam on Tomcat Hibernate3 Example 1.0
  | 
  | compile:
  | 
  | testexample:
  | 
  | BUILD FAILED
  | C:\robj\dev\seam\jboss-seam\build.xml:171: Reference example.resources not 
found.
  | 
  | Total time: 1 second

So clearly it doesn't really want to work.  Should I bother trying to fix these 
build problems?  Or should I not expect the testng tests to work without JBoss? 
 If it's a small amount of work I'll do it, but if it's not, I won't.

Thanks!
Cheers,
Rob

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914356#3914356

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914356


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to