Re: [Sync4j-users] Build Test Failing Problems

[Simon So <ss...@cs...>]

> there a newer version of sync4j up with solves these errors?

Do you have another Unix machine/environment you can build?  Would another
environment help you to pin down your problem?

>     Also, the log files that you had mentioned earlier do not exist anywhere
> on my system. I am attaching two files with my mail : bash_profile.txt and
> output.txt..

The NoClassDefFoundException means our Unit tests classes are not
found by Junit.  If you look into the <junit> tag, it tells you where the
unit test classes are supposed to be (${classesdir}).  Have you looked into
that directory and make sure the unit tests are all there?

Since the test classes are not being run to begin with, no log files are
generated.

Based on your previous problems, classpath seems to be an issue.  You may
track down your problem by understanding what <junit> tag do first, esp.
the <classpath> <pathelement> fileset in <junit>.

>     The bash_profile file contains all the paths that I have set up for the
> system. The output.txt file contains the output of 'ant all' command in the
> sync4j build directory. I have another question: Is there a way to run the
> jar files in the j2ee server with the tests failing. In other words, is
> there a way to run sunc4j with the junit test cases failing? Also, when I go

What do you mean by running sync4j?  Currently, you need some clients to
make use of the API.  Junit is that client.  The client code written with
the client framework in the library does not do anything yet, because the
transport layer (http, let alone wsp and obex) has not been completed.

So the junit classes test on the server side only.  Yes, theoretically
speaking you can write a class to test, say, non ejb library classes
like Base64, etc.  Just point to the correct classpath.

> to: http://127.0.0.1:9191 which is where all the jars from the build are, I
> am unable to execute any jar. Each jar gives me a Smart Update Error: the
> jar file failed the security check. Is there any other way of opening these
> jar files and executing them? Any help would be much appreciated because
> this is slightly urgent as my deadline is fast approaching and I haven't
> been able to figure this out after much effort.
> Thanks

I don't think the jar is meant to be executable.  They are deployable
through the enterprise app container, though.

Best,
Simon


> On 3/17/02 5:56 PM, "Simon So" <ss...@cs...> wrote:
>
> > Hi Assad,
> >
> > You can find out why the junit tests fail by going to the output directory
> > (between build directory and src directory) and look at the junit test log
> > file.  For each test there is one log file corresponding to it.
> >
> > I cannot tell what error you are running into just by looking at this.
> > Don't count my words, but I suspect it's a classpath problem.
> >
> > If you don't run into deploy error, that will mean your J2EE server is
> > already running.  BTW, only Sync4jHttpServletTest and TestAllCactus
> > requires a running J2EE server.  The other tests should just go through.
> >
> > javadoc....  Maybe you should just run <docs> target and see what
> > happens.  The last time I check, it produces javadoc.
> >
> > Debug a little bit with the log files I mentioned.  It should give you
> > plenty of insights as of what's going on with your environment.
> >
> > Cheers,
> > Simon
> >
> >
> >
> > On Sun, 17 Mar 2002, Assad Jarrahian wrote:
> >
> >>
> >> Hi Simon,
> >>
> >> I did as advised by you in the previous email. I got the latest versions for
> >> ant and JDK. Now, the build is successful but all the junit tests fail. I am
> >> sending the build file reqults with the -debug option. That file is
> >> attached.
> >>
> >> Also, below is the output of the filed junit tests:
> >>
> >>  [junit] TEST sync4j.tests.Base64Test FAILED
> >>     [junit] TEST sync4j.tests.CommandIdentifierTest FAILED
> >>     [junit] TEST sync4j.tests.SyncBodyTest FAILED
> >>     [junit] TEST sync4j.tests.SyncHeaderTest FAILED
> >>     [junit] TEST sync4j.tests.SyncCapabilitiesTest FAILED
> >>     [junit] TEST sync4j.tests.MessageTest FAILED
> >>     [junit] TEST sync4j.tests.Sync4jHttpServletTest FAILED
> >>     [junit] TEST sync4j.tests.MetaInfoTest FAILED
> >>     [junit] TEST sync4j.tests.DeviceInfoTest FAILED
> >>     [junit] TEST sync4j.tests.ClientFrameworkTest FAILED
> >>     [junit] TEST sync4j.tests.cactus.TestAllCactus FAILED
> >>
> >> Inspite of these failing tests, it says that the build s successful. Can you
> >> please advise as to why these tests fail. Also, in the output directory (the
> >> one formed after the build), there is a javadoc directory. That directoryis
> >> empty. Is that suppose to be so? I don't have and can't find any
> >> documentation as to how to actually run the client and the server.
> >>
> >> Could you kindly advise. Thanks for your time and cooperation in advance.
> >> -Assad
> >>
> >>
> >>
> >> On 3/16/02 5:44 PM, "Simon So" <ss...@cs...> wrote:
> >>
> >>> Hi Assad,
> >>>
> >>> I got the previous problem yesterday by building with Forte for Java's
> >>> 3.0 ANT facility.  You never mentioned how you build.  So I believe you
> >>> are probably running some IDE with ANT support, but the IDE is not
> >>> supporting the latest ANT.
> >>>
> >>> Plus, the first line of your debug file says ANT 1.3.  So now the
> >>> situation is like, if you are using JDK 1.1.7 to compile Sync4j, we can't
> >>> guarantee or support 1.1.7 will work for Sync4j.
> >>>
> >>> Anyway, keep the line regarding manifest file.  I believe you really need
> >>> the latest ANT, 1.4.1.  If IDE happens to be your problem, download a better
> >>> IDE.  The latest NetBeans 3.3.1 supports ANT 1.4.1 out of the box.  Hope
> >>> that
> >>> will solve the problem.
> >>>
> >>> Another resort is to use command prompt to build instead of IDE...  I
> >>> started out with command prompt, built without any problems, thought
> >>> about being cool to use IDE, PRESTO, problems.  If you already use command
> >>> prompt, the problem is so very apparent then -- use the latest ANT.
> >>>
> >>> As of how to enforce 1.4.1, it's your machine environment issue.  I really
> >>> don't know how you set things up et al.  You just have to debug and make
> >>> sure 1.4.1 libraries got the absolute ahead of everyone in the CLASSPATH.
> >>>
> >>> Hang in there.  Looking forward to your contribution in Sync4j.
> >>>
> >>>
> >>> Cheers,
> >>> Simon
> >>>
> >>> BTW: ear is in a built-in task, not an optional task.
> >>>
> >
>
>