Really, this was not really a problem for me.
I now use cvs version of jacobie and it now compiles with no problems.

I think I can help on JWebUnit.
I made some modifications :
- setWorkingForm was not implemented
- clickButton only clicked input buttons with type button, not submit 
buttons or input images).

But I did not yet submit a patch because I don't have made a junit test for 
that yet.

However, if you can give me access to repository, I think I can really help 
you.

Thanks,

C�dric

"Nicholas Neuberger - Home" <[EMAIL PROTECTED]> a �crit dans le 
message de news: [EMAIL PROTECTED]
> On Wednesday 27 April 2005 8:55 am, Daniel Serodio wrote:
>> Nick, I don't mean to be picky, and I hope you take this as constructive
>> criticism: These kind of disruptive changes must be made in a branch,
>> not HEAD. At the very least, tag the repository before "breaking the
>> build".
>
> Agreed.  Right now, there isn't much active development of the API but 
> myself.
> I didn't know it was disrupting anyone.   Since there is little 
> development
> on the project right now, I thought creating a branch was a bit overkill.
> Plus, CVS operations to SF.net can be extremly slow.
>
> If anyone is interested in helping....PLEASE ask.  There more help, the 
> faster
> these builds will occur.  This API has an ENORMOUS potential its just
> developed and maintained by very few developers.....I'm more of a give 
> person
> access to the repo as opposed to adding several patches to the patch list 
> and
> then later applying them.  Sometimes the patches are almost to old to 
> apply.
>
> Also, I made a ton of changes on my old workstation to my new laptop and
> wanted to synch.  If there were more active developers I probably would 
> have
> hesitated.   Plus, its extremely hard to debug not only jwebunit project
> code, but also jacobie project code.  To get a new build for jacobie I 
> have
> to run a maven build which that needs to be migrated to my laptop as well.
>
> I'll just have to create some temp jacobie.jar files and commit it to 
> jwebunit
> prior to commit.  This will eliminate the problem.  I just haven't gotten 
> to
> it yet.
>
> I hope you understand my pain. Thanks for the comment.
>
> See Ya,
>
> Nick Neuberger
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix 





-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Jwebunit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development

Reply via email to