[
https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15635829#comment-15635829
]
Remko Popma commented on LOG4J2-1587:
-
Interesting. I only looked at revapi in LOG4J2
[
https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636033#comment-15636033
]
Mikael Ståldal commented on LOG4J2-1587:
The point of this issue is not to always
I am OK with moving the Scala modules to a separate Git repository and
build, given that we keep the groupId and artifactIds, so that the users
will not notice any difference. It would probably be a good idea to try to
keep the version numbers in sync also.
On Thu, Nov 3, 2016 at 11:39 PM, Ralph
If someone create the new Git repo and give me access to it, I can populate
it.
On Fri, Nov 4, 2016 at 12:18 PM, Mikael Ståldal
wrote:
> I am OK with moving the Scala modules to a separate Git repository and
> build, given that we keep the groupId and artifactIds, so that the users
> will not no
[
https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636357#comment-15636357
]
Mikael Ståldal commented on LOG4J2-1661:
Notify here when done:
https://github.c
For now, we could include the 2.12 API in the new repo. For simplicity, you
could pull all 3 versions into the same repo.
I was figuring a good way to do API versioning would be to match version
numbers of non-core things with whatever version of core it requires at
minimum.
On 4 November 2016 at
[
https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636431#comment-15636431
]
Mikael Ståldal commented on LOG4J2-1661:
Make sure we are on https://index.scala-
[
https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636652#comment-15636652
]
Mikael Ståldal commented on LOG4J2-1661:
Seems to be quite easy (apart from requi
[
https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636652#comment-15636652
]
Mikael Ståldal edited comment on LOG4J2-1661 at 11/4/16 3:18 PM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637019#comment-15637019
]
Gary Gregory commented on LOG4J2-1659:
--
The patch I posted does not work in JBoss be
[
https://issues.apache.org/jira/browse/LOG4J2-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637651#comment-15637651
]
Gary Gregory commented on LOG4J2-1659:
--
OK, I finally got shading to work with my ub
[
https://issues.apache.org/jira/browse/LOG4J2-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1651:
-
Attachment: Log4j2Plugins.xml
Example of the log4-core's DAT file as an XML file created with the
[
https://issues.apache.org/jira/browse/LOG4J2-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15638094#comment-15638094
]
Ralph Goers commented on LOG4J2-1659:
-
I am in agreement with both of these. I think
[
https://issues.apache.org/jira/browse/LOG4J2-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15638168#comment-15638168
]
Ralph Goers commented on LOG4J2-1651:
-
Well, that is a bit verbose.
> Makes the dat
I guess I need to create a Jira issue for Infra to get some git repositories
created. I am thinking of creating repos for the following:
1. log4j-scala
2. log4j-audit (a project I have been planning on working on for a while and
need to get off the ground soon)
3. log4j-tools (Maven, Ant, Gradle,
That sounds like a hefty pile already ;-)
Gary
On Nov 4, 2016 6:41 PM, "Ralph Goers" wrote:
> I guess I need to create a Jira issue for Infra to get some git
> repositories created. I am thinking of creating repos for the following:
> 1. log4j-scala
> 2. log4j-audit (a project I have been plann
[
https://issues.apache.org/jira/browse/LOG4J2-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15638663#comment-15638663
]
Gary Gregory commented on LOG4J2-1651:
--
Yeah, no kidding.
JAXB can't even handle co
17 matches
Mail list logo