[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ormf-dev] Jaxen revisted
|
I would love to do that but the EMO-IP would not grant permission. I
will forward their email for reference. I do not understand the
rationale but that is the way that is :-(
I agree with you about spinning wheels, but I also am concerned that
we get no community exposure till next Spring :-/
Joel
On 14 Oct 2008, at 09:04, Achim Loerke wrote:
I just read my initial findings on replacing Jaxen (memory gets
really weak when you grow older). To wrap it up: seems like no
little effort.
I would go the way other projects do with their non EPL components:
tell the user to download and install it separately. This seems
reasonable since this would be an interims solution which will go
away with some future release. I really don't want spend time on
migrating some software we will throw out a few month later.
Technically we could tell an alpha/beta tester to download the jar
and put it in some plug-in directory or we could define a plug-in
which will export the Jaxen classes and define an update site
outside the Eclipse domain (this would be the Subversive approach).
Achim
Joel Rosi-Schwartz wrote:
Hi,
I am a embarrassed to admit that I made a fundamental error when B.
and I were doing the planning exercise. The plan <http://www.eclipse.org/projects/project-plan.php?projectid=technology.ormf
> states that at the end of M1 we have "Available functional system
based on OSGi server". Well that is not quite the case because I
conveniently forgot that we still had the Jaxen dependency to
contend with. Sorry, sigh... and all that :-( The EMO-IP team has
said that there is not an issue with us using Jaxen in our local
workspace as long as it is not checked into SVN or distributed by
any means by us outside the team. This at least means that we can
do testing at the end of M1.
There are a couple of ways to handle this. The simplest of course
is to change the plan. The other is to tackle the modifications to
Dom4J to excise Jaxen. Personally I would prefer if we had an early
alpha out next month than wait until next March. Community feedback
even on a limited alpha basis would be very good IMHO. Not that I
want to skew the opinion of the team ;-)
We have several options on how to resource the work if that is the
way we decide to go. If Achim manages Yahya on CM possibly he has
the bandwidth to continue with this. Otherwise any one of Yahya,
Jojy or possibly Wolfgang (if he is back among the walking
living:-) Achim started doing the feasibility and scoping exercise
on this, so I think he is best place to guide this discussion.
Your thoughts please!!
Joel
P Please consider the environment before printing this e-mail.
Thank you.
http://
www
.etish
.org
http
://www.eclipse.org/ormf
------------------------------------------------------------------------
_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
--
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