> [...]  Eclipse tries to keep up to date with libraries shipped. Quite
> often the effort of moving to new versions of a library (e.g. lucene)
> requires changes in Eclipse itself

Is this level of backward non-compatibility typical in Java?

> and Fedora being ahead/behind with versions puts too much burden on
> the maintainer. This is the number two item when classified by time
> spent.

Fedora could ship some frozen/LTS versions of libraries, if these exist
and do not constitute a security problem.  If that's not an option
either, to this outsider it looks like building on quicksand, paddling
as fast as possible to stay above the mud.

- FChE
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to