[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ormf-dev] Jaxen woes
|
Achim,
I agree with you, really, that changing dom4j is less than ideal. The
question is, though, is it doable and if it is we need to consider
whether or not we "have to" given resourcing and goals. One of the
reasons I considered this approach is because another Eclipse project
in the same situation with Jaxen modified Jdom in the manner we are
discussing. That worked for the foundation. But you are absolutely
right in the the the first thing for you to check is the dom4j licence
to see the repercussions of altering code.
Thanks again,
Joel
On 12 Aug 2008, at 08:44, Achim Loerke wrote:
Joel Rosi-Schwartz wrote:
Thanks Achim. The estimate for refactoring Dom4J to get away from
Jaxen is what is really needed right now.
Obviously I missed your point completely.
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.
I don't like this approach. It forces us to change other peoples
code (which is hopefully covert by their license) and have to go
with this code through IP. I will have a look at dom4j anyway, maybe
there is another solution.
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.
I'll start today and will get back to you this week, hopefully on
Thursday.
Achim
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450
<Achim_Loerke.vcf>_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
