[
https://issues.apache.org/jira/browse/LOG4J2-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856220#comment-15856220
]
Matt Sicker commented on LOG4J2-1691:
-------------------------------------
The final step is the site integration. I'm not exactly sure which would be the
best way to do so, but here are some ideas on how:
* Make the Log4j Scala API site its own subdirectory like Log4j Boot will be
and just include prominent links on the main Log4j site (and the Logging
Services site). I kind of prefer this option because it's easier to implement
for both this site as well as the other Log4j subprojects we're working on.
* Try to fake site integration between Log4j 2 and Log4j Scala API by copying
the generated sites from Log4j Scala API into the appropriate subdirectories in
the Log4j 2 site in svn, though this will require far more manual maintenance.
I feel as though if we went this route, we'd eventually want to switch to the
first idea anyways.
> Setup build process for new Git repo logging-log4j-scala, including site
> ------------------------------------------------------------------------
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira/browse/LOG4J2-1691
> Project: Log4j 2
> Issue Type: Task
> Reporter: Mikael Ståldal
> Assignee: Matt Sicker
>
> We need to setup the build process for new Git repo logging-log4j-scala,
> including site and Jenkins build.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
