[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682234#comment-16682234 ] ASF subversion and git services commented on PDFBOX-4374: - Commit 1846278 from til...@apache.org in branch 'pdfbox/branches/2.0' [ https://svn.apache.org/r1846278 ] PDFBOX-4374: remove log4j > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682236#comment-16682236 ] ASF subversion and git services commented on PDFBOX-4374: - Commit 1846280 from til...@apache.org in branch 'pdfbox/trunk' [ https://svn.apache.org/r1846280 ] PDFBOX-4374: remove log4j > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682237#comment-16682237 ] ASF subversion and git services commented on PDFBOX-4374: - Commit 1846281 from til...@apache.org in branch 'pdfbox/branches/2.0' [ https://svn.apache.org/r1846281 ] PDFBOX-4374: remove log4j > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682235#comment-16682235 ] ASF subversion and git services commented on PDFBOX-4374: - Commit 1846279 from til...@apache.org in branch 'pdfbox/trunk' [ https://svn.apache.org/r1846279 ] PDFBOX-4374: remove log4j > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[
https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682189#comment-16682189
]
Tilman Hausherr commented on PDFBOX-4374:
-
Something is cut off in your text at "{color:#33}that starts with "log4j" I
{color}".
> Switch from log4j to slf4j
> --
>
> Key: PDFBOX-4374
> URL: https://issues.apache.org/jira/browse/PDFBOX-4374
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
>Reporter: Mihai Nita
>Priority: Critical
>
> Hello,
> I would be nice to use slf4j instead of relying explicitly on log4j.
> ([slf4j.org|http://slf4j.org])
> There are adapters from slf4j to many logger implementations, one of them is
> log4j.
> The decision of which log engine does not belong in a library, it belongs to
> the user of that library.
> This was apparently done already by several Apache projects. Searching for
> slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo,
> EmpireDB, Oozie, Hadoop, and many others.
>
> I can offer a patch, I have done such migration before.
> Thank you very much,
> Mihai
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682185#comment-16682185 ] Tilman Hausherr commented on PDFBOX-4374: - The dependency in the parent is in dependency-management, so my understanding is that it is just about getting the correct version when it is used… and that's just in preflight test. Anyway, I have removed it now. In a next step (after builds on CI have worked) I'll also remove the entry in "Import-Package" in the pom files. > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682183#comment-16682183 ] ASF subversion and git services commented on PDFBOX-4374: - Commit 1846272 from til...@apache.org in branch 'pdfbox/trunk' [ https://svn.apache.org/r1846272 ] PDFBOX-4374: remove log4j > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682182#comment-16682182 ] ASF subversion and git services commented on PDFBOX-4374: - Commit 1846271 from til...@apache.org in branch 'pdfbox/branches/2.0' [ https://svn.apache.org/r1846271 ] PDFBOX-4374: remove log4j > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[
https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682146#comment-16682146
]
Mihai Nita commented on PDFBOX-4374:
Thank you for the fast answer!
I am building something using maven (and that uses PDFBox).
And I am getting this:
{{log4j:WARN No appenders could be found for logger
(org.apache.fontbox.ttf.PostScriptTable).}}
{{ log4j:WARN Please initialize the log4j system properly.}}
{{ log4j:WARN See [http://logging.apache.org/log4j/1.2/faq.html#noconfig] for
more info.}}
Checking the PostScriptTable code it does use Apache commons, indeed.
Digging a bit more it looks like it somehow it brings with it
org.apache.pdfbox:pdfbox-parent, and that lists log4j as a dependency
(see
[https://mvnrepository.com/artifact/org.apache.pdfbox/pdfbox-parent/2.0.12)]
Adding a log4.properties just for kicks and using format that starts with
"log4j" I
So it looks like the parent binds the Apache Commons Logging to log4j, hence
the error message...
I was able to solve this using jcl-over-slf4j...
But this is really the problem these days... you build something with various
libraries, and each one uses its own logging system.
So you end up with a mixture of several, and it is a pain.
In the last few years slf4j helped a lot, many libraries started to adopt it.
Somehow JCL seems left behind. The last release was in 2014, and can't be used
with anything more modern like logback, or log4j 2.
Of course, it is 100% your call if you want to stay with it.
I will still use PDFBox, as it is a great library, and I am grateful for it,
thank you!
But if you think that slf4j seems like a good idea, my offer to do the
migration stands :-)
And if you want to close this issue, I am also fine.
Thank you very much,
Mihai
> Switch from log4j to slf4j
> --
>
> Key: PDFBOX-4374
> URL: https://issues.apache.org/jira/browse/PDFBOX-4374
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
>Reporter: Mihai Nita
>Priority: Critical
>
> Hello,
> I would be nice to use slf4j instead of relying explicitly on log4j.
> ([slf4j.org|http://slf4j.org])
> There are adapters from slf4j to many logger implementations, one of them is
> log4j.
> The decision of which log engine does not belong in a library, it belongs to
> the user of that library.
> This was apparently done already by several Apache projects. Searching for
> slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo,
> EmpireDB, Oozie, Hadoop, and many others.
>
> I can offer a patch, I have done such migration before.
> Thank you very much,
> Mihai
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
[jira] [Commented] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681780#comment-16681780 ] Tilman Hausherr commented on PDFBOX-4374: - We're using Apache commons log, except for preflight tests. Where did you find log4j? > Switch from log4j to slf4j > -- > > Key: PDFBOX-4374 > URL: https://issues.apache.org/jira/browse/PDFBOX-4374 > Project: PDFBox > Issue Type: Bug > Components: Utilities >Reporter: Mihai Nita >Priority: Critical > > Hello, > I would be nice to use slf4j instead of relying explicitly on log4j. > ([slf4j.org|http://slf4j.org]) > There are adapters from slf4j to many logger implementations, one of them is > log4j. > The decision of which log engine does not belong in a library, it belongs to > the user of that library. > This was apparently done already by several Apache projects. Searching for > slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, > EmpireDB, Oozie, Hadoop, and many others. > > I can offer a patch, I have done such migration before. > Thank you very much, > Mihai > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
