[jira] [Closed] (MSITE-1008) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/MSITE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-1008. - Resolution: Fixed Fixed with [deee90af4e539095cfc6f3208db3df1fa9395ed8|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=deee90af4e539095cfc6f3208db3df1fa9395ed8]. > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: MSITE-1008 > URL: https://issues.apache.org/jira/browse/MSITE-1008 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-M15 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSITE-1008) Upgrade to Parent 42 and Maven 3.6.3
Michael Osipov created MSITE-1008: - Summary: Upgrade to Parent 42 and Maven 3.6.3 Key: MSITE-1008 URL: https://issues.apache.org/jira/browse/MSITE-1008 Project: Maven Site Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 4.0.0-M15, 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSITE-1007) Review "Configuring the Site Descriptor" for new site model and behavior
Michael Osipov created MSITE-1007: - Summary: Review "Configuring the Site Descriptor" for new site model and behavior Key: MSITE-1007 URL: https://issues.apache.org/jira/browse/MSITE-1007 Project: Maven Site Plugin Issue Type: Task Components: documentation Affects Versions: 4.0.0-M14 Reporter: Michael Osipov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINVOKER-351) Prevent XML-prohibited characters from entering JUnit report
[
https://issues.apache.org/jira/browse/MINVOKER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847509#comment-17847509
]
Michael Osipov commented on MINVOKER-351:
-
The behavior is inconsitent because plugins are a moving target. One must pin
all relevant plugins otherwise the behavior will vary.
> Prevent XML-prohibited characters from entering JUnit report
>
>
> Key: MINVOKER-351
> URL: https://issues.apache.org/jira/browse/MINVOKER-351
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Reporter: Mikkel Kjeldsen
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.0
>
> Attachments: minvoker-351.tar.gz
>
>
> Neither the Maven Invoker plugin's implementation of {{}}
> nor the underlying XML infrastructure directly protect against the presence
> of character literals prohibited by the XML specification, meaning such
> literals can appear in the JUnit report and render it unreadable. *I would
> appreciate if the Maven Invoker plugin could learn to strip prohibited
> literals to protect its users from creative plugins.* I argue that this is a
> safe and expected transformation that is not materially lossy.
>
> h2. Background
> MINVOKER-196 added the {{}} option [back in
> maven-invoker-plugin-3.2.1|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.2.1/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1878-L1946].
> As of [maven-invoker-plugin-3.6.0 the effective implementation of the JUnit
> report remains effectively
> unchanged|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.6.0/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1695-L1754].
> The JUnit report includes a {{}} element ([example
> documentation|https://github.com/testmoapp/junitxml]) whose value Maven
> Invoker populates with the raw build log contents. I've observed that this
> value is XML-escaped, which I imagine is well understood in the
> implementation, although I can't immediately find documentation to support
> that.
> However, escaping notwithstanding, a number of character literals are
> outright prohibited by the XML specifications. These literals cannot be
> escaped, and their presence renders an XML document not well formed. The
> exact set of prohibited characters varies by XML version; the report produced
> by the Maven Invoker plugin is XML version 1.0. When the Maven Invoker plugin
> reads in the build log it does not strip these character literals and neither
> does the XML writer the Maven Invoker plugin relies on. Consequently, if a
> build log ends up including a prohibited character the resulting JUnit report
> will not be well formed.
> The set of prohibited characters is the complement of [the XML
> specification's definition of {{Char}}|https://www.w3.org/TR/xml/#NT-Char].
> h2. Example
> Among the literals prohibited by XML version 1.0 is {{^H}} (backspace). When
> [pitest runs via Maven|https://pitest.org/quickstart/maven/] it prints a
> spinner to standard out, and the implementation uses backspace to render the
> spinner in place. I have used the Maven Invoker plugin with
> {{}} to verify a pitest configuration, whereby I discovered
> this limitation.
> h2. Remediation
> h3. Blame plugins
> Perhaps pitest should not behave this way but we can't change pitest, and
> even if pitest could be changed that offers no protection against any other
> plugin, so blaming plugins is an ineffective course of action.
> h3. Work-arounds
> The user can manually clean the build log in-place via
> {{}}. This is technically fairly easy to do, and makes
> the transformation very explicit, but it requires considerable local work to
> address an issue many would find obscure and the transformation is
> permanently lossy unless the user also backs up the raw log to another file
> name.
> h3. Strip prohibited literals inside Maven Invoker plugin
> If the Maven Invoker plugin learns to strip offending character literals
> in-between reading the build log and writing to the {{}} value
> then {{}} will Just Work™, which I assert is what a user
> will typically expect. Although the {{}} value will no longer
> exactly match the build log contents, this lossy translation is acceptable:
> the prohibited characters are overwhelmingly unprintable to begin with and
> therefore cannot be meaningfully rendered in a static context, and the raw
> build log remains unchanged in the event that the user needs to investigate
> or assert against the raw output.
> This change would be backwards compatible, because any existing user that
> would be affected by it would already have unparseable JUnit reports.
> * I _believe_ that Java's {{j.u.r.Pattern}}
[jira] [Created] (DOXIASITETOOLS-341) Upgrade plugins and components (in ITs)
Michael Osipov created DOXIASITETOOLS-341: - Summary: Upgrade plugins and components (in ITs) Key: DOXIASITETOOLS-341 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-341 Project: Maven Doxia Sitetools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0, 2.0.0-M19 * Upgrade to Doxia 2.0.0-M12 * Upgrade to Maven Reporting API 4.0.0-M12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIASITETOOLS-340) Rearrange title order in Velocity context
Michael Osipov created DOXIASITETOOLS-340:
-
Summary: Rearrange title order in Velocity context
Key: DOXIASITETOOLS-340
URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-340
Project: Maven Doxia Sitetools
Issue Type: Dependency upgrade
Components: Site renderer
Affects Versions: 2.0.0-M18
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 2.0.0, 2.0.0-M19
Currently, the title is set as follows:
{projectName}} -- {{documentTitle}}
This causes problems when you have multiple browsers tabs open, all you see is
the project name not the document title, making is hard to identify. The
common, today's approach is to go from specific to general: {{documentTitle}}
-- {projectName}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-340) Rearrange title order in Velocity context
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-340:
--
Description:
Currently, the title is set as follows:
{projectName}} -- {{documentTitle}}
This causes problems when you have multiple browsers tabs open, all you see is
the project name not the document title, making is hard to identify. The
common, today's approach is to go from specific to general: {{documentTitle}}
-- {projectName}}. We should do the same.
was:
Currently, the title is set as follows:
{projectName}} -- {{documentTitle}}
This causes problems when you have multiple browsers tabs open, all you see is
the project name not the document title, making is hard to identify. The
common, today's approach is to go from specific to general: {{documentTitle}}
-- {projectName}}
> Rearrange title order in Velocity context
> -
>
> Key: DOXIASITETOOLS-340
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-340
> Project: Maven Doxia Sitetools
> Issue Type: Dependency upgrade
> Components: Site renderer
>Affects Versions: 2.0.0-M18
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M19
>
>
> Currently, the title is set as follows:
> {projectName}} -- {{documentTitle}}
> This causes problems when you have multiple browsers tabs open, all you see
> is the project name not the document title, making is hard to identify. The
> common, today's approach is to go from specific to general: {{documentTitle}}
> -- {projectName}}. We should do the same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MSHARED-1399) Upgrade to Doxia 2.0.0-M12
[ https://issues.apache.org/jira/browse/MSHARED-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847440#comment-17847440 ] Michael Osipov edited comment on MSHARED-1399 at 5/17/24 8:18 PM: -- Fixed with [cda5232a8110073b81a071e07f2bd03a12598ecc|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=cda5232a8110073b81a071e07f2bd03a12598ecc]. was (Author: michael-o): Fixed with [9ef677cd1800f904b8269ce234a6d8074e1197b1|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=9ef677cd1800f904b8269ce234a6d8074e1197b1]. > Upgrade to Doxia 2.0.0-M12 > -- > > Key: MSHARED-1399 > URL: https://issues.apache.org/jira/browse/MSHARED-1399 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M12 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1399) Upgrade to Doxia 2.0.0-M12
[ https://issues.apache.org/jira/browse/MSHARED-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1399. --- Resolution: Fixed Fixed with [9ef677cd1800f904b8269ce234a6d8074e1197b1|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=9ef677cd1800f904b8269ce234a6d8074e1197b1]. > Upgrade to Doxia 2.0.0-M12 > -- > > Key: MSHARED-1399 > URL: https://issues.apache.org/jira/browse/MSHARED-1399 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M12 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1399) Upgrade to Doxia 2.0.0-M12
Michael Osipov created MSHARED-1399: --- Summary: Upgrade to Doxia 2.0.0-M12 Key: MSHARED-1399 URL: https://issues.apache.org/jira/browse/MSHARED-1399 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-api Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIA-737) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
[
https://issues.apache.org/jira/browse/DOXIA-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIA-737.
Resolution: Fixed
Fixed with
[c35e61cf6119f67b992c80aa9a971a1eb6975a8d|https://gitbox.apache.org/repos/asf?p=maven-doxia.git;a=commit;h=c35e61cf6119f67b992c80aa9a971a1eb6975a8d].
> [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not
> extract document titles anymore
> --
>
> Key: DOXIA-737
> URL: https://issues.apache.org/jira/browse/DOXIA-737
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M11
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Blocker
> Fix For: 2.0.0, 2.0.0-M12
>
>
> While working on https://github.com/apache/maven-site/pull/525 the following
> happens:
> Title before:
> {project} -- {document}
> Title now:
> {project}
> The document title is not extracted from the document anymore.
> If I do the following:
> {noformat}
> diff --git
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
>
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> index 544b6b9..b6a7d1d 100644
> ---
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> +++
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> @@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
> if (!isConfigured) {
> // DOXIASITETOOLS-146 don't render comments from source
> markup
> parser.setEmitComments(false);
> -parser.setEmitAnchorsForIndexableEntries(true);
> }
> // TODO: DOXIA-111: the filter used here must be checked
> generally.
> {noformat}
> Everything works again. I bet that the {{SiteRendererSink}} does not work
> well with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSHARED-1398) StringIndexOutOfBoundsException processing record classes
[
https://issues.apache.org/jira/browse/MSHARED-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHARED-1398:
Fix Version/s: (was: maven-dependency-analyzer-next-release)
> StringIndexOutOfBoundsException processing record classes
> -
>
> Key: MSHARED-1398
> URL: https://issues.apache.org/jira/browse/MSHARED-1398
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.14.0
>Reporter: Jared Stehler
>Priority: Major
>
> Processing classes with records results in an index out of bounds exception:
> {code:java}
> Caused by: java.lang.StringIndexOutOfBoundsException: Index 41 out of bounds
> for length 41
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$1.apply(Preconditions.java:55)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$1.apply(Preconditions.java:52)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$4.apply(Preconditions.java:213)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$4.apply(Preconditions.java:210)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:98)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:106)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:302)
> at java.base@21.0.3/java.lang.String.checkIndex(String.java:4832)
> at java.base@21.0.3/java.lang.StringLatin1.charAt(StringLatin1.java:46)
> at java.base@21.0.3/java.lang.String.charAt(String.java:1555)
> at app//org.objectweb.asm.Type.getReturnTypeOffset(Type.java:378)
> at app//org.objectweb.asm.Type.getReturnType(Type.java:355)
> at
> app//org.apache.maven.shared.dependency.analyzer.asm.ResultCollector.addMethodDesc(ResultCollector.java:112)
> {code}
> I have a reproducible test case here:
> https://github.com/jaredstehler/maven-dependency-analyzer/tree/js-repro-record-error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSHARED-1398) StringIndexOutOfBoundsException processing record classes
[
https://issues.apache.org/jira/browse/MSHARED-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHARED-1398:
Fix Version/s: maven-dependency-analyzer-next-release
> StringIndexOutOfBoundsException processing record classes
> -
>
> Key: MSHARED-1398
> URL: https://issues.apache.org/jira/browse/MSHARED-1398
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.14.0
>Reporter: Jared Stehler
>Priority: Major
> Fix For: maven-dependency-analyzer-next-release
>
>
> Processing classes with records results in an index out of bounds exception:
> {code:java}
> Caused by: java.lang.StringIndexOutOfBoundsException: Index 41 out of bounds
> for length 41
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$1.apply(Preconditions.java:55)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$1.apply(Preconditions.java:52)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$4.apply(Preconditions.java:213)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions$4.apply(Preconditions.java:210)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:98)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:106)
> at
> java.base@21.0.3/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:302)
> at java.base@21.0.3/java.lang.String.checkIndex(String.java:4832)
> at java.base@21.0.3/java.lang.StringLatin1.charAt(StringLatin1.java:46)
> at java.base@21.0.3/java.lang.String.charAt(String.java:1555)
> at app//org.objectweb.asm.Type.getReturnTypeOffset(Type.java:378)
> at app//org.objectweb.asm.Type.getReturnType(Type.java:355)
> at
> app//org.apache.maven.shared.dependency.analyzer.asm.ResultCollector.addMethodDesc(ResultCollector.java:112)
> {code}
> I have a reproducible test case here:
> https://github.com/jaredstehler/maven-dependency-analyzer/tree/js-repro-record-error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MINVOKER-351) Prevent XML-prohibited characters from entering JUnit report
[
https://issues.apache.org/jira/browse/MINVOKER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847398#comment-17847398
]
Michael Osipov commented on MINVOKER-351:
-
So this output shows a lot of problems:
* You failed to provide the conditions: Maven version, Java version, plugin
versions
* The test requires Java 11, what for? Is that a JAva version specific issue?
* The IT passes with Maven 3.8.x, but fails with 3.9.x.
* Important plugins haven't been pinned
When I diff the build log with Maven 3.8.x:
{noformat}
---
T E S T S
---
Running example.minvoker351.ExampleTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{noformat}
with 3.9.6:
{noformat}
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running example.minvoker351.ExampleTest
null
!
"
#
$
%
&
'
(
)
*
+
,
-
.
/
0
1
2
3
4
5
6
7
8
9
:
;
<
=
>
?
@
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
[
\
]
^
_
`
a
b
c
d
e
f
g
h
i
j
k
l
m
n
o
p
q
r
s
t
u
v
w
x
y
z
{
|
}
~
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 s
-- in example.minvoker351.ExampleTest
[INFO]
{noformat}
I have clearly to see this requires more analysis.
[~cstamas], do you remember that we had problems with Plexus Utils with XML
parsing it had regressions compared to 3.8.x. This could be yet another
regression.
I think we need understand the cause better before we can identify where to
apply a proper fix.
> Prevent XML-prohibited characters from entering JUnit report
>
>
> Key: MINVOKER-351
> URL: https://issues.apache.org/jira/browse/MINVOKER-351
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Reporter: Mikkel Kjeldsen
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.0
>
> Attachments: minvoker-351.tar.gz
>
>
> Neither the Maven Invoker plugin's implementation of {{}}
> nor the underlying XML infrastructure directly protect against the presence
> of character literals prohibited by the XML specification, meaning such
> literals can appear in the JUnit report and render it unreadable. *I would
> appreciate if the Maven Invoker plugin could learn to strip prohibited
> literals to protect its users from creative plugins.* I argue that this is a
> safe and expected transformation that is not materially lossy.
>
> h2. Background
> MINVOKER-196 added the {{}} option [back in
> maven-invoker-plugin-3.2.1|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.2.1/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1878-L1946].
> As of [maven-invoker-plugin-3.6.0 the effective implementation of the JUnit
> report remains effectively
> unchanged|https://github.com/apache/maven-invoker-plugin/blob/maven-invoker-plugin-3.6.0/src/main/java/org/apache/maven/plugins/invoker/AbstractInvokerMojo.java#L1695-L1754].
> The JUnit report includes a {{}} element ([example
> documentation|https://github.com/testmoapp/junitxml]) whose value Maven
> Invoker populates with the raw build log contents. I've observed that this
> value is XML-escaped, which I imagine is well understood in the
> implementation, although I can't immediately find documentation to support
> that.
> However, escaping notwithstanding, a number of character literals are
> outright prohibited by the XML specifications. These literals cannot be
> escaped, and their presence renders an XML document not well formed. The
> exact set of prohibited characters varies by XML version; the report produced
> by the Maven Invoker plugin is XML version 1.0. When the Maven Invoker plugin
> reads in the build log it does not strip these character literals and neither
> does the XML writer the Maven Invoker plugin relies on. Consequently, if a
> build log ends up including a prohibited character the resulting JUnit report
> will not be well formed.
> The set of prohibited characters is the complement of [the XML
> specification's definition of {{Char}}|https://www.w3.org/TR/xml/#NT-Char].
> h2. Example
> Among the literals prohibited by XML version 1.0 is {{^H}} (backspace). When
> [pitest runs via Maven|https://pitest.org/quickstart/maven/] it prints a
> spinner to standard out, and the implementation uses backspace to render the
> spinner in place. I have used the Maven Invoker plugin with
> {{}} to verify a pitest configuration, whereby I discovered
> this limitation.
> h2. Remediation
> h3. Blame plugins
>
[jira] [Commented] (MINVOKER-351) Prevent XML-prohibited characters from entering JUnit report
[
https://issues.apache.org/jira/browse/MINVOKER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847289#comment-17847289
]
Michael Osipov commented on MINVOKER-351:
-
[~mkjeldsen], beat me, but I don't see the failure:
{noformat}
D:\Entwicklung\Projekte\minvoker-351> mvn clean verify site
[INFO] Scanning for projects...
[INFO]
[INFO] --< example.minvoker351:minvoker-351 >--
[INFO] Building minvoker-351 1.0-SNAPSHOT
[INFO] from pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ minvoker-351 ---
[INFO] Deleting D:\Entwicklung\Projekte\minvoker-351\target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
minvoker-351 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\minvoker-351\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ minvoker-351
---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
minvoker-351 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\minvoker-351\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
minvoker-351 ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ minvoker-351 ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ minvoker-351 ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar:
D:\Entwicklung\Projekte\minvoker-351\target\minvoker-351-1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-invoker-plugin:3.6.1:install (integration-test) @ minvoker-351
---
[INFO] Installing
D:\Entwicklung\Projekte\minvoker-351\target\minvoker-351-1.0-SNAPSHOT.jar to
D:\Entwicklung\Projekte\minvoker-351\target\local-repo\example\minvoker351\minvoker-351\1.0-SNAPSHOT\minvoker-351-1.0-SNAPSHOT.jar
[INFO] Installing D:\Entwicklung\Projekte\minvoker-351\pom.xml to
D:\Entwicklung\Projekte\minvoker-351\target\local-repo\example\minvoker351\minvoker-351\1.0-SNAPSHOT\minvoker-351-1.0-SNAPSHOT.pom
[INFO]
[INFO] --- maven-invoker-plugin:3.6.1:run (integration-test) @ minvoker-351 ---
[INFO] Building: minvoker-351\pom.xml
[INFO] minvoker-351\pom.xml . SUCCESS
(15.12 s)
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 1, Failed: 0, Errors: 0, Skipped: 0
[INFO] -
[INFO]
[INFO] --- maven-site-plugin:3.12.1:site (default-site) @ minvoker-351 ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:3.5.0
[INFO] 15 reports detected for maven-project-info-reports-plugin:3.5.0:
ci-management, dependencies, dependency-info, dependency-management,
distribution-management, index, issue-management, licenses, mailing-lists,
modules, plugin-management, plugins, scm, summary, team
[INFO] configuring report plugin
org.apache.maven.plugins:maven-surefire-report-plugin:3.2.5
[INFO] preparing maven-surefire-report-plugin:report report requires
'[surefire]test' forked phase execution
[INFO]
[INFO] >>> maven-surefire-report-plugin:3.2.5:report > [surefire]test @
minvoker-351 >>>
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
minvoker-351 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\minvoker-351\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ minvoker-351
---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
minvoker-351 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
D:\Entwicklung\Projekte\minvoker-351\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
minvoker-351 ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ minvoker-351 ---
[INFO] No tests to run.
[INFO] Skipping execution of surefire because it has already been run for this
configuration
[INFO]
[INFO] <<< maven-surefire-report-plugin:3.2.5:report < [surefire]test @
minvoker-351 <<<
[INFO]
[INFO] '[surefire]test' forked phase execution for
maven-surefire-report-plugin:report report preparation done
[INFO] 3 reports detected for maven-surefire-report-plugin:3.2.5:
failsafe-report-only, report, report-only
[INFO] Rendering site with default locale English (en)
[WARNING] No project URL defined - decoration links will not be relativized!
[INFO] Rendering
[jira] [Updated] (MNG-8124) Allow regex usage in any profile activation key/value
[ https://issues.apache.org/jira/browse/MNG-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-8124: Description: Following up on MNG-5726 I'd like to request allowing the use of regex for any key/value pair. For example, one should be able to use regex in property names or values, OS names or values, etc. Justification: Many users have been asking for the ability to logically-OR multiple conditions. Allowing the use of regex will go a long way in resolving those use-cases. was: Following up on https://issues.apache.org/jira/browse/MNG-5726 I'd like to request allowing the use of regex for any key/value pair. For example, one should be able to use regex in property names or values, OS names or values, etc. Justification: Many users have been asking for the ability to logically-OR multiple conditions. Allowing the use of regex will go a long way in resolving those use-cases. > Allow regex usage in any profile activation key/value > - > > Key: MNG-8124 > URL: https://issues.apache.org/jira/browse/MNG-8124 > Project: Maven > Issue Type: Improvement > Components: Profiles >Affects Versions: 3.9.6 >Reporter: Gili >Priority: Major > > Following up on MNG-5726 I'd like to request allowing the use of regex for > any key/value pair. For example, one should be able to use regex in property > names or values, OS names or values, etc. > Justification: Many users have been asking for the ability to logically-OR > multiple conditions. Allowing the use of regex will go a long way in > resolving those use-cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DOXIA-737) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
[
https://issues.apache.org/jira/browse/DOXIA-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847096#comment-17847096
]
Michael Osipov commented on DOXIA-737:
--
Found it, truly a regression. {{IndexingSink}} was not passing the title text
to the super class.
> [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not
> extract document titles anymore
> --
>
> Key: DOXIA-737
> URL: https://issues.apache.org/jira/browse/DOXIA-737
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M11
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Blocker
> Fix For: 2.0.0, 2.0.0-M12
>
>
> While working on https://github.com/apache/maven-site/pull/525 the following
> happens:
> Title before:
> {project} -- {document}
> Title now:
> {project}
> The document title is not extracted from the document anymore.
> If I do the following:
> {noformat}
> diff --git
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
>
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> index 544b6b9..b6a7d1d 100644
> ---
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> +++
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> @@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
> if (!isConfigured) {
> // DOXIASITETOOLS-146 don't render comments from source
> markup
> parser.setEmitComments(false);
> -parser.setEmitAnchorsForIndexableEntries(true);
> }
> // TODO: DOXIA-111: the filter used here must be checked
> generally.
> {noformat}
> Everything works again. I bet that the {{SiteRendererSink}} does not work
> well with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DOXIA-737) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
[
https://issues.apache.org/jira/browse/DOXIA-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIA-737:
-
Fix Version/s: 2.0.0-M12
2.0.0
> [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not
> extract document titles anymore
> --
>
> Key: DOXIA-737
> URL: https://issues.apache.org/jira/browse/DOXIA-737
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M11
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Blocker
> Fix For: 2.0.0, 2.0.0-M12
>
>
> While working on https://github.com/apache/maven-site/pull/525 the following
> happens:
> Title before:
> {project} -- {document}
> Title now:
> {project}
> The document title is not extracted from the document anymore.
> If I do the following:
> {noformat}
> diff --git
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
>
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> index 544b6b9..b6a7d1d 100644
> ---
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> +++
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> @@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
> if (!isConfigured) {
> // DOXIASITETOOLS-146 don't render comments from source
> markup
> parser.setEmitComments(false);
> -parser.setEmitAnchorsForIndexableEntries(true);
> }
> // TODO: DOXIA-111: the filter used here must be checked
> generally.
> {noformat}
> Everything works again. I bet that the {{SiteRendererSink}} does not work
> well with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Moved] (DOXIA-737) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
[
https://issues.apache.org/jira/browse/DOXIA-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov moved DOXIASITETOOLS-339 to DOXIA-737:
-
Component/s: Core
(was: Site renderer)
Key: DOXIA-737 (was: DOXIASITETOOLS-339)
Affects Version/s: 2.0.0-M11
(was: 2.0.0-M18)
Project: Maven Doxia (was: Maven Doxia Sitetools)
> [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not
> extract document titles anymore
> --
>
> Key: DOXIA-737
> URL: https://issues.apache.org/jira/browse/DOXIA-737
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M11
>Reporter: Michael Osipov
>Priority: Blocker
>
> While working on https://github.com/apache/maven-site/pull/525 the following
> happens:
> Title before:
> {project} -- {document}
> Title now:
> {project}
> The document title is not extracted from the document anymore.
> If I do the following:
> {noformat}
> diff --git
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
>
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> index 544b6b9..b6a7d1d 100644
> ---
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> +++
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> @@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
> if (!isConfigured) {
> // DOXIASITETOOLS-146 don't render comments from source
> markup
> parser.setEmitComments(false);
> -parser.setEmitAnchorsForIndexableEntries(true);
> }
> // TODO: DOXIA-111: the filter used here must be checked
> generally.
> {noformat}
> Everything works again. I bet that the {{SiteRendererSink}} does not work
> well with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (DOXIA-737) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
[
https://issues.apache.org/jira/browse/DOXIA-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned DOXIA-737:
Assignee: Michael Osipov
> [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not
> extract document titles anymore
> --
>
> Key: DOXIA-737
> URL: https://issues.apache.org/jira/browse/DOXIA-737
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M11
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Blocker
>
> While working on https://github.com/apache/maven-site/pull/525 the following
> happens:
> Title before:
> {project} -- {document}
> Title now:
> {project}
> The document title is not extracted from the document anymore.
> If I do the following:
> {noformat}
> diff --git
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
>
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> index 544b6b9..b6a7d1d 100644
> ---
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> +++
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> @@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
> if (!isConfigured) {
> // DOXIASITETOOLS-146 don't render comments from source
> markup
> parser.setEmitComments(false);
> -parser.setEmitAnchorsForIndexableEntries(true);
> }
> // TODO: DOXIA-111: the filter used here must be checked
> generally.
> {noformat}
> Everything works again. I bet that the {{SiteRendererSink}} does not work
> well with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNGSITE-537) Set up CI for the GitHub repo
[ https://issues.apache.org/jira/browse/MNGSITE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNGSITE-537: --- Summary: Set up CI for the GitHub repo (was: Set up CI for the Giothub repo) > Set up CI for the GitHub repo > - > > Key: MNGSITE-537 > URL: https://issues.apache.org/jira/browse/MNGSITE-537 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Elliotte Rusty Harold >Priority: Major > > https://github.com/apache/maven-site/ seems to have no Continuous integration > checks. We should set some up. I'm pretty sure I've broken the site build in > the past by merging bad code, and if I haven't yet, I will in the future > without some guard rails. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1392) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/MSHARED-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1392. --- Resolution: Fixed Fixed with [2cd21f6537e066c70f9d002e972a6312cfb5ad25|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git=commit=2cd21f6537e066c70f9d002e972a6312cfb5ad25] for maven-reporting-exec. > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: MSHARED-1392 > URL: https://issues.apache.org/jira/browse/MSHARED-1392 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api, maven-reporting-exec, > maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-impl-4.0.0, > maven-reporting-exec-2.0.0, maven-reporting-api-4.0.0-M12, > maven-reporting-impl-4.0.0-M15, maven-reporting-exec-2.0.0-M14 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNGSITE-538) Drop generation of site JAR
[ https://issues.apache.org/jira/browse/MNGSITE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845966#comment-17845966 ] Michael Osipov edited comment on MNGSITE-538 at 5/13/24 2:33 PM: - Fixed with [0bd98e267e38c258236fff79a48467c8ca7049d9|https://gitbox.apache.org/repos/asf?p=maven-site.git=commit=0bd98e267e38c258236fff79a48467c8ca7049d9]. was (Author: michael-o): Fixed with [0bd98e267e38c258236fff79a48467c8ca7049d9|https://gitbox.apache.org/repos/asf?p=maven-plugin-tools.git=commit=0bd98e267e38c258236fff79a48467c8ca7049d9]. > Drop generation of site JAR > --- > > Key: MNGSITE-538 > URL: https://issues.apache.org/jira/browse/MNGSITE-538 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > > Is is highly questionable that anyone needs this site JAR. It wastes cycles. > Let's drop it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNGSITE-538) Drop generation of site JAR
[ https://issues.apache.org/jira/browse/MNGSITE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNGSITE-538. -- Resolution: Fixed Fixed with [0bd98e267e38c258236fff79a48467c8ca7049d9|https://gitbox.apache.org/repos/asf?p=maven-plugin-tools.git=commit=0bd98e267e38c258236fff79a48467c8ca7049d9]. > Drop generation of site JAR > --- > > Key: MNGSITE-538 > URL: https://issues.apache.org/jira/browse/MNGSITE-538 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > > Is is highly questionable that anyone needs this site JAR. It wastes cycles. > Let's drop it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNGSITE-538) Drop generation of site JAR
[ https://issues.apache.org/jira/browse/MNGSITE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845854#comment-17845854 ] Michael Osipov commented on MNGSITE-538: Then we should leave it. I wonder how the access logs for this resource look like. Means: Do people download it at all? > Drop generation of site JAR > --- > > Key: MNGSITE-538 > URL: https://issues.apache.org/jira/browse/MNGSITE-538 > Project: Maven Project Web Site > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > > Is is highly questionable that anyone needs this site JAR. It wastes cycles. > Let's drop it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNGSITE-538) Drop generation of site JAR
Michael Osipov created MNGSITE-538: -- Summary: Drop generation of site JAR Key: MNGSITE-538 URL: https://issues.apache.org/jira/browse/MNGSITE-538 Project: Maven Project Web Site Issue Type: Task Reporter: Michael Osipov Assignee: Michael Osipov Is is highly questionable that anyone needs this site JAR. It wastes cycles. Let's drop it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAR-310) [REGRESSION] Version 3.4.x fails to handle toolchain paths that contain spaces
[
https://issues.apache.org/jira/browse/MJAR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAR-310:
Summary: [REGRESSION] Version 3.4.x fails to handle toolchain paths that
contain spaces (was: [regression] Version 3.4.x fails to handle toolchain
paths that contain spaces)
> [REGRESSION] Version 3.4.x fails to handle toolchain paths that contain spaces
> --
>
> Key: MJAR-310
> URL: https://issues.apache.org/jira/browse/MJAR-310
> Project: Maven JAR Plugin
> Issue Type: Bug
> Environment: Maven 3.9.6
> Windows 10
>Reporter: Gili
>Priority: Major
>
> When upgrading from version 3.3.0 to 3.4.0 I started getting the following
> build-time warning:
>
> {{[WARNING] Unrecognized output form C:\Program
> Files\Java\zulu-8\bin\javac.exe -version - 'C:\Program' is not recognized as
> an internal or external command,}}
> {{operable program or batch file.}}
>
> The contents of toolchain.xml is:
>
> {{}}
> {{}}
> {{ }}
> {{ jdk}}
> {{ }}
> {{ 8}}
> {{ zulu}}
> {{ }}
> {{ }}
> {{ C:\Program Files\Java\zulu-8}}
> {{ }}
> {{ }}
> {{}}
>
> I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAR-310) [REGRESSION] Version 3.4.x fails to handle toolchain paths that contain spaces
[
https://issues.apache.org/jira/browse/MJAR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAR-310:
Affects Version/s: 3.4.1
3.4.0
> [REGRESSION] Version 3.4.x fails to handle toolchain paths that contain spaces
> --
>
> Key: MJAR-310
> URL: https://issues.apache.org/jira/browse/MJAR-310
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 3.4.0, 3.4.1
> Environment: Maven 3.9.6
> Windows 10
>Reporter: Gili
>Priority: Major
>
> When upgrading from version 3.3.0 to 3.4.0 I started getting the following
> build-time warning:
>
> {{[WARNING] Unrecognized output form C:\Program
> Files\Java\zulu-8\bin\javac.exe -version - 'C:\Program' is not recognized as
> an internal or external command,}}
> {{operable program or batch file.}}
>
> The contents of toolchain.xml is:
>
> {{}}
> {{}}
> {{ }}
> {{ jdk}}
> {{ }}
> {{ 8}}
> {{ zulu}}
> {{ }}
> {{ }}
> {{ C:\Program Files\Java\zulu-8}}
> {{ }}
> {{ }}
> {{}}
>
> I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MJAR-310) [REGRESSION] Plugin fails to handle toolchain paths that contain spaces
[
https://issues.apache.org/jira/browse/MJAR-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAR-310:
Summary: [REGRESSION] Plugin fails to handle toolchain paths that contain
spaces (was: [REGRESSION] Version 3.4.x fails to handle toolchain paths that
contain spaces)
> [REGRESSION] Plugin fails to handle toolchain paths that contain spaces
> ---
>
> Key: MJAR-310
> URL: https://issues.apache.org/jira/browse/MJAR-310
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 3.4.0, 3.4.1
> Environment: Maven 3.9.6
> Windows 10
>Reporter: Gili
>Priority: Major
>
> When upgrading from version 3.3.0 to 3.4.0 I started getting the following
> build-time warning:
>
> {{[WARNING] Unrecognized output form C:\Program
> Files\Java\zulu-8\bin\javac.exe -version - 'C:\Program' is not recognized as
> an internal or external command,}}
> {{operable program or batch file.}}
>
> The contents of toolchain.xml is:
>
> {{}}
> {{}}
> {{ }}
> {{ jdk}}
> {{ }}
> {{ 8}}
> {{ zulu}}
> {{ }}
> {{ }}
> {{ C:\Program Files\Java\zulu-8}}
> {{ }}
> {{ }}
> {{}}
>
> I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-339) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-339:
--
Description:
While working on https://github.com/apache/maven-site/pull/525 the following
happens:
Title before:
{project} -- {document}
Title now:
{project}
The document title is not extracted from the document anymore.
If I do the following:
{noformat}
diff --git
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
index 544b6b9..b6a7d1d 100644
---
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
+++
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
@@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
if (!isConfigured) {
// DOXIASITETOOLS-146 don't render comments from source markup
parser.setEmitComments(false);
-parser.setEmitAnchorsForIndexableEntries(true);
}
// TODO: DOXIA-111: the filter used here must be checked generally.
{noformat}
Everything works again. I bet that the {{SiteRendererSink}} does not work well
with the new approach in Doxia.
was:
While working on https://github.com/apache/maven-site/pull/525 the following
happens:
Title before:
{project} -- {document}
Title now:
{project}
The document title is not extracted from the document anymore.
If I do the following:
{noformat}
diff --git
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
index 544b6b9..b6a7d1d 100644
---
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
+++
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
@@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
if (!isConfigured) {
// DOXIASITETOOLS-146 don't render comments from source markup
parser.setEmitComments(false);
-parser.setEmitAnchorsForIndexableEntries(true);
}
// TODO: DOXIA-111: the filter used here must be checked generally.
{noformat}
Everything works again. I bet that the {{SiteRendererSink}} does not work well
with the new approach in Doxia.
> [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not
> extract document titles anymore
> --
>
> Key: DOXIASITETOOLS-339
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-339
> Project: Maven Doxia Sitetools
> Issue Type: Bug
> Components: Site renderer
>Affects Versions: 2.0.0-M18
>Reporter: Michael Osipov
>Priority: Blocker
>
> While working on https://github.com/apache/maven-site/pull/525 the following
> happens:
> Title before:
> {project} -- {document}
> Title now:
> {project}
> The document title is not extracted from the document anymore.
> If I do the following:
> {noformat}
> diff --git
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
>
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> index 544b6b9..b6a7d1d 100644
> ---
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> +++
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> @@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
> if (!isConfigured) {
> // DOXIASITETOOLS-146 don't render comments from source
> markup
> parser.setEmitComments(false);
> -parser.setEmitAnchorsForIndexableEntries(true);
> }
> // TODO: DOXIA-111: the filter used here must be checked
> generally.
> {noformat}
> Everything works again. I bet that the {{SiteRendererSink}} does not work
> well with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DOXIASITETOOLS-339) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845825#comment-17845825
]
Michael Osipov commented on DOXIASITETOOLS-339:
---
[~kwin], can you investigate because you know the new Doxia code best? Maybe
the actual bug is in Doxia, not here.
> [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not
> extract document titles anymore
> --
>
> Key: DOXIASITETOOLS-339
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-339
> Project: Maven Doxia Sitetools
> Issue Type: Bug
> Components: Site renderer
>Affects Versions: 2.0.0-M18
>Reporter: Michael Osipov
>Priority: Blocker
>
> While working on https://github.com/apache/maven-site/pull/525 the following
> happens:
> Title before:
> {project} -- {document}
> Title now:
> {project}
> The document title is not extracted from the document anymore.
> If I do the following:
> {noformat}
> diff --git
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
>
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> index 544b6b9..b6a7d1d 100644
> ---
> a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> +++
> b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
> @@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
> if (!isConfigured) {
> // DOXIASITETOOLS-146 don't render comments from source
> markup
> parser.setEmitComments(false);
> -parser.setEmitAnchorsForIndexableEntries(true);
> }
> // TODO: DOXIA-111: the filter used here must be checked
> generally.
> {noformat}
> Everything works again. I bet that the {{SiteRendererSink}} does not work
> well with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (DOXIASITETOOLS-339) [REGRESSION] Making EmitAnchorsForIndexableEntries by default does not extract document titles anymore
Michael Osipov created DOXIASITETOOLS-339:
-
Summary: [REGRESSION] Making EmitAnchorsForIndexableEntries by
default does not extract document titles anymore
Key: DOXIASITETOOLS-339
URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-339
Project: Maven Doxia Sitetools
Issue Type: Bug
Components: Site renderer
Affects Versions: 2.0.0-M18
Reporter: Michael Osipov
While working on https://github.com/apache/maven-site/pull/525 the following
happens:
Title before:
{project} -- {document}
Title now:
{project}
The document title is not extracted from the document anymore.
If I do the following:
{noformat}
diff --git
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
index 544b6b9..b6a7d1d 100644
---
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
+++
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
@@ -330,7 +330,6 @@ public class DefaultSiteRenderer implements Renderer {
if (!isConfigured) {
// DOXIASITETOOLS-146 don't render comments from source markup
parser.setEmitComments(false);
-parser.setEmitAnchorsForIndexableEntries(true);
}
// TODO: DOXIA-111: the filter used here must be checked generally.
{noformat}
Everything works again. I bet that the {{SiteRendererSink}} does not work well
with the new approach in Doxia.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MTOOLCHAINS-54) [regression] Paths with spaces trigger a build-time warning
[
https://issues.apache.org/jira/browse/MTOOLCHAINS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MTOOLCHAINS-54.
-
Resolution: Not A Problem
> [regression] Paths with spaces trigger a build-time warning
> ---
>
> Key: MTOOLCHAINS-54
> URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-54
> Project: Maven Toolchains Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
> Environment: Maven 3.9.6
>Reporter: Gili
>Priority: Major
>
> When upgrading from version 3.1.0 to 3.2.0 I started getting the following
> build-time warning:
>
> {{[WARNING] Unrecognized output form C:\Program
> Files\Java\zulu-8\bin\javac.exe -version - 'C:\Program' is not recognized as
> an internal or external command,}}
> {{operable program or batch file.}}
>
> The contents of toolchain.xml is:
>
> {{}}
> {{}}
> {{ }}
> {{ jdk}}
> {{ }}
> {{ 8}}
> {{ zulu}}
> {{ }}
> {{ }}
> {{ C:\Program Files\Java\zulu-8}}
> {{ }}
> {{ }}
> {{}}
>
> I don't know if this warning breaks anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSKINS-246) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSKINS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSKINS-246. - Resolution: Fixed Fixed with [1f449b606ab455c61dc25f56e68d371e659bfe90|https://gitbox.apache.org/repos/asf?p=maven-fluido-skin.git;a=commit;h=1f449b606ab455c61dc25f56e68d371e659bfe90]. > Upgrade plugins and components (in ITs) > --- > > Key: MSKINS-246 > URL: https://issues.apache.org/jira/browse/MSKINS-246 > Project: Maven Skins > Issue Type: Dependency upgrade > Components: Fluido Skin >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-2.0.0-M9, fluido-2.0.0 > > > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Site Plugin 4.0.0-M14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1392) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/MSHARED-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845638#comment-17845638 ] Michael Osipov commented on MSHARED-1392: - Fixed with [7bff1c2ddbe6d196ab71ad196a0367235a694332|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=7bff1c2ddbe6d196ab71ad196a0367235a694332] for maven-reporting-impl. > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: MSHARED-1392 > URL: https://issues.apache.org/jira/browse/MSHARED-1392 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api, maven-reporting-exec, > maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-impl-4.0.0, > maven-reporting-exec-2.0.0, maven-reporting-api-4.0.0-M12, > maven-reporting-impl-4.0.0-M15, maven-reporting-exec-2.0.0-M14 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1392) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/MSHARED-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1392: Summary: Upgrade to Parent 42 and Maven 3.6.3 (was: Upgrade to Parent 42) > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: MSHARED-1392 > URL: https://issues.apache.org/jira/browse/MSHARED-1392 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api, maven-reporting-exec, > maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-impl-4.0.0, > maven-reporting-exec-2.0.0, maven-reporting-api-4.0.0-M12, > maven-reporting-impl-4.0.0-M15, maven-reporting-exec-2.0.0-M14 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (MPMD-395) Build doesn't fail for invalid CPD format
[ https://issues.apache.org/jira/browse/MPMD-395 ] Michael Osipov deleted comment on MPMD-395: - was (Author: githubbot): michael-o commented on PR #150: URL: https://github.com/apache/maven-pmd-plugin/pull/150#issuecomment-2104284197 Is this the fix for https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392? > Build doesn't fail for invalid CPD format > - > > Key: MPMD-395 > URL: https://issues.apache.org/jira/browse/MPMD-395 > Project: Maven PMD Plugin > Issue Type: Bug > Components: CPD >Affects Versions: 3.22.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > > See > [https://github.com/apache/maven-pmd-plugin/pull/144#issuecomment-2094371392] > > If an exception occurs while the CPD report is created, the exception is only > logged but doesn't fail the build. This means, that build appears to be > successful, although it didn't produce all expected build artifacts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1396) Upgrade to Doxia 2.0.0-M11
[ https://issues.apache.org/jira/browse/MSHARED-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1396. --- Resolution: Fixed Fixed with [7c0a727ea22e2c31731b5165bf5c794f5f4bc850|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=7c0a727ea22e2c31731b5165bf5c794f5f4bc850]. > Upgrade to Doxia 2.0.0-M11 > -- > > Key: MSHARED-1396 > URL: https://issues.apache.org/jira/browse/MSHARED-1396 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M12 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-338) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-338: -- Summary: Upgrade to Parent 42 and Maven 3.6.3 (was: Upgrade to Parent 42) > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: DOXIASITETOOLS-338 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-338 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M19 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-338) Upgrade to Parent 42 and Maven 3.6.3
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-338. - Resolution: Fixed Fixed with [6f232441482c220e8d31c05a50161ca55c45f30d|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=6f232441482c220e8d31c05a50161ca55c45f30d]. > Upgrade to Parent 42 and Maven 3.6.3 > > > Key: DOXIASITETOOLS-338 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-338 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M19 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1396) Upgrade to Doxia 2.0.0-M11
Michael Osipov created MSHARED-1396: --- Summary: Upgrade to Doxia 2.0.0-M11 Key: MSHARED-1396 URL: https://issues.apache.org/jira/browse/MSHARED-1396 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-api Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSKINS-246) Upgrade plugins and components (in ITs)
Michael Osipov created MSKINS-246: - Summary: Upgrade plugins and components (in ITs) Key: MSKINS-246 URL: https://issues.apache.org/jira/browse/MSKINS-246 Project: Maven Skins Issue Type: Dependency upgrade Components: Fluido Skin Reporter: Michael Osipov Assignee: Michael Osipov Fix For: fluido-2.0.0-M9, fluido-2.0.0 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Site Plugin 4.0.0-M14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIASITETOOLS-338) Upgrade to Parent 42
Michael Osipov created DOXIASITETOOLS-338: - Summary: Upgrade to Parent 42 Key: DOXIASITETOOLS-338 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-338 Project: Maven Doxia Sitetools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0, 2.0.0-M19 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1392) Upgrade to Parent 42
[ https://issues.apache.org/jira/browse/MSHARED-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844419#comment-17844419 ] Michael Osipov commented on MSHARED-1392: - Fixed with [b5b66f4c6e468685f5105e8d2a965f240b335f5f|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=b5b66f4c6e468685f5105e8d2a965f240b335f5f] for maven-reporting-api. > Upgrade to Parent 42 > > > Key: MSHARED-1392 > URL: https://issues.apache.org/jira/browse/MSHARED-1392 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api, maven-reporting-exec, > maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-impl-4.0.0, > maven-reporting-exec-2.0.0, maven-reporting-api-4.0.0-M12, > maven-reporting-impl-4.0.0-M15, maven-reporting-exec-2.0.0-M14 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1392) Upgrade to Parent 42
Michael Osipov created MSHARED-1392: --- Summary: Upgrade to Parent 42 Key: MSHARED-1392 URL: https://issues.apache.org/jira/browse/MSHARED-1392 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-api, maven-reporting-exec, maven-reporting-impl Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-impl-4.0.0-M15, maven-reporting-exec-2.0.0-M14, maven-reporting-api-4.0.0, maven-reporting-impl-4.0.0, maven-reporting-exec-2.0.0, maven-reporting-api-4.0.0-M12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIA-736) Upgrade to Parent 42
[ https://issues.apache.org/jira/browse/DOXIA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIA-736. Resolution: Fixed Fixed with [11c6a53f9308848813fa09ce4a7d111ce2e75ee0|https://gitbox.apache.org/repos/asf?p=maven-doxia.git;a=commit;h=11c6a53f9308848813fa09ce4a7d111ce2e75ee0]. > Upgrade to Parent 42 > > > Key: DOXIA-736 > URL: https://issues.apache.org/jira/browse/DOXIA-736 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M11 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIA-736) Upgrade to Parent 42
Michael Osipov created DOXIA-736: Summary: Upgrade to Parent 42 Key: DOXIA-736 URL: https://issues.apache.org/jira/browse/DOXIA-736 Project: Maven Doxia Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0, 2.0.0-M11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSITE-1000) Allow parametrisation of Doxia parser per file
[
https://issues.apache.org/jira/browse/MSITE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-1000:
--
Description:
Currently only the attributes used for rendering the site can be parameterized
in
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
There is no possibility to configure the parser in
https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
per document.
This would be nice in the context of
https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
should be switched on/off for certain documents. Also generation of comments
may be desirable for certain documents.
I propose the following additional plugin goal parameter:
{code}
**/apt/**
false
true
{code}
where {{parserConfigurations}} is an array of a complex type with (include)
patterns on the source path (String array) and boolean methods for features.
This also required an upgrade to Maven Plugin Tools 3.13.0.
was:
Currently only the attributes used for rendering the site can be parameterized
in
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
There is no possibility to configure the parser in
https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
per document.
This would be nice in the context of
https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
should be switched on/off for certain documents. Also generation of comments
may be desirable for certain documents.
I propose the following additional plugin goal parameter:
{code}
**/apt/**
false
true
{code}
where {{parserConfigurations}} is an array of a complex type with (include)
patterns on the source path (String array) and boolean methods for features.
This also required an upgrade to Maven Plugin Tools 3.13.0
> Allow parametrisation of Doxia parser per file
> --
>
> Key: MSITE-1000
> URL: https://issues.apache.org/jira/browse/MSITE-1000
> Project: Maven Site Plugin
> Issue Type: New Feature
> Components: doxia integration
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently only the attributes used for rendering the site can be
> parameterized in
> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
> There is no possibility to configure the parser in
> https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
> per document.
> This would be nice in the context of
> https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
> should be switched on/off for certain documents. Also generation of comments
> may be desirable for certain documents.
> I propose the following additional plugin goal parameter:
> {code}
>
>
>
> **/apt/**
>
> false
> true
>
>
> {code}
> where {{parserConfigurations}} is an array of a complex type with (include)
> patterns on the source path (String array) and boolean methods for features.
>
> This also required an upgrade to Maven Plugin Tools 3.13.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-1000) Allow parametrisation of Doxia parser per file
[
https://issues.apache.org/jira/browse/MSITE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-1000:
--
Description:
Currently only the attributes used for rendering the site can be parameterized
in
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
There is no possibility to configure the parser in
https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
per document.
This would be nice in the context of
https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
should be switched on/off for certain documents. Also generation of comments
may be desirable for certain documents.
I propose the following additional plugin goal parameter:
{code}
**/apt/**
false
true
{code}
where {{parserConfigurations}} is an array of a complex type with (include)
patterns on the source path (String array) and boolean methods for features.
This also required an upgrade to Maven Plugin Tools 3.13.0
was:
Currently only the attributes used for rendering the site can be parameterized
in
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
There is no possibility to configure the parser in
https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
per document.
This would be nice in the context of
https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
should be switched on/off for certain documents. Also generation of comments
may be desirable for certain documents.
I propose the following additional plugin goal parameter:
{code}
**/apt/**
false
true
{code}
where {{parserConfigurations}} is an array of a complex type with (include)
patterns on the source path (String array) and boolean methods for features.
> Allow parametrisation of Doxia parser per file
> --
>
> Key: MSITE-1000
> URL: https://issues.apache.org/jira/browse/MSITE-1000
> Project: Maven Site Plugin
> Issue Type: New Feature
> Components: doxia integration
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently only the attributes used for rendering the site can be
> parameterized in
> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#attributes.
> There is no possibility to configure the parser in
> https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L322
> per document.
> This would be nice in the context of
> https://issues.apache.org/jira/browse/DOXIA-722 where generation of anchors
> should be switched on/off for certain documents. Also generation of comments
> may be desirable for certain documents.
> I propose the following additional plugin goal parameter:
> {code}
>
>
>
> **/apt/**
>
> false
> true
>
>
> {code}
> where {{parserConfigurations}} is an array of a complex type with (include)
> patterns on the source path (String array) and boolean methods for features.
>
> This also required an upgrade to Maven Plugin Tools 3.13.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8116) Plugin configuration can randomly fail in case of method overloading as it doesn't take into account implementation attribute
[
https://issues.apache.org/jira/browse/MNG-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-8116:
Summary: Plugin configuration can randomly fail in case of method
overloading as it doesn't take into account implementation attribute (was:
Plugin configuration can randomly fail in case of method overloading as it
doesn't take into account implementation attriute)
> Plugin configuration can randomly fail in case of method overloading as it
> doesn't take into account implementation attribute
> -
>
> Key: MNG-8116
> URL: https://issues.apache.org/jira/browse/MNG-8116
> Project: Maven
> Issue Type: Task
> Components: Plugin Requests
>Affects Versions: 3.9.6
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.9.7
>
>
> Originally discovered via a Jetty bug report see
> https://github.com/jetty/jetty.project/issues/11732
> The bean to configured have the following overloading method naming:
> * public void setExtraClasspath(String extraClasspath)
> * public void setExtraClasspath(List extraClasspath)
> The plugin configuration:
>
> ${basedir}/config
>
> even forcing the implementation attribute doesn't help
>
>implementation="java.lang.String">${basedir}/config
>
> The fix is implemented via the PR
> https://github.com/eclipse/sisu.plexus/pull/52
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSITE-1006) MSITE-723 causes duplicate document rendering and log output
[
https://issues.apache.org/jira/browse/MSITE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSITE-1006.
-
Resolution: Fixed
Fixed with
[b3a063b17f2a2a15b02b179b84103e0bf6330c87|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=b3a063b17f2a2a15b02b179b84103e0bf6330c87].
> MSITE-723 causes duplicate document rendering and log output
>
>
> Key: MSITE-1006
> URL: https://issues.apache.org/jira/browse/MSITE-1006
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: doxia integration
>Affects Versions: 4.0.0-M13
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M14
>
>
> Consider the following output:
> {noformat}
> ...
> [INFO] --- maven-site-plugin:3.12.1:site (default-site) @ doxia-skin-model ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.5
> [INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.5:
> index, summary, dependency-info, modules, team, scm, issue-management,
> mailing-lists, dependency-management, dependencies, dependency-convergence,
> ci-management, plugin-management, plugins, distribution-management
> [INFO] Rendering site with default locale English (en)
> [INFO] Relativizing decoration links with respect to localized project URL:
> https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
> [INFO] Rendering content with
> org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin.
> [INFO] Skipped "About" report
> (maven-project-info-reports-plugin:3.4.5:index), file "index.html" already
> exists.
> [INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:3.4.5:summary
> [INFO] Generating "Dependency Information" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-info
> [INFO] Generating "Team" report ---
> maven-project-info-reports-plugin:3.4.5:team
> [INFO] Generating "Source Code Management" report ---
> maven-project-info-reports-plugin:3.4.5:scm
> [INFO] Generating "Issue Management" report ---
> maven-project-info-reports-plugin:3.4.5:issue-management
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:3.4.5:mailing-lists
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-management
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:3.4.5:dependencies
> [INFO] Generating "Dependency Convergence" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-convergence
> [INFO] Generating "CI Management" report---
> maven-project-info-reports-plugin:3.4.5:ci-management
> [INFO] Generating "Plugin Management" report---
> maven-project-info-reports-plugin:3.4.5:plugin-management
> [INFO] Generating "Plugins" report ---
> maven-project-info-reports-plugin:3.4.5:plugins
> [INFO] Generating "Distribution Management" report ---
> maven-project-info-reports-plugin:3.4.5:distribution-management
> [INFO] Rendering 1 generated Doxia document: 1 xdoc
> ...
> {noformat}
> Let's locate these two handwritten documents:
> {noformat}
> ~/var/Projekte/maven-doxia-sitetools (master =)
> $ tree doxia-skin-model/src/site/
> doxia-skin-model/src/site/
> ├── apt
> │ └── index.apt
> └── site.xml
> 2 directories, 2 files
> {noformat}
> There aren't. This is caused by MSITE-723 which add generated documents for
> the first round of rendering (non-editable ones), then does the rendering,
> does reports and then allows generated documents to overwrite report output
> by running generated rendering again.
> This is suboptimal since it causes:
> * Duplicate rendering
> * Deceiving log output
> * Maven Fluido Skin generates an "Edit Button" for such content sind the
> editable flag is set to true:
> view-source:https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-2.0.0-M16/doxia-skin-model/skin.html
> The solution to the problem is to flag the document renderer for such output
> with Sitetools to allow unconditional overwrite. We need to fix Doxia
> Sitetools first and then we can fix in this plugin.
> Block in question:
> https://github.com/apache/maven-site-plugin/blob/036997f9a70b7394d9a9771ede04a686aca834e1/src/main/java/org/apache/maven/plugins/site/render/SiteMojo.java#L123-L167
> This needs to be {{true}}:
> https://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/xref/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.html#L61
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MINVOKER-364) Rename invoker.systemPropertiesFile to invoker.userPropertiesFile
[ https://issues.apache.org/jira/browse/MINVOKER-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843181#comment-17843181 ] Michael Osipov commented on MINVOKER-364: - System properties are/will be handled separately? > Rename invoker.systemPropertiesFile to invoker.userPropertiesFile > - > > Key: MINVOKER-364 > URL: https://issues.apache.org/jira/browse/MINVOKER-364 > Project: Maven Invoker Plugin > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.6.2 > > > Old property will be deprecated > It are user properties added to cli - not a system properties -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPLUGIN-521) Nested types not properly extracted cause exception while generating Javadoc URLs
[
https://issues.apache.org/jira/browse/MPLUGIN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPLUGIN-521.
--
Resolution: Fixed
Fixed with
[789315b6958250c0e2e9291bb407a25fdd5112e3|https://gitbox.apache.org/repos/asf?p=maven-plugin-tools.git;a=commit;h=789315b6958250c0e2e9291bb407a25fdd5112e3].
> Nested types not properly extracted cause exception while generating Javadoc
> URLs
> -
>
> Key: MPLUGIN-521
> URL: https://issues.apache.org/jira/browse/MPLUGIN-521
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.12.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.12.1
>
>
> Details:
> https://github.com/apache/maven-site-plugin/pull/177#pullrequestreview-2033188399
> If you have a type like {{Map>}} the generator will extract
> {{List}} instead of just {{Foo}}. We should recursively go down to the
> type.
> This is likely an edge case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSITE-1003) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSITE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSITE-1003. - Resolution: Fixed Fixed with [1bbad2d356a4ede8ebbe3a523533b660d66d9b58|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=1bbad2d356a4ede8ebbe3a523533b660d66d9b58]. > Upgrade plugins and components (in ITs) > --- > > Key: MSITE-1003 > URL: https://issues.apache.org/jira/browse/MSITE-1003 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 > * Upgrade to Maven Reporting Exec 4.0.0-M13 > * Upgrade to Maven Plugin Tools 3.12.0 > * Upgrade to Commons IO 2.16.1 > * Upgrade to Jetty 9.4.54.v20240208 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPLUGIN-521) Nested types not properly extracted cause exception while generating Javadoc URLs
Michael Osipov created MPLUGIN-521:
--
Summary: Nested types not properly extracted cause exception while
generating Javadoc URLs
Key: MPLUGIN-521
URL: https://issues.apache.org/jira/browse/MPLUGIN-521
Project: Maven Plugin Tools
Issue Type: Bug
Components: Plugin Plugin
Affects Versions: 3.12.0
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.12.1
Details:
https://github.com/apache/maven-site-plugin/pull/177#pullrequestreview-2033188399
If you have a type like {{Map>}} the generator will extract
{{List}} instead of just {{Foo}}. We should recursively go down to the
type.
This is likely an edge case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8111) Version 3.9.6 is not reproducible
[
https://issues.apache.org/jira/browse/MNG-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-8111.
---
Resolution: Information Provided
> Version 3.9.6 is not reproducible
> -
>
> Key: MNG-8111
> URL: https://issues.apache.org/jira/browse/MNG-8111
> Project: Maven
> Issue Type: Bug
> Components: Core, General
>Affects Versions: 3.9.6
> Environment: Arch Linux updated (29/04/2024)
>Reporter: Leonidas Spyropoulos
>Priority: Major
> Labels: reproducibility
> Attachments: maven-3.9.6-1-x86_64-build.log
>
>
> Version 3.9.6 is not reproducible. It seems like the compiled classes are
> different.
> - JDK used: OpenJDK version 8.412.u08
> - Command line used:
> {code:bash}
> mvn package \
> -DbuildNumber="bc0240f3c744dd6b6ec2920b3cd08dcc295161ae" \
> -Dline.separator=$'\r\n' \
> -Dproject.build.sourceEncoding=UTF-8 -e \
> -Dmaven.repo.local="./repo" \
> -DskipTests
> {code}
> buildNumber is found from:
> {code}
> bsdtar xOf <(bsdtar xOf apache-maven-3.9.6-bin.tar.gz
> apache-maven-3.9.6/lib/maven-core-3.9.6.jar) \
> org/apache/maven/messages/build.properties | grep buildNumber | cut -d=
> -f2 | tr -cd '[:print:]'
> {code}
> Relevant issue: https://issues.apache.org/jira/browse/MNG-6276
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSITE-1003) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSITE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSITE-1003: -- Description: * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Reporting Exec 4.0.0-M13 * Upgrade to Maven Plugin Tools 3.12.0 * Upgrade to Commons IO 2.16.1 * Upgrade to Jetty 9.4.54.v20240208 was: * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Reporting Exec 4.0.0-M13 * Upgrade to Maven Plugin Tools 3.12.0 > Upgrade plugins and components (in ITs) > --- > > Key: MSITE-1003 > URL: https://issues.apache.org/jira/browse/MSITE-1003 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 > * Upgrade to Maven Reporting Exec 4.0.0-M13 > * Upgrade to Maven Plugin Tools 3.12.0 > * Upgrade to Commons IO 2.16.1 > * Upgrade to Jetty 9.4.54.v20240208 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSITE-1003) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSITE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSITE-1003: -- Description: * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Reporting Exec 4.0.0-M13 * Upgrade to Maven Plugin Tools 3.12.0 was: * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Reporting Exec 4.0.0-M13 * Upgrade to Maven Plugin Tools 3.12.0 * Upgrade to Maven JXR Plugin 3.3.2 > Upgrade plugins and components (in ITs) > --- > > Key: MSITE-1003 > URL: https://issues.apache.org/jira/browse/MSITE-1003 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 > * Upgrade to Maven Reporting Exec 4.0.0-M13 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8111) Version 3.9.6 is not reproducible
[
https://issues.apache.org/jira/browse/MNG-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842259#comment-17842259
]
Michael Osipov commented on MNG-8111:
-
[~artafinde], what does diffoscope say?
> Version 3.9.6 is not reproducible
> -
>
> Key: MNG-8111
> URL: https://issues.apache.org/jira/browse/MNG-8111
> Project: Maven
> Issue Type: Bug
> Components: Core, General
>Affects Versions: 3.9.6
> Environment: Arch Linux updated (29/04/2024)
>Reporter: Leonidas Spyropoulos
>Priority: Major
> Labels: reproducibility
>
> Version 3.9.6 is not reproducible. It seems like the compiled classes are
> different.
> - JDK used: OpenJDK version 8.412.u08
> - Command line used:
> {code:bash}
> mvn package \
> -DbuildNumber="bc0240f3c744dd6b6ec2920b3cd08dcc295161ae" \
> -Dline.separator=$'\r\n' \
> -Dproject.build.sourceEncoding=UTF-8 -e \
> -Dmaven.repo.local="./repo" \
> -DskipTests
> {code}
> buildNumber is found from:
> {code}
> bsdtar xOf <(bsdtar xOf apache-maven-3.9.6-bin.tar.gz
> apache-maven-3.9.6/lib/maven-core-3.9.6.jar) \
> org/apache/maven/messages/build.properties | grep buildNumber | cut -d=
> -f2 | tr -cd '[:print:]'
> {code}
> Relevant issue: https://issues.apache.org/jira/browse/MNG-6276
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (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 closed MSHARED-1362. --- Resolution: Fixed Fixed with [55262efc9800e0b874b50f0c2e222b08db4208a5|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git=commit=55262efc9800e0b874b50f0c2e222b08db4208a5]. > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1362 > URL: https://issues.apache.org/jira/browse/MSHARED-1362 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > > * Upgrade to Maven Site Plugin 4.0.0-M13 > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 was: * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Plugin Tools 3.12.0 > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1362 > URL: https://issues.apache.org/jira/browse/MSHARED-1362 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > > * Upgrade to Maven Site Plugin 4.0.0-M13 > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1387) Clean up dependencies
[ https://issues.apache.org/jira/browse/MSHARED-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1387. --- Resolution: Fixed Fixed with [a087b1e0770d3fbf844d473842d533c4fe97bf18|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git=commit=a087b1e0770d3fbf844d473842d533c4fe97bf18]. > Clean up dependencies > - > > Key: MSHARED-1387 > URL: https://issues.apache.org/jira/browse/MSHARED-1387 > Project: Maven Shared Components > Issue Type: Task > Components: maven-reporting-exec >Affects Versions: maven-reporting-exec-2.0.0-M12 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1387) Clean up dependencies
Michael Osipov created MSHARED-1387: --- Summary: Clean up dependencies Key: MSHARED-1387 URL: https://issues.apache.org/jira/browse/MSHARED-1387 Project: Maven Shared Components Issue Type: Task Components: maven-reporting-exec Affects Versions: maven-reporting-exec-2.0.0-M12 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-exec-2.0.0, maven-reporting-exec-2.0.0-M13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-337) Move maven-compat to test scope
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-337: -- Fix Version/s: 2.0.0-M19 > Move maven-compat to test scope > --- > > Key: DOXIASITETOOLS-337 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-337 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade > Components: Integration Tools >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-M19 > > > As maven-compat is not runtime/transitive dependency, is used in tests only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-337) Move maven-compat to test scope
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-337: -- Fix Version/s: (was: 2.0.0-M18) > Move maven-compat to test scope > --- > > Key: DOXIASITETOOLS-337 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-337 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade > Components: Integration Tools >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > As maven-compat is not runtime/transitive dependency, is used in tests only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-337) Move maven-compat to test scope
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-337: -- Fix Version/s: 2.0.0-M18 > Move maven-compat to test scope > --- > > Key: DOXIASITETOOLS-337 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-337 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade > Components: Integration Tools >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-M18 > > > As maven-compat is not runtime/transitive dependency, is used in tests only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (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 closed MSHARED-1361. --- Resolution: Fixed Fixed with [153df38982c10061eb8d004066bb2d521f8cc608|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=153df38982c10061eb8d004066bb2d521f8cc608]. > Upgrade plugins and components (in ITs) (2) > --- > > Key: MSHARED-1361 > URL: https://issues.apache.org/jira/browse/MSHARED-1361 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0, > maven-reporting-impl-4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSITE-1003) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSITE-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSITE-1003: -- Description: * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Reporting Exec 4.0.0-M13 * Upgrade to Maven Plugin Tools 3.12.0 * Upgrade to Maven JXR Plugin 3.3.2 was: * Upgrade to Doxia 2.0.0-M9 * Upgrade to Doxia Sitetools 2.0.0-M17 * Upgrade to Maven Reporting API 4.0.0-M10 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Reporting Exec 4.0.0-M13 * Upgrade to Maven Plugin Tools 3.11.0 * Upgrade to Maven JXR Plugin 3.3.2 > Upgrade plugins and components (in ITs) > --- > > Key: MSITE-1003 > URL: https://issues.apache.org/jira/browse/MSITE-1003 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0, 4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 > * Upgrade to Maven Reporting Exec 4.0.0-M13 > * Upgrade to Maven Plugin Tools 3.12.0 > * Upgrade to Maven JXR Plugin 3.3.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Plugin Tools 3.12.0 was: * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M19 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M15 * Upgrade to Maven Plugin Tools 3.12.0 > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1362 > URL: https://issues.apache.org/jira/browse/MSHARED-1362 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > > * Upgrade to Maven Site Plugin 4.0.0-M13 > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M14 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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-M11 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Plugin Tools 3.12.0 was: * Upgrade to Doxia 2.0.0-M10 * Upgrade to Doxia Sitetools 2.0.0-M19 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Plugin Tools 3.12.0 > Upgrade plugins and components (in ITs) (2) > --- > > Key: MSHARED-1361 > URL: https://issues.apache.org/jira/browse/MSHARED-1361 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0, > maven-reporting-impl-4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M11 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Plugin Tools 3.12.0 was: * Upgrade to Doxia 2.0.0-M11 * Upgrade to Doxia Sitetools 2.0.0-M18 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Plugin Tools 3.12.0 > Upgrade plugins and components (in ITs) (2) > --- > > Key: MSHARED-1361 > URL: https://issues.apache.org/jira/browse/MSHARED-1361 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0, > maven-reporting-impl-4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIA-730) Update Asciidoctor Doxia Modules in doxia-site
[ https://issues.apache.org/jira/browse/DOXIA-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIA-730: - Component/s: Documentation > Update Asciidoctor Doxia Modules in doxia-site > -- > > Key: DOXIA-730 > URL: https://issues.apache.org/jira/browse/DOXIA-730 > Project: Maven Doxia > Issue Type: Improvement > Components: Documentation >Reporter: Abel Salgado Romero >Assignee: Sylwester Lachiewicz >Priority: Major > > In v3.0.0, we renamed the current module and created a new one. > I am working on a PR to update the page > https://maven.apache.org/doxia/references/index.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIA-730) Update Asciidoctor Doxia Modules in doxia-site
[ https://issues.apache.org/jira/browse/DOXIA-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIA-730: - Fix Version/s: (was: 2.0.0) (was: 2.0.0-M10) > Update Asciidoctor Doxia Modules in doxia-site > -- > > Key: DOXIA-730 > URL: https://issues.apache.org/jira/browse/DOXIA-730 > Project: Maven Doxia > Issue Type: Improvement >Reporter: Abel Salgado Romero >Assignee: Sylwester Lachiewicz >Priority: Major > > In v3.0.0, we renamed the current module and created a new one. > I am working on a PR to update the page > https://maven.apache.org/doxia/references/index.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-336) Make SiteRenderingContext#siteDirectories editable aware
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-336.
-
Resolution: Fixed
Fixed with
[f76b6608ef1084cb125a8ab5e351af8f7022c92a|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=f76b6608ef1084cb125a8ab5e351af8f7022c92a].
> Make SiteRenderingContext#siteDirectories editable aware
>
>
> Key: DOXIASITETOOLS-336
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-336
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Affects Versions: 2.0.0-M16
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M18
>
>
> Right now you cannot qualify a {{siteDirectory}} whether the content is
> editable or generated. You need to perform multiple calls with distinct
> {{SiteRenderingContexts}}. This causes computational overhead is hacks like
> MSITE-723.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHARED-1382) Maven-invoker: support '--no-snapshot-updates'
[
https://issues.apache.org/jira/browse/MSHARED-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839058#comment-17839058
]
Michael Osipov commented on MSHARED-1382:
-
Will happily review a PR with [~sjaranowski].
> Maven-invoker: support '--no-snapshot-updates'
> --
>
> Key: MSHARED-1382
> URL: https://issues.apache.org/jira/browse/MSHARED-1382
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-invoker
>Affects Versions: maven-invoker-3.2.0
>Reporter: Leonid Rozenblyum
>Priority: Major
>
> Let's add support for *{{--no-snapshot-updates}}* in
> *{{org.apache.maven.shared.invoker.InvocationRequest}}*
>
> Currently *{{InvocationRequest}}* supports just the *{{-U}}* *mvn* option
> which is not enough: it's possible to force the snapshots update or keep
> default maven policy on this.
>
> But it's not possible to prevent snapshots updates which is highly desired
> under some circumstances (e.g. for CI reproducibility).
>
> NOTE: I may contribute a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (DOXIASITETOOLS-336) Make SiteRenderingContext#siteDirectories editable aware
Michael Osipov created DOXIASITETOOLS-336:
-
Summary: Make SiteRenderingContext#siteDirectories editable aware
Key: DOXIASITETOOLS-336
URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-336
Project: Maven Doxia Sitetools
Issue Type: Improvement
Components: Site renderer
Affects Versions: 2.0.0-M16
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 2.0.0, 2.0.0-M18
Right now you cannot qualify a {{siteDirectory}} whether the content is
editable or generated. You need to perform multiple calls with distinct
{{SiteRenderingContexts}}. This causes computational overhead is hacks like
MSITE-723.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-1006) MSITE-723 causes duplicate document rendering and log output
[
https://issues.apache.org/jira/browse/MSITE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838193#comment-17838193
]
Michael Osipov commented on MSITE-1006:
---
Don't confuse reports with generated documents. There is no issue with reports
vs. documents, but solely generated documents. Currently they override reports
and editable documents, but that his implemented ugly.
> MSITE-723 causes duplicate document rendering and log output
>
>
> Key: MSITE-1006
> URL: https://issues.apache.org/jira/browse/MSITE-1006
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: doxia integration
>Affects Versions: 4.0.0-M13
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M14
>
>
> Consider the following output:
> {noformat}
> ...
> [INFO] --- maven-site-plugin:3.12.1:site (default-site) @ doxia-skin-model ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.5
> [INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.5:
> index, summary, dependency-info, modules, team, scm, issue-management,
> mailing-lists, dependency-management, dependencies, dependency-convergence,
> ci-management, plugin-management, plugins, distribution-management
> [INFO] Rendering site with default locale English (en)
> [INFO] Relativizing decoration links with respect to localized project URL:
> https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
> [INFO] Rendering content with
> org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin.
> [INFO] Skipped "About" report
> (maven-project-info-reports-plugin:3.4.5:index), file "index.html" already
> exists.
> [INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:3.4.5:summary
> [INFO] Generating "Dependency Information" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-info
> [INFO] Generating "Team" report ---
> maven-project-info-reports-plugin:3.4.5:team
> [INFO] Generating "Source Code Management" report ---
> maven-project-info-reports-plugin:3.4.5:scm
> [INFO] Generating "Issue Management" report ---
> maven-project-info-reports-plugin:3.4.5:issue-management
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:3.4.5:mailing-lists
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-management
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:3.4.5:dependencies
> [INFO] Generating "Dependency Convergence" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-convergence
> [INFO] Generating "CI Management" report---
> maven-project-info-reports-plugin:3.4.5:ci-management
> [INFO] Generating "Plugin Management" report---
> maven-project-info-reports-plugin:3.4.5:plugin-management
> [INFO] Generating "Plugins" report ---
> maven-project-info-reports-plugin:3.4.5:plugins
> [INFO] Generating "Distribution Management" report ---
> maven-project-info-reports-plugin:3.4.5:distribution-management
> [INFO] Rendering 1 generated Doxia document: 1 xdoc
> ...
> {noformat}
> Let's locate these two handwritten documents:
> {noformat}
> ~/var/Projekte/maven-doxia-sitetools (master =)
> $ tree doxia-skin-model/src/site/
> doxia-skin-model/src/site/
> ├── apt
> │ └── index.apt
> └── site.xml
> 2 directories, 2 files
> {noformat}
> There aren't. This is caused by MSITE-723 which add generated documents for
> the first round of rendering (non-editable ones), then does the rendering,
> does reports and then allows generated documents to overwrite report output
> by running generated rendering again.
> This is suboptimal since it causes:
> * Duplicate rendering
> * Deceiving log output
> * Maven Fluido Skin generates an "Edit Button" for such content sind the
> editable flag is set to true:
> view-source:https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-2.0.0-M16/doxia-skin-model/skin.html
> The solution to the problem is to flag the document renderer for such output
> with Sitetools to allow unconditional overwrite. We need to fix Doxia
> Sitetools first and then we can fix in this plugin.
> Block in question:
> https://github.com/apache/maven-site-plugin/blob/036997f9a70b7394d9a9771ede04a686aca834e1/src/main/java/org/apache/maven/plugins/site/render/SiteMojo.java#L123-L167
> This needs to be {{true}}:
> https://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/xref/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.html#L61
--
This message was sent by Atlassian Jira
[jira] [Comment Edited] (MSITE-1006) MSITE-723 causes duplicate document rendering and log output
[
https://issues.apache.org/jira/browse/MSITE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838047#comment-17838047
]
Michael Osipov edited comment on MSITE-1006 at 4/17/24 9:14 AM:
Some design questions before I implement the fix:
* Can we always assume that non-editable documents come last and can overwrite
everything from before?
* Can we always assume that non-editable documents are generated?
* Should this be controlable via parameter?
[~kwin], [~hboutemy], opinions?
Cheapest solution:
{noformat}
$ git stash show -p
diff --git
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
index a436c94..92b4390 100644
---
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
+++
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
@@ -58,7 +58,7 @@ public class DoxiaDocumentRenderer implements
DocumentRenderer {
/** {@inheritDoc} */
public boolean isOverwrite() {
-return false;
+return !docRenderingContext.isEditable();
}
public boolean isExternalReport() {
{noformat}
was (Author: michael-o):
Some design questions before I implement the fix:
* Can we always assume that non-editable documents come last and can overwrite
everything from before?
* Should this be controlable via parameter?
[~kwin], [~hboutemy], opinions?
Cheapest solution:
{noformat}
$ git stash show -p
diff --git
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
index a436c94..92b4390 100644
---
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
+++
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
@@ -58,7 +58,7 @@ public class DoxiaDocumentRenderer implements
DocumentRenderer {
/** {@inheritDoc} */
public boolean isOverwrite() {
-return false;
+return !docRenderingContext.isEditable();
}
public boolean isExternalReport() {
{noformat}
> MSITE-723 causes duplicate document rendering and log output
>
>
> Key: MSITE-1006
> URL: https://issues.apache.org/jira/browse/MSITE-1006
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: doxia integration
>Affects Versions: 4.0.0-M13
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M14
>
>
> Consider the following output:
> {noformat}
> ...
> [INFO] --- maven-site-plugin:3.12.1:site (default-site) @ doxia-skin-model ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.5
> [INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.5:
> index, summary, dependency-info, modules, team, scm, issue-management,
> mailing-lists, dependency-management, dependencies, dependency-convergence,
> ci-management, plugin-management, plugins, distribution-management
> [INFO] Rendering site with default locale English (en)
> [INFO] Relativizing decoration links with respect to localized project URL:
> https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
> [INFO] Rendering content with
> org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin.
> [INFO] Skipped "About" report
> (maven-project-info-reports-plugin:3.4.5:index), file "index.html" already
> exists.
> [INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:3.4.5:summary
> [INFO] Generating "Dependency Information" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-info
> [INFO] Generating "Team" report ---
> maven-project-info-reports-plugin:3.4.5:team
> [INFO] Generating "Source Code Management" report ---
> maven-project-info-reports-plugin:3.4.5:scm
> [INFO] Generating "Issue Management" report ---
> maven-project-info-reports-plugin:3.4.5:issue-management
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:3.4.5:mailing-lists
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-management
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:3.4.5:dependencies
> [INFO] Generating "Dependency Convergence" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-convergence
> [INFO] Generating "CI Management" report---
>
[jira] [Commented] (MSITE-1006) MSITE-723 causes duplicate document rendering and log output
[
https://issues.apache.org/jira/browse/MSITE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838047#comment-17838047
]
Michael Osipov commented on MSITE-1006:
---
Some design questions before I implement the fix:
* Can we always assume that non-editable documents come last and can overwrite
everything from before?
* Should this be controlable via parameter?
[~kwin], [~hboutemy], opinions?
Cheapest solution:
{noformat}
$ git stash show -p
diff --git
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
index a436c94..92b4390 100644
---
a/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
+++
b/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.java
@@ -58,7 +58,7 @@ public class DoxiaDocumentRenderer implements
DocumentRenderer {
/** {@inheritDoc} */
public boolean isOverwrite() {
-return false;
+return !docRenderingContext.isEditable();
}
public boolean isExternalReport() {
{noformat}
> MSITE-723 causes duplicate document rendering and log output
>
>
> Key: MSITE-1006
> URL: https://issues.apache.org/jira/browse/MSITE-1006
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: doxia integration
>Affects Versions: 4.0.0-M13
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0, 4.0.0-M14
>
>
> Consider the following output:
> {noformat}
> ...
> [INFO] --- maven-site-plugin:3.12.1:site (default-site) @ doxia-skin-model ---
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.5
> [INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.5:
> index, summary, dependency-info, modules, team, scm, issue-management,
> mailing-lists, dependency-management, dependencies, dependency-convergence,
> ci-management, plugin-management, plugins, distribution-management
> [INFO] Rendering site with default locale English (en)
> [INFO] Relativizing decoration links with respect to localized project URL:
> https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
> [INFO] Rendering content with
> org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin.
> [INFO] Skipped "About" report
> (maven-project-info-reports-plugin:3.4.5:index), file "index.html" already
> exists.
> [INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:3.4.5:summary
> [INFO] Generating "Dependency Information" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-info
> [INFO] Generating "Team" report ---
> maven-project-info-reports-plugin:3.4.5:team
> [INFO] Generating "Source Code Management" report ---
> maven-project-info-reports-plugin:3.4.5:scm
> [INFO] Generating "Issue Management" report ---
> maven-project-info-reports-plugin:3.4.5:issue-management
> [INFO] Generating "Mailing Lists" report---
> maven-project-info-reports-plugin:3.4.5:mailing-lists
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-management
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:3.4.5:dependencies
> [INFO] Generating "Dependency Convergence" report ---
> maven-project-info-reports-plugin:3.4.5:dependency-convergence
> [INFO] Generating "CI Management" report---
> maven-project-info-reports-plugin:3.4.5:ci-management
> [INFO] Generating "Plugin Management" report---
> maven-project-info-reports-plugin:3.4.5:plugin-management
> [INFO] Generating "Plugins" report ---
> maven-project-info-reports-plugin:3.4.5:plugins
> [INFO] Generating "Distribution Management" report ---
> maven-project-info-reports-plugin:3.4.5:distribution-management
> [INFO] Rendering 1 generated Doxia document: 1 xdoc
> ...
> {noformat}
> Let's locate these two handwritten documents:
> {noformat}
> ~/var/Projekte/maven-doxia-sitetools (master =)
> $ tree doxia-skin-model/src/site/
> doxia-skin-model/src/site/
> ├── apt
> │ └── index.apt
> └── site.xml
> 2 directories, 2 files
> {noformat}
> There aren't. This is caused by MSITE-723 which add generated documents for
> the first round of rendering (non-editable ones), then does the rendering,
> does reports and then allows generated documents to overwrite report output
> by running generated rendering again.
> This is suboptimal since it causes:
> * Duplicate rendering
> * Deceiving log output
> * Maven Fluido Skin generates an "Edit Button" for such
[jira] [Updated] (MSITE-1006) MSITE-723 causes duplicate document rendering and log output
[
https://issues.apache.org/jira/browse/MSITE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSITE-1006:
--
Description:
Consider the following output:
{noformat}
...
[INFO] --- maven-site-plugin:3.12.1:site (default-site) @ doxia-skin-model ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.5
[INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.5:
index, summary, dependency-info, modules, team, scm, issue-management,
mailing-lists, dependency-management, dependencies, dependency-convergence,
ci-management, plugin-management, plugins, distribution-management
[INFO] Rendering site with default locale English (en)
[INFO] Relativizing decoration links with respect to localized project URL:
https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
[INFO] Rendering content with
org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:3.4.5:index),
file "index.html" already exists.
[INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc
[INFO] Generating "Summary" report ---
maven-project-info-reports-plugin:3.4.5:summary
[INFO] Generating "Dependency Information" report ---
maven-project-info-reports-plugin:3.4.5:dependency-info
[INFO] Generating "Team" report ---
maven-project-info-reports-plugin:3.4.5:team
[INFO] Generating "Source Code Management" report ---
maven-project-info-reports-plugin:3.4.5:scm
[INFO] Generating "Issue Management" report ---
maven-project-info-reports-plugin:3.4.5:issue-management
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:3.4.5:mailing-lists
[INFO] Generating "Dependency Management" report ---
maven-project-info-reports-plugin:3.4.5:dependency-management
[INFO] Generating "Dependencies" report ---
maven-project-info-reports-plugin:3.4.5:dependencies
[INFO] Generating "Dependency Convergence" report ---
maven-project-info-reports-plugin:3.4.5:dependency-convergence
[INFO] Generating "CI Management" report---
maven-project-info-reports-plugin:3.4.5:ci-management
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:3.4.5:plugin-management
[INFO] Generating "Plugins" report ---
maven-project-info-reports-plugin:3.4.5:plugins
[INFO] Generating "Distribution Management" report ---
maven-project-info-reports-plugin:3.4.5:distribution-management
[INFO] Rendering 1 generated Doxia document: 1 xdoc
...
{noformat}
Let's locate these two handwritten documents:
{noformat}
~/var/Projekte/maven-doxia-sitetools (master =)
$ tree doxia-skin-model/src/site/
doxia-skin-model/src/site/
├── apt
│ └── index.apt
└── site.xml
2 directories, 2 files
{noformat}
There aren't. This is caused by MSITE-723 which add generated documents for the
first round of rendering (non-editable ones), then does the rendering, does
reports and then allows generated documents to overwrite report output by
running generated rendering again.
This is suboptimal since it causes:
* Duplicate rendering
* Deceiving log output
* Maven Fluido Skin generates an "Edit Button" for such content sind the
editable flag is set to true:
view-source:https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-2.0.0-M16/doxia-skin-model/skin.html
The solution to the problem is to flag the document renderer for such output
with Sitetools to allow unconditional overwrite. We need to fix Doxia Sitetools
first and then we can fix in this plugin.
Block in question:
https://github.com/apache/maven-site-plugin/blob/036997f9a70b7394d9a9771ede04a686aca834e1/src/main/java/org/apache/maven/plugins/site/render/SiteMojo.java#L123-L167
This needs to be {{true}}:
https://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/xref/org/apache/maven/doxia/siterenderer/DoxiaDocumentRenderer.html#L61
was:
Consider the following output:
{noformat}
...
[INFO] --- maven-site-plugin:3.12.1:site (default-site) @ doxia-skin-model ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.5
[INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.5:
index, summary, dependency-info, modules, team, scm, issue-management,
mailing-lists, dependency-management, dependencies, dependency-convergence,
ci-management, plugin-management, plugins, distribution-management
[INFO] Rendering site with default locale English (en)
[INFO] Relativizing decoration links with respect to localized project URL:
https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
[INFO] Rendering content with
org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:3.4.5:index),
file "index.html" already exists.
[INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc
[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 Plugin
Issue Type: Bug
Components: doxia integration
Affects Versions: 4.0.0-M13
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 4.0.0, 4.0.0-M14
Consider the following output:
{noformat}
...
[INFO] --- maven-site-plugin:3.12.1:site (default-site) @ doxia-skin-model ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:3.4.5
[INFO] 15 reports configured for maven-project-info-reports-plugin:3.4.5:
index, summary, dependency-info, modules, team, scm, issue-management,
mailing-lists, dependency-management, dependencies, dependency-convergence,
ci-management, plugin-management, plugins, distribution-management
[INFO] Rendering site with default locale English (en)
[INFO] Relativizing decoration links with respect to localized project URL:
https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
[INFO] Rendering content with
org.apache.maven.skins:maven-fluido-skin:jar:1.11.2 skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:3.4.5:index),
file "index.html" already exists.
[INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc
[INFO] Generating "Summary" report ---
maven-project-info-reports-plugin:3.4.5:summary
[INFO] Generating "Dependency Information" report ---
maven-project-info-reports-plugin:3.4.5:dependency-info
[INFO] Generating "Team" report ---
maven-project-info-reports-plugin:3.4.5:team
[INFO] Generating "Source Code Management" report ---
maven-project-info-reports-plugin:3.4.5:scm
[INFO] Generating "Issue Management" report ---
maven-project-info-reports-plugin:3.4.5:issue-management
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:3.4.5:mailing-lists
[INFO] Generating "Dependency Management" report ---
maven-project-info-reports-plugin:3.4.5:dependency-management
[INFO] Generating "Dependencies" report ---
maven-project-info-reports-plugin:3.4.5:dependencies
[INFO] Generating "Dependency Convergence" report ---
maven-project-info-reports-plugin:3.4.5:dependency-convergence
[INFO] Generating "CI Management" report---
maven-project-info-reports-plugin:3.4.5:ci-management
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:3.4.5:plugin-management
[INFO] Generating "Plugins" report ---
maven-project-info-reports-plugin:3.4.5:plugins
[INFO] Generating "Distribution Management" report ---
maven-project-info-reports-plugin:3.4.5:distribution-management
[INFO] Rendering 1 generated Doxia document: 1 xdoc
...
{noformat}
Let's locate these two handwritten documents:
{noformat}
~/var/Projekte/maven-doxia-sitetools (master =)
$ tree doxia-skin-model/src/site/
doxia-skin-model/src/site/
├── apt
│ └── index.apt
└── site.xml
2 directories, 2 files
{noformat}
There aren't. This is caused by MSITE-723 which add generated documents for the
first round of rendering (non-editable ones), then does the rendering, does
reports and then allows generated documents to overwrite report output by
running generated rendering again.
This is suboptimal since it causes:
* Duplicate rendering
* Deceiving log output
* Maven Fluido Skin generates an "Edit Button" for such content sind the
editable flag is set to true:
view-source:https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-2.0.0-M16/doxia-skin-model/skin.html
The solution to the problem is to flag the document renderer for such output
with Sitetools to allow unconditional overwrite. We need to fix Doxia Sitetools
first and then we can fix in this plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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 > -- > > Key: DOXIASITETOOLS-335 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-335 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M18 > > > This also includes: > * Upgrade to Maven Reporting API 4.0.0-M11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 [3d2a29353dd6da8b79bddafe290e6e22982964f6|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=3d2a29353dd6da8b79bddafe290e6e22982964f6]. > Upgrade to Doxia 2.0.0-M10 > -- > > Key: DOXIASITETOOLS-335 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-335 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M18 > > > This also includes: > * Upgrade to Maven Reporting API 4.0.0-M11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 Plexus Testing 1.3.0 * Upgrade to Plexus Velocity 2.1.0 * Upgrade to Commons Lang 3.14.0 * Upgrade to Commons IO 2.15.1 * Upgrade to JUnit 5.10.1 * Upgrade to Plexus Classworlds 2.8.0 was: * Upgrade to Plexus Interpolation 1.27 * Upgrade to Plexus Testing 1.3.0 * Upgrade to Plexus Velocity 2.1.0 * Upgrade to Commons Lang 3.14.0 * Upgrade to Commons IO 2.15.1 * Upgrade to JUnit 5.10.1 > Upgrade components > -- > > Key: DOXIASITETOOLS-323 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-323 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0, 2.0.0-M17, 2.0.0-M18 > > > * Upgrade to Plexus Interpolation 1.27 > * Upgrade to Plexus Testing 1.3.0 > * Upgrade to Plexus Velocity 2.1.0 > * Upgrade to Commons Lang 3.14.0 > * Upgrade to Commons IO 2.15.1 > * Upgrade to JUnit 5.10.1 > * Upgrade to Plexus Classworlds 2.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 3.9) > Upgrade htmlunit 2.x to 4.0.0 > - > > Key: DOXIASITETOOLS-321 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-321 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 2.0.0, 2.0.0-M17, 2.0.0-M18 > > > https://github.com/advisories/GHSA-3xrr-7m6p-p7xh -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 commons-io:commons-io to 2.16.0) > Upgrade commons-io:commons-io to 2.16.1 > --- > > Key: DOXIASITETOOLS-333 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-333 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 2.0.0, 2.0.0-M18 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 Sitetools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0-M18 This also includes: * Upgrade to Maven Reporting API 4.0.0-M11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 * Upgrade to Doxia Sitetools 2.0.0-M19 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Reporting Impl 4.0.0-M15 * Upgrade to Maven Plugin Tools 3.12.0 was: * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Doxia 2.0.0-M9 * Upgrade to Doxia Sitetools 2.0.0-M17 * Upgrade to Maven Reporting API 4.0.0-M10 * Upgrade to Maven Reporting Impl 4.0.0-M14 * Upgrade to Maven Plugin Tools 3.11.0 > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1362 > URL: https://issues.apache.org/jira/browse/MSHARED-1362 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0, > maven-reporting-exec-2.0.0-M13 > > > * Upgrade to Maven Site Plugin 4.0.0-M13 > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M19 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Reporting Impl 4.0.0-M15 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 * Upgrade to Maven Reporting API 4.0.0-M11 * Upgrade to Maven Plugin Tools 3.12.0 was: * Upgrade to Doxia 2.0.0-M9 * Upgrade to Doxia Sitetools 2.0.0-M17 * Upgrade to Maven Reporting API 4.0.0-M10 * Upgrade to Maven Plugin Tools 3.11.0 > Upgrade plugins and components (in ITs) (2) > --- > > Key: MSHARED-1361 > URL: https://issues.apache.org/jira/browse/MSHARED-1361 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0, > maven-reporting-impl-4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M19 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 [c60211df4f36d794414673ca62a5ea30e5f056ab|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=c60211df4f36d794414673ca62a5ea30e5f056ab]. > Upgrade to Doxia 2.0.0-M10 > -- > > Key: MSHARED-1379 > URL: https://issues.apache.org/jira/browse/MSHARED-1379 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M11 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 > -- > > Key: MSHARED-1379 > URL: https://issues.apache.org/jira/browse/MSHARED-1379 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 > -- > > Key: MSHARED-1379 > URL: https://issues.apache.org/jira/browse/MSHARED-1379 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-api >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M11 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 Type: Dependency upgrade Components: maven-reporting-api Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-api-4.0.0, maven-reporting-api-4.0.0-M10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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(...)
> -
>
> Key: DOXIA-731
> URL: https://issues.apache.org/jira/browse/DOXIA-731
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Core
>Affects Versions: 2.0.0-M9
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M10
>
>
> The XHTML markup generated from Sink.verbatim(...) should be streamlined to
> either emit {{}} or {{}} depending on the given attribute.
> There is no need to generate an additional div nor any additional classes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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: DOXIA-728 > URL: https://issues.apache.org/jira/browse/DOXIA-728 > Project: Maven Doxia > Issue Type: Improvement >Affects Versions: 2.0.0-M9 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 2.0.0-M10 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 XdocParser/FmlParser
> -
>
> Key: DOXIA-734
> URL: https://issues.apache.org/jira/browse/DOXIA-734
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Apt, Module - Fml
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M10
>
>
> Currently only {{}} is translated into a proper
> {{Sink.anchor(...)}} call.
> The obsolete {{}} is currently not calling an according
> {{Sink.anchor(...)}} method but may be still used in ancient markups which
> derive from the XHtml5BaseParser.
> For example XDoc and FML both stem from the time where
> https://www.w3.org/TR/xhtml1/ was the most recent XHTML spec and therefore
> support {{a name}} (according to
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-xdoc/xsddoc/http___maven.apache.org_XDOC_2.0/element/a.html
> and
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-fml/xsddoc/http___maven.apache.org_FML_1.0.1/element/a.html)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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
>
>
> Key: DOXIA-724
> URL: https://issues.apache.org/jira/browse/DOXIA-724
> Project: Maven Doxia
> Issue Type: Bug
>Affects Versions: 2.0.0-M9
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M10
>
>
> According to the javadoc the SinkWrapperFactory should be ordered according
> to their priority from highest to lowest. However in
> {{AbstractParser.getWrappedSink()}} a pipeline is returned which has no
> predictable order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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 > --- > > Key: DOXIA-723 > URL: https://issues.apache.org/jira/browse/DOXIA-723 > Project: Maven Doxia > Issue Type: Improvement > Components: Sink API >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 2.0.0, 2.0.0-M10 > > > Similar to http://www.saxproject.org/apidoc/org/xml/sax/Locator.html the Sink > API should provide means to figure out the document location. This should be > available whenever the Sink events are emitted from parsing a file. > The locator should expose file name, line number and column number. > This can be used to enhance warning/errors as otherwise it is very hard to > figure out the root cause of messages like > https://github.com/apache/maven-doxia/blob/e01880801ca1283b86205e2f7064b9b4dbc84d54/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java#L930. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 &
> -
>
> Key: DOXIA-726
> URL: https://issues.apache.org/jira/browse/DOXIA-726
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Markdown
>Affects Versions: 2.0.0-M9
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M10
>
>
> As Markdown emits all unknown characters "as-is" in the resulting HTML also
> all XML escape characters need to be leveraged in addition to the ones
> outlined in https://daringfireball.net/projects/markdown/syntax#backslash in
> {{Sink.text(...)}}. Currently only the latter is considered though which
> leads to incorrect output: The text value
> {code}
> "this is a "
> {code}
> should lead to
> {code}
> "this is a test"
> {code}
> but right now the "<" and ">" are not escaped.
> Compare also with
> https://spec.commonmark.org/0.30/#entity-and-numeric-character-references.
> It needs to be ensured that all parsed XHTML elements which are not natively
> supported by the Sink API (i.e. don't lead to a dedicated event) are passed
> as is to the output (given the input is XHTML).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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
> --
>
> Key: DOXIA-732
> URL: https://issues.apache.org/jira/browse/DOXIA-732
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Core
>Affects Versions: 2.0.0-M9
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M10
>
>
> The {{UniqueAnchorNamesValidator}} added with DOXIA-722 fails with an ISE in
> case duplicate anchor names are found on a page
> (https://github.com/apache/maven-doxia/blob/7a04c033456511e1bd4870f03ba768d03158f368/doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/UniqueAnchorNamesValidator.java#L49).
> As this only has a functional impact for links using the anchors the default
> behaviour should rather be a WARNING in the log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
