On Jul 1, 2009, at 1:14 AM, Ivan wrote:
I think the one is what need, no samples and testcases are included. But I found 1.3.1 is released, why not use the newest one ?
Newer would be better if we can get it to work. I set this up a few days ago and forgot the details... I think that I saw some problem and wasn't sure what was causing it and tried changing to an earlier dojo version. I didn't actually have any reason to think the problem was caused by dojo so very likely the more recent release should work.
And for the legacy dojo 0.4.3, how shall we handle it ? Like tomcat, maitaine a our own repo ?
Ideally I think we would migrate our code to up-to-date dojo. Unfortunately I have no idea how hard that would be. Does anyone? If we can't, I think there is some release of some 0.4.3 dojo, perhaps we can investigate using or repackaging it.
There's also dwr.... but I think working on one dependency at a time will be less confusing.
2009/7/1 David Jencks <firstname.lastname@example.org>
In my attempt to remove our svn repo I found that dojo releases a dojo-war that looks pretty similar to our repacked dojo war. I can make the build work with the substitution but I don't know enough about dojo to know if/what it breaks. Is there anyone who understands our use of dojo well enough to take a look and see if this replacement is plausible?
I recall some discussion in the distant past about not including all of dojo... I'm not sure if this is still a concern, but if the released dojo-war works and is too big we can use maven to come up with a smaller war.
See https://issues.apache.org/jira/browse/GERONIMO-4723 for my patch.