You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by Vincent Massol <vm...@pivolis.com> on 2003/05/13 19:12:03 UTC

task and HttpUnit

When running <cactifywar>, it says that I need to add HttpUnit. However,
HttpUnit is optional and only needed if I am using it... 

We have 2 options:
- not write this warning
- or say that HttpUnit is optional

BTW, if HttpUnit then nekohtml.jar (or jtidy.jar) and js.jar may also be
needed but the cactifywar task does not say anything about them.

Also, it may surprise users that HttpUnit is needed in the war whereas
it is only needed on the client side...

Chris, what do you suggest?

Thanks
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org


RE: task and HttpUnit

Posted by Vincent Massol <vm...@pivolis.com>.

> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 13 May 2003 22:28
> To: Cactus Developers List
> Subject: Re: <cactifywar> task and HttpUnit
> 
> Vincent Massol wrote:
> >>-----Original Message-----
> >>From: Christopher Lenz [mailto:cmlenz@gmx.de]
> >>Sent: 13 May 2003 19:22
> >>To: Cactus Developers List
> >>Subject: Re: <cactifywar> task and HttpUnit
> >>
> >>Vincent Massol wrote:
> >>
> >>>When running <cactifywar>, it says that I need to add HttpUnit.
> >
> > However,
> >
> >>>HttpUnit is optional and only needed if I am using it...
> >>>
> >>>We have 2 options:
> >>>- not write this warning
> >>>- or say that HttpUnit is optional
> >>>
> >>>BTW, if HttpUnit then nekohtml.jar (or jtidy.jar) and js.jar may
> >
> > also be
> >
> >>>needed but the cactifywar task does not say anything about them.
> >>>
> >>>Also, it may surprise users that HttpUnit is needed in the war
> >
> > whereas
> >
> >>>it is only needed on the client side...
> >>>
> >>>Chris, what do you suggest?
> >>
> >>There is another option: Require that the user adds HttpUnit.jar to
> >
> > the
> >
> >>cactified WAR explicitly:
> >>
> >>   <cactifywar ...>
> >>     ...
> >>     <lib file="${httpunit.jar}"/>
> >>   </cactify>
> >>
> >>I'm starting to feel that this would be the cleanest solution.
> >>What do you think about that?
> >
> >
> > +1
> >
> > -Vincent
> >
> 
> Hmm, for consistency, we should probably also remove the implicit
adding
> of HttpUnit and NekoHTML to the classpath for the <cactus> task?
> 
> Or do you have objections?

Nope, please go ahead! :-)

Thanks
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org


Re: task and HttpUnit

Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
>>-----Original Message-----
>>From: Christopher Lenz [mailto:cmlenz@gmx.de]
>>Sent: 13 May 2003 19:22
>>To: Cactus Developers List
>>Subject: Re: <cactifywar> task and HttpUnit
>>
>>Vincent Massol wrote:
>>
>>>When running <cactifywar>, it says that I need to add HttpUnit.
> 
> However,
> 
>>>HttpUnit is optional and only needed if I am using it...
>>>
>>>We have 2 options:
>>>- not write this warning
>>>- or say that HttpUnit is optional
>>>
>>>BTW, if HttpUnit then nekohtml.jar (or jtidy.jar) and js.jar may
> 
> also be
> 
>>>needed but the cactifywar task does not say anything about them.
>>>
>>>Also, it may surprise users that HttpUnit is needed in the war
> 
> whereas
> 
>>>it is only needed on the client side...
>>>
>>>Chris, what do you suggest?
>>
>>There is another option: Require that the user adds HttpUnit.jar to
> 
> the
> 
>>cactified WAR explicitly:
>>
>>   <cactifywar ...>
>>     ...
>>     <lib file="${httpunit.jar}"/>
>>   </cactify>
>>
>>I'm starting to feel that this would be the cleanest solution.
>>What do you think about that?
> 
> 
> +1
> 
> -Vincent
> 

Hmm, for consistency, we should probably also remove the implicit adding 
of HttpUnit and NekoHTML to the classpath for the <cactus> task?

Or do you have objections?

-- 
Christopher Lenz
/=/ cmlenz at gmx.de


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org


RE: task and HttpUnit

Posted by Vincent Massol <vm...@pivolis.com>.

> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 13 May 2003 19:22
> To: Cactus Developers List
> Subject: Re: <cactifywar> task and HttpUnit
> 
> Vincent Massol wrote:
> > When running <cactifywar>, it says that I need to add HttpUnit.
However,
> > HttpUnit is optional and only needed if I am using it...
> >
> > We have 2 options:
> > - not write this warning
> > - or say that HttpUnit is optional
> >
> > BTW, if HttpUnit then nekohtml.jar (or jtidy.jar) and js.jar may
also be
> > needed but the cactifywar task does not say anything about them.
> >
> > Also, it may surprise users that HttpUnit is needed in the war
whereas
> > it is only needed on the client side...
> >
> > Chris, what do you suggest?
> 
> There is another option: Require that the user adds HttpUnit.jar to
the
> cactified WAR explicitly:
> 
>    <cactifywar ...>
>      ...
>      <lib file="${httpunit.jar}"/>
>    </cactify>
> 
> I'm starting to feel that this would be the cleanest solution.
> What do you think about that?

+1

-Vincent

> 
> -chris
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org


Re: task and HttpUnit

Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
> When running <cactifywar>, it says that I need to add HttpUnit. However,
> HttpUnit is optional and only needed if I am using it... 
> 
> We have 2 options:
> - not write this warning
> - or say that HttpUnit is optional
> 
> BTW, if HttpUnit then nekohtml.jar (or jtidy.jar) and js.jar may also be
> needed but the cactifywar task does not say anything about them.
> 
> Also, it may surprise users that HttpUnit is needed in the war whereas
> it is only needed on the client side...
> 
> Chris, what do you suggest?

There is another option: Require that the user adds HttpUnit.jar to the 
cactified WAR explicitly:

   <cactifywar ...>
     ...
     <lib file="${httpunit.jar}"/>
   </cactify>

I'm starting to feel that this would be the cleanest solution.
What do you think about that?

-chris


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org