René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Logging broken when first argument is an element","articleBody":"While working on https://github.com/androidannotations/androidannotations/issues/2143 I found that for some places the logging might be broken.\r\n\r\ne.g.\r\nhttps://github.com/androidannotations/androidannotations/blob/074df636fbd482cea3f797eece296524a877fd67/AndroidAnnotations/androidannotations-core/androidannotations/src/main/java/org/androidannotations/internal/process/ModelProcessor.java#L203\r\n\r\nresults in the message:\r\n\u003e 17:54:26.825 [Task worker for ':' Thread 2] ERROR o.a.i.p.ModelProcessor:203 - Skip element  because it's abstract\r\n\r\nThis happens as the signatures of the trace methods are\r\n```\r\nvoid trace(String message, Object... args);\r\nvoid trace(String message, Element element, Object... args);\r\n```\r\nInstead of using the first (and in this case desired version) the compiler uses the second version of `trace` as the first parameter after the message is an `Element` adn so it is not usedas replacement for the `{}` the log message but the message (without a valuefor `{}`) is attached to the element.\r\n\r\nI think we should review all places where we use these logs and possibly even refactor the logger to avoid similar issues. maybe move the `element` in front of the string parameter?\r\n\r\n@WonderCsabo wdyt?","author":{"url":"https://github.com/dodgex","@type":"Person","name":"dodgex"},"datePublished":"2018-06-09T16:11:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2145/androidannotations/issues/2145"}