[ 
https://issues.apache.org/jira/browse/LOG4J2-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324810#comment-15324810
 ] 

Ralph Goers commented on LOG4J2-1414:
-------------------------------------

I have a fix for the git checkout info to point to the actual release tag when 
the site is generated. I will be checking that in tonight.

There is no surefire report for the top level because there are no tests (or 
code for that matter). I have no idea why Maven generates the report anyway. 
The same is true for the dependencies page. We don't have a dependencies 
section in the parent pom. If we had one we might at least get an empty page.

> Minor issues with the 2.6.1 web site
> ------------------------------------
>
>                 Key: LOG4J2-1414
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1414
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 2.6.1
>            Reporter: Remko Popma
>            Priority: Minor
>
> 2.6
> (-) Project Information -> Dependencies, does not exist (I believe there's 
> already a bug report for this link)
> (-) Source Repository, git checkout info references a release candidate tag. 
> Will this be updated when an official release is tagged?
> (-) Surefire Report, does not exist
> (-) Manual page on 
> [Messages|http://logging.apache.org/log4j/2.x/manual/messages.html] is 
> missing the new ReusableXxxMessage types
> 2.6.1
> (/) [Changes Report|http://rgoers.github.io/log4j2-site/changes-report.html]  
> Release date is "Release 2.6.1 – 2016-MM-DD"
> (/) (Not an issue) Add German article on Log4j to the list: 
> https://jaxenter.de/apache-log4j-2-6-laeuft-nun-auch-ohne-muell-41098



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to