[jira] [Commented] (MNG-6661) Override project.build.directory via user property

[ https://issues.apache.org/jira/browse/MNG-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849396#comment-16849396 ] Sergey Ponomarev commented on MNG-6661: --- ok, then maybe we can introduce some another

[jira] [Commented] (MJAVADOC-606) doclint fails checking references on dependencies with scope 'provided'

[ https://issues.apache.org/jira/browse/MJAVADOC-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849404#comment-16849404 ] Aurélien Baudet commented on MJAVADOC-606: -- Finally, I found the solution so I

[GitHub] [maven-jdeps-plugin] NennoA opened a new pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line

NennoA opened a new pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line URL: https://github.com/apache/maven-jdeps-plugin/pull/3 This is an automat

[jira] [Comment Edited] (MJDEPS-23) The parameter multiRelease should have a user property so that you can set it from the command line

[ https://issues.apache.org/jira/browse/MJDEPS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849492#comment-16849492 ] Nenni Andrea edited comment on MJDEPS-23 at 5/28/19 8:56 AM: -

[jira] [Commented] (MJDEPS-23) The parameter multiRelease should have a user property so that you can set it from the command line

[ https://issues.apache.org/jira/browse/MJDEPS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849492#comment-16849492 ] Nenni Andrea commented on MJDEPS-23: i propose a fix linked above. > The parameter mu

[jira] [Created] (MNG-6662) More concise logging

Vasiliy Kudriavtsev created MNG-6662: Summary: More concise logging Key: MNG-6662 URL: https://issues.apache.org/jira/browse/MNG-6662 Project: Maven Issue Type: Improvement Comp

[jira] [Updated] (MNG-6662) More concise logging

[ https://issues.apache.org/jira/browse/MNG-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Kudriavtsev updated MNG-6662: - Description: Maven supports configurable logging, but sometimes even more flexibility is r

[jira] [Updated] (MNG-6662) More concise logging

[ https://issues.apache.org/jira/browse/MNG-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Kudriavtsev updated MNG-6662: - Description: Maven supports configurable logging, but sometimes even more flexibility is r

[GitHub] [maven-jdeps-plugin] eolivelli closed pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line

eolivelli closed pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line URL: https://github.com/apache/maven-jdeps-plugin/pull/3 This is an automated

[GitHub] [maven-jdeps-plugin] eolivelli commented on issue #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line

eolivelli commented on issue #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line URL: https://github.com/apache/maven-jdeps-plugin/pull/3#issuecomment-496463768 Le'ts wait for CI https://builds.apache.org/job/maven-box/job/m

[GitHub] [maven-jdeps-plugin] NennoA opened a new pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line

NennoA opened a new pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line URL: https://github.com/apache/maven-jdeps-plugin/pull/3 Mapping parameter multielease to property jdeps.multiRelease ---

[jira] [Commented] (MNG-6573) Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI

[ https://issues.apache.org/jira/browse/MNG-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849592#comment-16849592 ] Hudson commented on MNG-6573: - Build succeeded in Jenkins: Maven TLP » maven-jdeps-plugin » mas

[jira] [Commented] (MNG-6662) More concise logging

[ https://issues.apache.org/jira/browse/MNG-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849595#comment-16849595 ] Michael Osipov commented on MNG-6662: - Maybe we should work with SLF4J markers which ar

[GitHub] [maven-jdeps-plugin] eolivelli closed pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line

eolivelli closed pull request #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line URL: https://github.com/apache/maven-jdeps-plugin/pull/3 This is an automated

[GitHub] [maven-jdeps-plugin] eolivelli commented on issue #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line

eolivelli commented on issue #3: [MJDEPS-23] The parameter multiRelease should have a user property so that you can set it from the command line URL: https://github.com/apache/maven-jdeps-plugin/pull/3#issuecomment-496475603 Merged to master thank you @NennoA ! -

[jira] [Commented] (MJDEPS-23) The parameter multiRelease should have a user property so that you can set it from the command line

[ https://issues.apache.org/jira/browse/MJDEPS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849619#comment-16849619 ] Hudson commented on MJDEPS-23: -- Build succeeded in Jenkins: Maven TLP » maven-jdeps-plugin »

[jira] [Assigned] (MJDEPS-23) The parameter multiRelease should have a user property so that you can set it from the command line

[ https://issues.apache.org/jira/browse/MJDEPS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli reassigned MJDEPS-23: - Assignee: Enrico Olivelli > The parameter multiRelease should have a user property so tha

[jira] [Resolved] (MJDEPS-23) The parameter multiRelease should have a user property so that you can set it from the command line

[ https://issues.apache.org/jira/browse/MJDEPS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli resolved MJDEPS-23. --- Resolution: Fixed committed to master branch, thank you [~nenno] > The parameter multiRelease

[jira] [Commented] (DOXIASITETOOLS-190) Generate (X)HTML5 by default

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849658#comment-16849658 ] Graham Leggett commented on DOXIASITETOOLS-190: --- Quick ping on this

[jira] [Commented] (MNG-6662) More concise logging

[ https://issues.apache.org/jira/browse/MNG-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849686#comment-16849686 ] Vasiliy Kudriavtsev commented on MNG-6662: -- [~michael-o], it would be nice, but Si

[jira] [Commented] (MNG-6649) Duplicate class error in maven-compiler-plugin

[ https://issues.apache.org/jira/browse/MNG-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849690#comment-16849690 ] Matthias Geerdsen commented on MNG-6649: Actually we are experiencing something sim

[GitHub] [maven] mickaelistria opened a new pull request #250: Always deploy snapshot from master

mickaelistria opened a new pull request #250: Always deploy snapshot from master URL: https://github.com/apache/maven/pull/250 Signed-off-by: Mickael Istria This is an automated message from the Apache Git Service. To res

[jira] [Commented] (DOXIA-575) Add support for (X)HTML5

[ https://issues.apache.org/jira/browse/DOXIA-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849704#comment-16849704 ] Graham Leggett commented on DOXIA-575: -- Quick ping, had a chance to take a look at h

[jira] [Updated] (MNG-6663) overriding parent dependency management doesn't work for transitive dependencies

[ https://issues.apache.org/jira/browse/MNG-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alireza Ghassemi updated MNG-6663: -- Description: overriding the dependencies of a parent POM is possible by setting the dependency v

[jira] [Created] (MNG-6663) overriding parent dependency management doesn't work for transitive dependencies

Alireza Ghassemi created MNG-6663: - Summary: overriding parent dependency management doesn't work for transitive dependencies Key: MNG-6663 URL: https://issues.apache.org/jira/browse/MNG-6663 Project:

[jira] [Commented] (MNG-6662) More concise logging

[ https://issues.apache.org/jira/browse/MNG-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849763#comment-16849763 ] Michael Osipov commented on MNG-6662: - That's true, but your you could swap for logback

[jira] [Commented] (DOXIA-575) Add support for (X)HTML5

[ https://issues.apache.org/jira/browse/DOXIA-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849766#comment-16849766 ] Michael Osipov commented on DOXIA-575: -- Apologies, got out of sight. Looking into. >

[GitHub] [maven-doxia-sitetools] michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288132161 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterender

[GitHub] [maven-doxia-sitetools] michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288132557 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterender

[GitHub] [maven-doxia-sitetools] michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288135567 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterender

[GitHub] [maven-doxia-sitetools] michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288134222 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterender

[GitHub] [maven-doxia-sitetools] michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288136255 ## File path: pom.xml ## @@ -69,7 +69,7 @@ under the License.

[GitHub] [maven-doxia-sitetools] michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288134481 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterender

[GitHub] [maven-doxia-sitetools] michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

michael-o commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288134341 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterender

[jira] [Assigned] (DOXIA-591) Require minimum Java 7 at runtime

[ https://issues.apache.org/jira/browse/DOXIA-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned DOXIA-591: Assignee: Sylwester Lachiewicz > Require minimum Java 7 at runtime > --

[jira] [Updated] (DOXIA-573) Upgrade mave-surefire/failsafe-plugin 2.21.0

[ https://issues.apache.org/jira/browse/DOXIA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIA-573: - Fix Version/s: (was: 1.9) > Upgrade mave-surefire/failsafe-plugin 2.21.0 > ---

[jira] [Updated] (DOXIA-540) Update/remove ancient information on Doxia site

[ https://issues.apache.org/jira/browse/DOXIA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIA-540: - Fix Version/s: (was: 1.9) > Update/remove ancient information on Doxia site >

[jira] [Updated] (DOXIA-580) Numbered list items are always at level 1 in ConfluenceSink

[ https://issues.apache.org/jira/browse/DOXIA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIA-580: - Fix Version/s: (was: 1.9) > Numbered list items are always at level 1 in ConfluenceSink >

[jira] [Commented] (DOXIA-580) Numbered list items are always at level 1 in ConfluenceSink

[ https://issues.apache.org/jira/browse/DOXIA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849785#comment-16849785 ] Michael Osipov commented on DOXIA-580: -- I have removed the fix version for now since

[jira] [Commented] (DOXIA-538) Tag used for monospaced is not a valid html5 tag

[ https://issues.apache.org/jira/browse/DOXIA-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849787#comment-16849787 ] Michael Osipov commented on DOXIA-538: -- [~minfrin], isn't this implicitly fixed by yo

[jira] [Commented] (DOXIA-568) Doxia Markdown extension > Support for some MarkDown extensions has been removed since 1.7

[ https://issues.apache.org/jira/browse/DOXIA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849790#comment-16849790 ] Michael Osipov commented on DOXIA-568: -- Has this been implicitly fixed with the flexm

[jira] [Commented] (DOXIA-528) Enable rendering of HTML5 data- attributes

[ https://issues.apache.org/jira/browse/DOXIA-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849792#comment-16849792 ] Michael Osipov commented on DOXIA-528: -- [~minfrin], is this covered by your work? >

[jira] [Commented] (DOXIA-583) XhtmlBaseSink : Table caption is escaped incorrectly

[ https://issues.apache.org/jira/browse/DOXIA-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849806#comment-16849806 ] Michael Osipov commented on DOXIA-583: -- Please do a GitHub PR, I will take a look for

[jira] [Commented] (DOXIA-574) XHTML: div tags filtered in the output

[ https://issues.apache.org/jira/browse/DOXIA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849815#comment-16849815 ] Michael Osipov commented on DOXIA-574: -- Indeed, it is eaten for some reason. Probably

[jira] [Commented] (DOXIA-588) The Sink.JUSTIFY_XXX has no effect

[ https://issues.apache.org/jira/browse/DOXIA-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849817#comment-16849817 ] Michael Osipov commented on DOXIA-588: -- Can you provide an example that this isn't wo

[jira] [Updated] (MANTRUN-207) scriptdef ignores CDATA when there is also an element

[ https://issues.apache.org/jira/browse/MANTRUN-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MANTRUN-207: - Fix Version/s: waiting-for-feedback > scriptdef ignores CDATA when there is also

[jira] [Commented] (MANTRUN-207) scriptdef ignores CDATA when there is also an element

[ https://issues.apache.org/jira/browse/MANTRUN-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849833#comment-16849833 ] Sylwester Lachiewicz commented on MANTRUN-207: -- Now code looks litle differ

[jira] [Updated] (MANTRUN-206) Plugin fails with conditional property containing a Windows path.

[ https://issues.apache.org/jira/browse/MANTRUN-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MANTRUN-206: - Fix Version/s: more-investigation > Plugin fails with conditional property conta

[jira] [Commented] (DOXIA-583) XhtmlBaseSink : Table caption is escaped incorrectly

[ https://issues.apache.org/jira/browse/DOXIA-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849837#comment-16849837 ] Iwao AVE! commented on DOXIA-583: - That would be great, thanks! Here is the PR : https://g

[jira] [Commented] (MNG-6610) pomless builds fail on jenkins with windows agents

[ https://issues.apache.org/jira/browse/MNG-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849863#comment-16849863 ] Benjamin commented on MNG-6610: --- Subdirectory: We have a internal project, where the pom is l

[jira] [Commented] (MSITE-837) use an embedded http server that is light and requires just Java 7

[ https://issues.apache.org/jira/browse/MSITE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849876#comment-16849876 ] Damien Burke commented on MSITE-837: [~hboutemy] I only did a quick bit of research on

[jira] [Updated] (DOXIA-583) XhtmlBaseSink : Table caption is escaped incorrectly

[ https://issues.apache.org/jira/browse/DOXIA-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-583: --- Fix Version/s: 1.9 > XhtmlBaseSink : Table caption is escaped incorrectly > --

[jira] [Updated] (MSHARED-821) Retire Maven Runtime

[ https://issues.apache.org/jira/browse/MSHARED-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSHARED-821: --- Component/s: maven-runtime (RETIRED) > Retire Maven Runtime > > >

[jira] [Updated] (MSHARED-821) Retire Maven Runtime

[ https://issues.apache.org/jira/browse/MSHARED-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSHARED-821: --- Description: There's been [a vote|https://lists.apache.org/thread.html/4a399fef3e75ae2bb777

[jira] [Updated] (MSHARED-821) Retire Maven Runtime

[ https://issues.apache.org/jira/browse/MSHARED-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSHARED-821: --- Description: There's been [a vote|https://lists.apache.org/thread.html/4a399fef3e75ae2bb777

[jira] [Updated] (MSHARED-821) Retire Maven Runtime

[ https://issues.apache.org/jira/browse/MSHARED-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSHARED-821: --- Description: There's been [a vote|https://lists.apache.org/thread.html/4a399fef3e75ae2bb777

[GitHub] [maven-pmd-plugin] edouard-gv opened a new pull request #12: [MPMD-269] - Display PMD version that is being used

edouard-gv opened a new pull request #12: [MPMD-269] - Display PMD version that is being used URL: https://github.com/apache/maven-pmd-plugin/pull/12 only for checks, for reports already done Following this checklist to help us incorporate your contribution quickly and easily:

[jira] [Commented] (MPMD-269) Display PMD version that is being used

[ https://issues.apache.org/jira/browse/MPMD-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850109#comment-16850109 ] Édouard Gomez-Vaëz commented on MPMD-269: - Pull request #12 > Display PMD version

[GitHub] [maven-doxia-sitetools] minfrin commented on issue #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on issue #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#issuecomment-496725879 I'm scratching my head - I tried to rebuild this to test out an htmlunit upgrade, but the maven-doxia v1.9-SN

[GitHub] [maven-doxia-sitetools] minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288341343 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterenderer

[GitHub] [maven-doxia-sitetools] minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288342288 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterenderer

[GitHub] [maven-doxia-sitetools] minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288342337 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterenderer

[GitHub] [maven-doxia-sitetools] minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288343567 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterenderer

[GitHub] [maven-doxia-sitetools] minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288343608 ## File path: pom.xml ## @@ -69,7 +69,7 @@ under the License. -

[GitHub] [maven-doxia-sitetools] minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288348557 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterenderer

[GitHub] [maven-doxia-sitetools] minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on a change in pull request #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#discussion_r288348557 ## File path: doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterenderer

[GitHub] [maven-doxia-sitetools] minfrin commented on issue #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer.

minfrin commented on issue #5: Switch from XhtmlSink to Xhtml5Sink as the default site renderer. URL: https://github.com/apache/maven-doxia-sitetools/pull/5#issuecomment-496734851 > There are a few issues need to be discussed. Especially other skins, did you try at least the fluido skin w

[GitHub] [maven] olamy merged pull request #250: Always deploy snapshot from master

olamy merged pull request #250: Always deploy snapshot from master URL: https://github.com/apache/maven/pull/250 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and