Hi Dwayne,


great to hear about your progress!



I still couldn’t manage to check in the WebTest sources to github yet. I
hoped, I would be able to do so this week, but I was completely absorbed
by other tasks.



Concerning your changes:

did you base on the subversion trunk for your changes?

Then there are a couple of alternatives how we could proceed:

1.       if you are done with the tests before I do the move to github I
can just give you commiter right on our subversion repo and you can commit
your changes

2.       alternatively, whether you are done or not:
it should be possible that I mark (tag) the imported state from svn in the
github git repo. This then is corresponding to the latest and last
subversion HEAD. You can do an update of your subversion sources, checkout
the git tag, copy your files over and use git to merge it with the changes
that maybe already have been commited to github ( I am no super git
expert, so I don’t know the exact procedure). As it is to be expected that
there are not many changes, if any at all, the git HEAD probably will
reflect the svn HEAD – and such you just can do a pull request in git, ...



I would prefer option 2 if none of you can see any fault  with it.



Thanks and regards,

Martin





From: [email protected] [mailto:[email protected]]
On Behalf Of Dwayne Miller
Sent: Freitag, 11. April 2014 14:41
To: [email protected]
Subject: [Webtest] Progress on upgrade of Webtest to HtmlUnit 2.14



Martin,



I have made a lot of progress with code changes to update Webtest to
HtmlUnit 2.14.  I’ve also added upgrade to ant 1.9.3, updated some of the
JavaDoc jar files to clean up the compile.



Still have a few tests failing due to changes in HtmlUnit behavior, but
working through them.  Biggest problem, which exists for me even in the
version downloaded from Webtest site, is an all too frequent app failure
to do “concurrent modification” exception thrown from getProperty().



Biggest question… there are many files changed…. so not sure how best to
get this to someone or what the new commit policy/procedure is.



Disclaimer: This message is intended only for the use of the individual or
entity to which it is addressed and may contain information which is
privileged, confidential, proprietary, or exempt from disclosure under
applicable law. If you are not the intended recipient or the person
responsible for delivering the message to the intended recipient, you are
strictly prohibited from disclosing, distributing, copying, or in any way
using this message. If you have received this communication in error,
please notify the sender and destroy and delete any copies you may have
received.

Reply via email to