[ https://issues.apache.org/jira/browse/LOG4J2-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma updated LOG4J2-343: ------------------------------- Attachment: LOG4J2-343_20130815-1117+0900.patch Attached LOG4J2-343_20130815-1117+0900.patch resolves conflicts caused by the LOG4J2-353 refactoring. It also removes the (now unnecessary) {{@param <T>}} javadoc comments. > Remove the Generics from Appender > --------------------------------- > > Key: LOG4J2-343 > URL: https://issues.apache.org/jira/browse/LOG4J2-343 > Project: Log4j 2 > Issue Type: Improvement > Components: Core > Affects Versions: 2.0-beta8 > Reporter: Henning Schmiedehausen > Attachments: 0001-convert-Appender-to-not-use-Generics.patch, > LOG4J2-343_20130815-1117+0900.patch > > > As proposed on the mailing list, removing the Generic from Appender will make > the API more readable and easier to use. This is an updated patch which does > not touch the AbstractDatabase code. > If you use subversion, just apply the attached patch to trunk. It should > apply. > The easier way to deal with this patch is to do this: > {code} > % mkdir appender-patch > % cd appender-patch > % git svn init http://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk > % git svn fetch -r 1512793 > % git remote add hgschmie https://github.com/hgschmie/logging-log4j2.git > % git fetch hgschmie > % git cherry-pick $(git log hgschmie/appender-only | head -1 | cut -d' ' -f2) > {code} > which will apply the latest version of the patch automatically to the repo. > Then doing > {code} > % git svn dcommit > {code} > will put it into subversion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org