Hi,
It would much easier to help if one can see your actual build.xml and
envirinment where they are used.. But If you are using jndi-lookup where is
jndi.properties located is it hardcoded into java code? Are your Junit
components run in server side -> this would explain classpath issues.
And if
Hi all
I will summarize my problem. We have a class path ref which refers to
jboss-all-client jar and other dependent jars. I am using this class path
ref in two places
In junit task and in my custom task definition
The process(lookup) what i do with the classes in jboss-all-client.jar is
same in b
Thanks Steve for your reply
I thought of avoiding asking this question... If it is a problem with java
apis, how come the lookup process in junit
test cases are working (JUNIT TASK)??
On 10/2/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
> Ramu Sethu wrote:
> > Hi all
> >
> > 'Tried my best
Ramu Sethu wrote:
Hi all
'Tried my best to solve this problem on my own, but i couldn't solve it. so
asking the experts
I will summarize again my problem. We have a class path ref which refers to
jboss-all-client jar and other dependent jars. I am using this class path
ref in two places
In junit
Hi all
'Tried my best to solve this problem on my own, but i couldn't solve it. so
asking the experts
I will summarize again my problem. We have a class path ref which refers to
jboss-all-client jar and other dependent jars. I am using this class path
ref in two places
In junit task and in my cust
On Tue, 2007-09-11 at 08:48 +0530, Ramu Sethu wrote:
> Both the junit task and custom task has the same class path ref id.
> Junit task works but my task fails with no class found exception
May be your task does not expand refids. Have you tried cut pasting the
classpath instead of referring to i
Can anybody provide some help on this?
On 9/5/07, Ramu Sethu <[EMAIL PROTECTED]> wrote:
> Hi prashant
> I did run in debug mode, verbose mode, checked the class in the jar. I
> do see the jar in class path when the build in debug mode.
>
> Actually junit task runs without any problem. Only the cus
Hi prashant
I did run in debug mode, verbose mode, checked the class in the jar. I
do see the jar in class path when the build in debug mode.
Actually junit task runs without any problem. Only the custom task
gives us problem
On 9/5/07, Prashant Reddy <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-09-
On Wed, 2007-09-05 at 14:56 +0530, Ramu Sethu wrote:
> hi
>
> We are working in EJB and we use jboss-all-clent.jar. We have custom
> task which makes use jboss-all-cleint.jar
>
> When we run our custom task with the taskdef which has
> jboss-all-client.jar in classpath, what we get is No class fo
hi
We are working in EJB and we use jboss-all-clent.jar. We have custom
task which makes use jboss-all-cleint.jar
When we run our custom task with the taskdef which has
jboss-all-client.jar in classpath, what we get is No class found error
. We avoided this by adding the jar in environment variab
10 matches
Mail list logo
