[jira] [Created] (MSITE-1006) MSITE-723 causes duplicate document rendering and log output

Michael Osipov created MSITE-1006: - Summary: MSITE-723 causes duplicate document rendering and log output Key: MSITE-1006 URL: https://issues.apache.org/jira/browse/MSITE-1006 Project: Maven Site

[jira] [Updated] (DOXIASITETOOLS-335) Upgrade to Doxia 2.0.0-M10

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-335: -- Fix Version/s: 2.0.0 > Upgrade to Doxia 2.0.0-M10 >

[jira] [Closed] (DOXIASITETOOLS-335) Upgrade to Doxia 2.0.0-M10

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-335. - Resolution: Fixed Fixed with

[jira] [Updated] (DOXIASITETOOLS-323) Upgrade components

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-323: -- Description: * Upgrade to Plexus Interpolation 1.27 * Upgrade to

[jira] [Updated] (DOXIASITETOOLS-321) Upgrade htmlunit 2.x to 4.0.0

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-321: -- Summary: Upgrade htmlunit 2.x to 4.0.0 (was: Upgrade htmlunit 2.x to

[jira] [Updated] (DOXIASITETOOLS-333) Upgrade commons-io:commons-io to 2.16.1

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-333: -- Summary: Upgrade commons-io:commons-io to 2.16.1 (was: Upgrade

[jira] [Created] (DOXIASITETOOLS-335) Upgrade to Doxia 2.0.0-M10

Michael Osipov created DOXIASITETOOLS-335: - Summary: Upgrade to Doxia 2.0.0-M10 Key: DOXIASITETOOLS-335 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-335 Project: Maven Doxia

[jira] [Updated] (MSHARED-1362) Upgrade plugins and components (in ITs)

[ https://issues.apache.org/jira/browse/MSHARED-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1362: Description: * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Doxia 2.0.0-M10 *

[jira] [Updated] (MSHARED-1361) Upgrade plugins and components (in ITs) (2)

[ https://issues.apache.org/jira/browse/MSHARED-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1361: Description: * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M19 *

[jira] [Closed] (MSHARED-1379) Upgrade to Doxia 2.0.0-M10

[ https://issues.apache.org/jira/browse/MSHARED-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1379. --- Resolution: Fixed Fixed with

[jira] [Updated] (MSHARED-1379) Upgrade to Doxia 2.0.0-M10

[ https://issues.apache.org/jira/browse/MSHARED-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1379: Fix Version/s: (was: maven-reporting-api-4.0.0-M10) > Upgrade to Doxia 2.0.0-M10 >

[jira] [Updated] (MSHARED-1379) Upgrade to Doxia 2.0.0-M10

[ https://issues.apache.org/jira/browse/MSHARED-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1379: Fix Version/s: maven-reporting-api-4.0.0-M11 > Upgrade to Doxia 2.0.0-M10 >

[jira] [Created] (MSHARED-1379) Upgrade to Doxia 2.0.0-M10

Michael Osipov created MSHARED-1379: --- Summary: Upgrade to Doxia 2.0.0-M10 Key: MSHARED-1379 URL: https://issues.apache.org/jira/browse/MSHARED-1379 Project: Maven Shared Components Issue

[jira] [Closed] (DOXIA-731) Simplify HTML emitted from Sink.verbatim(...)

[ https://issues.apache.org/jira/browse/DOXIA-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-731. > Simplify HTML emitted from Sink.verbatim(...) > - > >

[jira] [Closed] (DOXIA-728) MarkdownSink: Support blockquotes

[ https://issues.apache.org/jira/browse/DOXIA-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-728. > MarkdownSink: Support blockquotes > - > > Key:

[jira] [Closed] (DOXIA-734) XHTML 1.0 elements/attributes which are obsolete in XHTML5 no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-734. > XHTML 1.0 elements/attributes which are obsolete in XHTML5 no longer detected > by

[jira] [Closed] (DOXIA-724) Sink pipeline returned by AbstractParser.getWrappedSink(...) has wrong order

[ https://issues.apache.org/jira/browse/DOXIA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-724. > Sink pipeline returned by AbstractParser.getWrappedSink(...) has wrong order >

[jira] [Closed] (DOXIA-723) Optionally expose document location in Sink

[ https://issues.apache.org/jira/browse/DOXIA-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-723. > Optionally expose document location in Sink > --- > >

[jira] [Closed] (DOXIA-726) MarkdownSink: Incorrect escaping of <,>,",' and

[ https://issues.apache.org/jira/browse/DOXIA-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-726. > MarkdownSink: Incorrect escaping of <,>,",' and & > -

[jira] [Closed] (DOXIA-732) Do not fail for duplicate anchor names

[ https://issues.apache.org/jira/browse/DOXIA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-732. > Do not fail for duplicate anchor names > -- > >

[jira] [Closed] (DOXIA-727) MarkdownSink: Incorrect escaping inside code spans

[ https://issues.apache.org/jira/browse/DOXIA-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-727. > MarkdownSink: Incorrect escaping inside code spans >

[jira] [Commented] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work

[ https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836779#comment-17836779 ] Michael Osipov commented on MNG-8095: - This should have stayed open until the release notes are fixed.

[jira] [Commented] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work

[ https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836629#comment-17836629 ] Michael Osipov commented on MNG-8095: - I see now. I am certain that it is implemented differently than

[jira] [Commented] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work

[ https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836622#comment-17836622 ] Michael Osipov commented on MNG-8095: - ??? I am genuinly confused. Those exist with Maven 4 only. How

[jira] [Closed] (MPLUGIN-517) GoalRenderer renderParameterDetails() renders in wrong order

[ https://issues.apache.org/jira/browse/MPLUGIN-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPLUGIN-517. -- Resolution: Fixed Fixed with

[jira] [Commented] (MPLUGIN-517) GoalRenderer renderParameterDetails() renders in wrong order

[ https://issues.apache.org/jira/browse/MPLUGIN-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836435#comment-17836435 ] Michael Osipov commented on MPLUGIN-517: That one slipped through...will fix. > GoalRenderer

[jira] [Updated] (MPLUGIN-517) GoalRenderer renderParameterDetails() renders in wrong order

[ https://issues.apache.org/jira/browse/MPLUGIN-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPLUGIN-517: --- Fix Version/s: 3.12.1 > GoalRenderer renderParameterDetails() renders in wrong order >

[jira] [Assigned] (MPLUGIN-517) GoalRenderer renderParameterDetails() renders in wrong order

[ https://issues.apache.org/jira/browse/MPLUGIN-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPLUGIN-517: -- Assignee: Michael Osipov > GoalRenderer renderParameterDetails() renders in wrong

[jira] [Commented] (MNG-8041) Maven Core bug regarding resolution scopes for Mojos

[ https://issues.apache.org/jira/browse/MNG-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836195#comment-17836195 ] Michael Osipov commented on MNG-8041: - Is this worthy 3.8.9? > Maven Core bug regarding resolution

[jira] [Closed] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-939. -- Resolution: Fixed Fixed with

[jira] [Commented] (DOXIA-735) Upgrade commons-io:commons-io to 2.16.1

[ https://issues.apache.org/jira/browse/DOXIA-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836042#comment-17836042 ] Michael Osipov commented on DOXIA-735: -- https://github.com/apache/maven-doxia/pull/207 > Upgrade

[jira] [Updated] (DOXIA-735) Upgrade commons-io:commons-io to 2.16.1

[ https://issues.apache.org/jira/browse/DOXIA-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIA-735: - Summary: Upgrade commons-io:commons-io to 2.16.1 (was: Upgrade commons-io:commons-io to 2.16.0)

[jira] [Commented] (MPOM-480) Remove maven-site-plugin:attach-descriptor from ASF parent

[ https://issues.apache.org/jira/browse/MPOM-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836012#comment-17836012 ] Michael Osipov commented on MPOM-480: - Great, the change sounds totally reasonable.  > Remove

[jira] [Commented] (MPOM-480) Remove maven-site-plugin:attach-descriptor from ASF parent

[ https://issues.apache.org/jira/browse/MPOM-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835849#comment-17835849 ] Michael Osipov commented on MPOM-480: - So better understand this: only POM projects do attach that and

[jira] [Assigned] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SCM-939: -- Assignee: Michael Osipov > Assume SCM is present > - > >

[jira] [Updated] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-939: --- Fix Version/s: 2.1.0 > Assume SCM is present > - > > Key: SCM-939 >

[jira] [Closed] (SCM-1022) jgit push failure is not failing the build

[ https://issues.apache.org/jira/browse/SCM-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-1022. --- Resolution: Fixed Fixed with

[jira] [Closed] (SCM-1024) maven-scm-plugin tests do not properly check for existence of svn command

[ https://issues.apache.org/jira/browse/SCM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-1024. --- Resolution: Fixed Fixed with

[jira] [Updated] (SCM-1024) maven-scm-plugin tests do not properly check for existence of svn command

[ https://issues.apache.org/jira/browse/SCM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-1024: Summary: maven-scm-plugin tests do not properly check for existence of svn command (was:

[jira] [Created] (SCM-1024) maven-scm-plugin tests do not properly check for existance of svn command

Michael Osipov created SCM-1024: --- Summary: maven-scm-plugin tests do not properly check for existance of svn command Key: SCM-1024 URL: https://issues.apache.org/jira/browse/SCM-1024 Project: Maven SCM

[jira] [Closed] (SCM-1023) Upgrade components

[ https://issues.apache.org/jira/browse/SCM-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SCM-1023. --- Resolution: Fixed Fixed with

[jira] [Created] (SCM-1023) Upgrade components

Michael Osipov created SCM-1023: --- Summary: Upgrade components Key: SCM-1023 URL: https://issues.apache.org/jira/browse/SCM-1023 Project: Maven SCM Issue Type: Dependency upgrade

[jira] [Updated] (MPMD-379) Upgrade to use PMD 7.0.0 by default

[ https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPMD-379: Fix Version/s: next-release > Upgrade to use PMD 7.0.0 by default >

[jira] [Updated] (SCM-1022) jgit push failure is not failing the build

[ https://issues.apache.org/jira/browse/SCM-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-1022: Fix Version/s: 2.1.0 > jgit push failure is not failing the build >

[jira] [Assigned] (SCM-1022) jgit push failure is not failing the build

[ https://issues.apache.org/jira/browse/SCM-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SCM-1022: --- Assignee: Michael Osipov > jgit push failure is not failing the build >

[jira] [Commented] (MARTIFACT-60) artifact:3.5.0:check-buildplan is too chatty by default

[ https://issues.apache.org/jira/browse/MARTIFACT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833558#comment-17833558 ] Michael Osipov commented on MARTIFACT-60: - Makes sense. [~hboutemy], WDYT? >

[jira] [Commented] (SCM-1022) jgit push failure is not failing the build

[ https://issues.apache.org/jira/browse/SCM-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833557#comment-17833557 ] Michael Osipov commented on SCM-1022: - A PR would be appreciated, best with a test proving it. > jgit

[jira] [Updated] (DOXIASITETOOLS-334) Pass project relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-334: -- Fix Version/s: 2.0.0 > Pass project relative source path to

[jira] [Commented] (DOXIASITETOOLS-334) Pass project relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833276#comment-17833276 ] Michael Osipov commented on DOXIASITETOOLS-334: --- It is logically identical. If you

[jira] [Commented] (DOXIASITETOOLS-334) Pass basedir relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833265#comment-17833265 ] Michael Osipov commented on DOXIASITETOOLS-334: --- Makes sense, but that change would

[jira] [Commented] (DOXIASITETOOLS-334) Pass basedir relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833261#comment-17833261 ] Michael Osipov commented on DOXIASITETOOLS-334: --- Why? Please explain. > Pass

[jira] [Commented] (DOXIASITETOOLS-334) Pass basedir relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833259#comment-17833259 ] Michael Osipov commented on DOXIASITETOOLS-334: --- For locale {{de_DE}} two files:

[jira] [Comment Edited] (DOXIASITETOOLS-334) Pass relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833255#comment-17833255 ] Michael Osipov edited comment on DOXIASITETOOLS-334 at 4/2/24 4:35 PM:

[jira] [Commented] (DOXIASITETOOLS-334) Pass relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833255#comment-17833255 ] Michael Osipov commented on DOXIASITETOOLS-334: --- No, I have added {{foo/index.apt}}

[jira] [Comment Edited] (DOXIASITETOOLS-334) Pass relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833170#comment-17833170 ] Michael Osipov edited comment on DOXIASITETOOLS-334 at 4/2/24 3:08 PM:

[jira] [Commented] (DOXIASITETOOLS-334) Pass relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833170#comment-17833170 ] Michael Osipov commented on DOXIASITETOOLS-334: --- I have applied the following

[jira] [Commented] (MGPG-121) Signing fails with 3.2.2: "/Users/stevenobelia/.settings-security.xml (No such file or directory)"

[ https://issues.apache.org/jira/browse/MGPG-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833132#comment-17833132 ] Michael Osipov commented on MGPG-121: - [~cstamas], how I hate this pseudo security... > Signing fails

[jira] [Comment Edited] (DOXIASITETOOLS-334) Pass relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833092#comment-17833092 ] Michael Osipov edited comment on DOXIASITETOOLS-334 at 4/2/24 10:19 AM:

[jira] [Commented] (DOXIASITETOOLS-334) Pass relative source path to Parser.parse(...) as reference argument

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833092#comment-17833092 ] Michael Osipov commented on DOXIASITETOOLS-334: --- Are you certain? I am confused. I

[jira] [Closed] (MNG-8086) Maven no longer initializes logging configuration based on java.util.logging config file

[ https://issues.apache.org/jira/browse/MNG-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-8086. --- Resolution: Information Provided > Maven no longer initializes logging configuration based on

[jira] [Commented] (MJAR-300) maven jar plugin does not interpret build outputTimestamp correctly

[ https://issues.apache.org/jira/browse/MJAR-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832287#comment-17832287 ] Michael Osipov commented on MJAR-300: - Can we close this issue? > maven jar plugin does not interpret

[jira] [Commented] (MRELEASE-1138) Regression: @{releaseLabel} variable is not resolved in the commit message of the branch goal

[ https://issues.apache.org/jira/browse/MRELEASE-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831932#comment-17831932 ] Michael Osipov commented on MRELEASE-1138: -- Please try to find the first broken version, then

[jira] [Comment Edited] (MNG-8086) Maven no longer initializes logging configuration based on java.util.logging config file

[ https://issues.apache.org/jira/browse/MNG-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831926#comment-17831926 ] Michael Osipov edited comment on MNG-8086 at 3/28/24 6:40 PM: -- The command you

[jira] [Commented] (MNG-8086) Maven no longer initializes logging configuration based on java.util.logging config file

[ https://issues.apache.org/jira/browse/MNG-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831926#comment-17831926 ] Michael Osipov commented on MNG-8086: - The command you are calling is what I have expected -- wrong.

[jira] [Closed] (MNG-8087) `user.home` system property is not propagated

[ https://issues.apache.org/jira/browse/MNG-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-8087. --- Resolution: Information Provided > `user.home` system property is not propagated >

[jira] [Commented] (MNG-8086) Maven no longer initializes logging configuration based on java.util.logging config file

[ https://issues.apache.org/jira/browse/MNG-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831755#comment-17831755 ] Michael Osipov commented on MNG-8086: - You haven't provided the full command how you launch which leads

[jira] [Commented] (MNG-8086) Maven no longer initializes logging configuration based on java.util.logging config file

[ https://issues.apache.org/jira/browse/MNG-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831558#comment-17831558 ] Michael Osipov commented on MNG-8086: - I don't consider this as a bug, but you are relying on undefined

[jira] [Commented] (MSITE-1000) Allow parametrisation of Doxia parser per file

[ https://issues.apache.org/jira/browse/MSITE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828485#comment-17828485 ] Michael Osipov commented on MSITE-1000: --- Good idea, similar to the Maven Release Plugin. > Allow

[jira] [Updated] (DOXIA-734) XHTML 1.0 elements/attributes which are obsolete in XHTML5 no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIA-734: - Summary: XHTML 1.0 elements/attributes which are obsolete in XHTML5 no longer detected by

[jira] [Commented] (MSHARED-1364) AbstractMavenReportRenderer should not depend on Doxia impl classes

[ https://issues.apache.org/jira/browse/MSHARED-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827736#comment-17827736 ] Michael Osipov commented on MSHARED-1364: - I see and then extend from to retain binary compat?

[jira] [Commented] (MPLUGIN-501) Upgrade to Doxia 2.0.0 Milestone Stack

[ https://issues.apache.org/jira/browse/MPLUGIN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827693#comment-17827693 ] Michael Osipov commented on MPLUGIN-501: The how is this related to this issue? I don't

[jira] [Commented] (MSHARED-1364) AbstractMavenReportRenderer should not depend on Doxia impl classes

[ https://issues.apache.org/jira/browse/MSHARED-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827671#comment-17827671 ] Michael Osipov commented on MSHARED-1364: - What do you recommend to do in such a case? Where

[jira] [Commented] (MPLUGIN-501) Upgrade to Doxia 2.0.0 Milestone Stack

[ https://issues.apache.org/jira/browse/MPLUGIN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827669#comment-17827669 ] Michael Osipov commented on MPLUGIN-501: Already done some time ago:

[jira] [Commented] (DOXIA-734) XHTML 1 elements/attributes which are obsolete in XHTML5 no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827668#comment-17827668 ] Michael Osipov commented on DOXIA-734: -- I don't see a reason to drop FML although I thought about it

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827103#comment-17827103 ] Michael Osipov commented on DOXIA-734: -- That is true. How much effort do you see to provide the

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827047#comment-17827047 ] Michael Osipov commented on DOXIA-734: -- Even if we have a lot, it does not mean that they are void.

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826999#comment-17826999 ] Michael Osipov commented on DOXIA-734: -- I see, is it really worth the effort? I don't think so.

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826987#comment-17826987 ] Michael Osipov commented on DOXIA-734: -- [~hboutemy], I do remember that you told me that there is no

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826985#comment-17826985 ] Michael Osipov commented on DOXIA-734: -- [~hboutemy], are you OK with uplifting XDoc content to XHML5

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826878#comment-17826878 ] Michael Osipov commented on DOXIA-734: -- Right and nothing stops us to bump major version on them. We

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826876#comment-17826876 ] Michael Osipov commented on DOXIA-734: -- I'd like to know [~hboutemy]'s opinion. Both formats don't

[jira] [Comment Edited] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826865#comment-17826865 ] Michael Osipov edited comment on DOXIA-734 at 3/13/24 8:57 PM: --- Apt? How?

[jira] [Commented] (DOXIA-734) anchor element with "name" attribute no longer detected by XdocParser/FmlParser

[ https://issues.apache.org/jira/browse/DOXIA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826865#comment-17826865 ] Michael Osipov commented on DOXIA-734: -- Apt? How? As for FML/XDoc: I do understand your concern, but

[jira] [Commented] (DOXIA-731) Simplify HTML emitted from Sink.verbatim(...)

[ https://issues.apache.org/jira/browse/DOXIA-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825368#comment-17825368 ] Michael Osipov commented on DOXIA-731: -- Please note that this needs to reversible, means a parser

[jira] [Updated] (MNG-8073) Generated XSD files needs to have AL2.0 license headers

[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-8073: Summary: Generated XSD files needs to have AL2.0 license headers (was: Generated XSD files needs to

[jira] [Commented] (MSKINS-244) Get rid of CSS classes "table" and "verbatim"

[ https://issues.apache.org/jira/browse/MSKINS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825356#comment-17825356 ] Michael Osipov commented on MSKINS-244: --- This task should be split into two. > Get rid of CSS

[jira] [Comment Edited] (MSITE-1002) Maven Site 4 will break code highlight of site generated by Markdown

[ https://issues.apache.org/jira/browse/MSITE-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825216#comment-17825216 ] Michael Osipov edited comment on MSITE-1002 at 3/11/24 9:06 AM: Let's

[jira] [Commented] (MSITE-1002) Maven Site 4 will break code highlight of site generated by Markdown

[ https://issues.apache.org/jira/browse/MSITE-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825216#comment-17825216 ] Michael Osipov commented on MSITE-1002: --- Let's slow down here a bit and analyze what is first

[jira] [Commented] (MSITE-1002) Maven Site 4 will break code highlight of site generated by Markdown

[ https://issues.apache.org/jira/browse/MSITE-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824986#comment-17824986 ] Michael Osipov commented on MSITE-1002: --- [~kwin], ping. > Maven Site 4 will break code highlight

[jira] [Created] (MSITE-1003) Upgrade plugins and components (in ITs)

Michael Osipov created MSITE-1003: - Summary: Upgrade plugins and components (in ITs) Key: MSITE-1003 URL: https://issues.apache.org/jira/browse/MSITE-1003 Project: Maven Site Plugin Issue

[jira] [Created] (MSHARED-1362) Upgrade plugins and components (in ITs)

Michael Osipov created MSHARED-1362: --- Summary: Upgrade plugins and components (in ITs) Key: MSHARED-1362 URL: https://issues.apache.org/jira/browse/MSHARED-1362 Project: Maven Shared Components

[jira] [Created] (MSHARED-1361) Upgrade plugins and components (in ITs) (2)

Michael Osipov created MSHARED-1361: --- Summary: Upgrade plugins and components (in ITs) (2) Key: MSHARED-1361 URL: https://issues.apache.org/jira/browse/MSHARED-1361 Project: Maven Shared Components

[jira] [Closed] (DOXIASITETOOLS-322) Upgrade to Doxia 2.0.0-M9

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-322. - > Upgrade to Doxia 2.0.0-M9 > - > >

[jira] [Updated] (DOXIASITETOOLS-324) Allow configuration of parser per markup

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-324: -- Fix Version/s: (was: 2.0.0-M17) > Allow configuration of parser

[jira] [Closed] (DOXIASITETOOLS-332) Create anchors for indexable entries automatically

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-332. - Resolution: Fixed Fixed with

[jira] [Updated] (MCOMPILER-581) Create second default execution "default-generate-sources" for APT

[ https://issues.apache.org/jira/browse/MCOMPILER-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MCOMPILER-581: - Summary: Create second default execution "default-generate-sources" for APT (was:

[jira] [Created] (DOXIASITETOOLS-332) Create anchors for indexable entries automatically

Michael Osipov created DOXIASITETOOLS-332: - Summary: Create anchors for indexable entries automatically Key: DOXIASITETOOLS-332 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-332

[jira] [Closed] (DOXIA-725) Latest Doxia Core is not compatible with doxia-sitetools

[ https://issues.apache.org/jira/browse/DOXIA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-725. Fix Version/s: (was: waiting-for-feedback) Resolution: Information Provided > Latest

[jira] [Closed] (DOXIASITETOOLS-331) Upgrade to htmlunit 3.11.0

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-331. - Resolution: Fixed Fixed with

[jira] [Created] (DOXIASITETOOLS-331) Upgrade to htmlunit 3.11.0

Michael Osipov created DOXIASITETOOLS-331: - Summary: Upgrade to htmlunit 3.11.0 Key: DOXIASITETOOLS-331 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-331 Project: Maven Doxia

<    1   2   3   4   5   6   7   8   9   10   >