[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ormf-dev] Jaxen woes
|
Thanks Achim. The estimate for refactoring Dom4J to get away from
Jaxen is what is really needed right now. That will not however give
you any insight into the Useme code, the idea is to fix dom4j and the
changes will be transparent to our code. What I know so far is that
there are 8 classes in dom4j that have jaxen dependencies.
If you want to look into EMF, that is great, but it is tangential to
the first step. I guess this is less than a days work to scope.
As far as timing, I would really like to know about dom4j sooner
rather than later as it will be one of the keys that will drive our
decision making process.
Iac, I agree with you concerning EMF...it is all a matter of
resourceing. More on that later this evening.
Cheers,
Joel
On 11 Aug 2008, at 10:51, Achim Loerke wrote:
Joel Rosi-Schwartz wrote:
Thanks for your comments Wolfgang. I want to give everyone a chance
to comment and discuss before reaching conclusions.
There was a very specific request made that has not been addressed
and I do not want it to get lost in an architectural
discussion. Who is willing to take on estimating the effort to
do this for dom4j?
Having a feeling for this will impact our decision, so it is time
for the hearty to step forward. Any takers?
I'm willing to look into the code and come up with a proposal on how
to migrate (and how long it might take) if we have a few weeks time
for this (i.e. it will be done end of August earliest). I think it
is a good way to get into the code by planing a refactoring. I
assume that Barbara and Joel are available for some kickstart help.
I would look into an "easy migration" first and then try to estimate
the cost for a switch to EMF (which I would prefer). I'm not really
fluent using EMF so this part would be a "high risk" approach. If
someone with a more in depth knowledge of EMF would take this part
(or review my findings) things would be a lot easier.
Achim
<Achim_Loerke.vcf>_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
