Re: FOP and Avalon
Thanks Glenn, it may come to that. -- View this message in context: http://apache-fop.1065347.n5.nabble.com/FOP-and-Avalon-tp44302p44309.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP and Avalon
There has been no discussion that I'm aware of. You are welcome to submit a patch making the necessary changes. On Thu, Aug 11, 2016 at 1:36 PM, jdebinder <debin...@us.ibm.com> wrote: > The last question on this topic was back in 2007. I also see a couple of > more recent posts about the Maven link to Avalon 4.3.1. I have to repeat > the question about removing the dependency on Avalon. As now even the > Excalibur project has also been retired as of 2010. I work on a product > for > IBM and due to security risks we are required to remove all frameworks that > are no longer supported. Since FOP depends on Avalon we will also have to > remove our dependency on FOP and try to find something to replace it. > > Is there any more thought to removing the dependency on the Avalon > framework? > > > > -- > View this message in context: http://apache-fop.1065347.n5. > nabble.com/FOP-and-Avalon-tp44302.html > Sent from the FOP - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > >
FOP and Avalon
The last question on this topic was back in 2007. I also see a couple of more recent posts about the Maven link to Avalon 4.3.1. I have to repeat the question about removing the dependency on Avalon. As now even the Excalibur project has also been retired as of 2010. I work on a product for IBM and due to security risks we are required to remove all frameworks that are no longer supported. Since FOP depends on Avalon we will also have to remove our dependency on FOP and try to find something to replace it. Is there any more thought to removing the dependency on the Avalon framework? -- View this message in context: http://apache-fop.1065347.n5.nabble.com/FOP-and-Avalon-tp44302.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
FOP and Avalon
Hello there, I have been browsing the archive and I have read old messages regarding the dependencies between FOP and the Avalon framework. As far as I understood FOP uses the logging and configuration utilities from Avalon and I have read that there is already some work done to use commons-logging instead. Any lans to use commons-configuration as well? In summary is the latest release (0.93) Avalon-free or are there any plans to have an Avalon-free release in the near future? My concerns are due to the fact that our applications that uses FOP for report generation, and I would like to plan ahead all the details of the support issues. Thanks for the help and best regards, J. -- View this message in context: http://www.nabble.com/FOP-and-Avalon-tf4129121.html#a11742030 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP and Avalon
Hi Javier, The Avalon dependencies are minimal in the latest trunk build (and the forth coming 0.94 release). FOP uses Apache Commons logging which allows you to chose which ever logging implementation you desire. The old configuration dependencies are now minimal, I abstracted all that code out of the renderers, and it now resides in a series of Configurator classes which could be easily overriden/rewritten with different implementations in the future. Adrian. Javier Salado wrote: Hello there, I have been browsing the archive and I have read old messages regarding the dependencies between FOP and the Avalon framework. As far as I understood FOP uses the logging and configuration utilities from Avalon and I have read that there is already some work done to use commons-logging instead. Any lans to use commons-configuration as well? In summary is the latest release (0.93) Avalon-free or are there any plans to have an Avalon-free release in the near future? My concerns are due to the fact that our applications that uses FOP for report generation, and I would like to plan ahead all the details of the support issues. Thanks for the help and best regards, J. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP and Avalon
On 05.07.2005 16:48:57 Chris Bowditch wrote: Wiström wrote: snip/ 1. Is there any plan on removing the dependency to Avalon on later versions on FOP? Yes, the logging part of avalon has been replaced by Apache Common Logging in the development version. However, there are some pieces of code that still require avalon. I'm not sure how much work it would be to remove it completely, but I think its on the TODO list. I't not on my TODO list. :-) I don't see a reason to remove it, especially since the functionality delivered by the configuration package would have to be replaced somehow. snip/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP and Avalon
Welcome back from the wildnerness :-) Jeremias Maerki wrote: On 05.07.2005 16:48:57 Chris Bowditch wrote: Yes, the logging part of avalon has been replaced by Apache Common Logging in the development version. However, there are some pieces of code that still require avalon. I'm not sure how much work it would be to remove it completely, but I think its on the TODO list. I't not on my TODO list. :-) I don't see a reason to remove it, especially since the functionality delivered by the configuration package would have to be replaced somehow. Thats OK, I didnt mean to imply it was on any individuals TODO list, but I seem to remember it being discussed whether avalon should be removed on fop-dev. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
