[
https://issues.apache.org/jira/browse/MNG-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626462#comment-17626462
]
Maarten Mulders commented on MNG-7564:
--
{quote}This likely also applies to 3.9.0.{quot
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-268:
--
Issue Type: Improvement (was: Bug)
> Don't open version resource file
asfgit closed pull request #65: [DOXIASITETOOLS-268] - Improve performance by
only loading the renderer version once during class initialization
URL: https://github.com/apache/maven-doxia-sitetools/pull/65
--
This is an automated message from the Apache Git Service.
To respond to the message,
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-268.
-
Resolution: Fixed
Fixed with
[8353560e73c8c13a02918d4d53f598afce1ca7fa|h
[
https://issues.apache.org/jira/browse/MNG-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626477#comment-17626477
]
Michael Osipov commented on MNG-7564:
-
Then it should be straightforward to apply.
> P
[
https://issues.apache.org/jira/browse/MCOMPILER-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626478#comment-17626478
]
Michael Osipov commented on MCOMPILER-509:
--
Not from me, I have layed the gro
[
https://issues.apache.org/jira/browse/MNG-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders updated MNG-7564:
-
Fix Version/s: 3.9.0-candidate
> Potential NPE in MavenMetadataSource
> ---
[
https://issues.apache.org/jira/browse/MNG-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626502#comment-17626502
]
Hudson commented on MNG-7564:
-
Build unstable in Jenkins: Maven » Maven TLP » maven » maven-3.9
[
https://issues.apache.org/jira/browse/MNG-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7564:
Fix Version/s: 3.9.0
(was: 3.9.0-candidate)
> Potential NPE in MavenMetadataSo
[
https://issues.apache.org/jira/browse/DOXIA-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626517#comment-17626517
]
Michael Osipov commented on DOXIA-667:
--
I have pushed a branch which should fix your
kwin commented on PR #862:
URL: https://github.com/apache/maven/pull/862#issuecomment-1296927401
Ok, so when generating descriptor beans in a dedicated package, where should
this live? IMHO it doesn't make sense to expose under
https://github.com/apache/maven/tree/master/api/maven-api-core.
[
https://issues.apache.org/jira/browse/MNG-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626530#comment-17626530
]
ASF GitHub Bot commented on MNG-7588:
-
kwin commented on PR #862:
URL: https://github.c
elharo commented on code in PR #135:
URL:
https://github.com/apache/maven-dependency-plugin/pull/135#discussion_r1009346626
##
src/it/projects/mdep-568-go-offline-exclude/pom.xml:
##
@@ -0,0 +1,57 @@
+
+
+
+http://maven.apache.org/POM/4.0.0";
+ xmlns:xsi="http://www.w3.
[
https://issues.apache.org/jira/browse/MNG-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626566#comment-17626566
]
wei cai commented on MNG-5896:
--
[~michael-o] [~cstamas]
May I know the additional things I c
[
https://issues.apache.org/jira/browse/MNG-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626575#comment-17626575
]
Michael Osipov commented on MNG-5896:
-
[~wecai], we will first integrate this into 3.9.
dependabot[bot] opened a new pull request, #169:
URL: https://github.com/apache/maven-plugin-tools/pull/169
Bumps [wagon-provider-api](https://github.com/apache/maven-wagon) from 2.4
to 2.12.
Commits
https://github.com/apache/maven-wagon/commit/0f2c8bc57a9b3094e6566ca601bf2025d
michael-o commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297127783
@jdimeo have a look
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific commen
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626596#comment-17626596
]
ASF GitHub Bot commented on DOXIA-678:
--
michael-o commented on PR #126:
URL: https://
[
https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626603#comment-17626603
]
Philippe Cloutier commented on MRESOLVER-7:
---
Thank you very much [~wecai] for
Eric Barboni created MSCMPUB-51:
---
Summary: Api incompatibility issue using maven-scm-provider-gitexe
2.0.0-M2
Key: MSCMPUB-51
URL: https://issues.apache.org/jira/browse/MSCMPUB-51
Project: Maven SCM Pub
jdimeo commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297231833
Looks good @michael-o ! However, how future proof is this approach? As you
mentioned, there aren't a ton of people able to maintain Doxia any more and I'm
a bit worried about all these s
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626634#comment-17626634
]
ASF GitHub Bot commented on DOXIA-678:
--
jdimeo commented on PR #126:
URL: https://git
[
https://issues.apache.org/jira/browse/MSCMPUB-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626636#comment-17626636
]
Michael Osipov commented on MSCMPUB-51:
---
Please show the full output. The reason li
michael-o commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297241475
> Looks good @michael-o ! However, how future proof is this approach? As you
mentioned, there aren't a ton of people able to maintain Doxia any more and I'm
a bit worried about all th
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626639#comment-17626639
]
ASF GitHub Bot commented on DOXIA-678:
--
michael-o commented on PR #126:
URL: https://
jdimeo commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297245608
> Also consider that I am the only one maintaining Doxia for the last couple
of years...
That is exactly what I was considering with my comment :-) thank you for
your time and keeping
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626640#comment-17626640
]
ASF GitHub Bot commented on DOXIA-678:
--
jdimeo commented on PR #126:
URL: https://git
Neutius commented on PR #170:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/170#issuecomment-1297256661
Hi! We're using the maven-javadoc-plugin at our company, and our parent
company's IT department is complaining about "dangerous" code that is present
on our build server. Turn
[
https://issues.apache.org/jira/browse/MSCMPUB-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626645#comment-17626645
]
Eric Barboni commented on MSCMPUB-51:
-
Failed to execute goal
org.apache.maven.plugi
michael-o commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297261130
> > Also consider that I am the only one maintaining Doxia for the last
couple of years...
>
> That is exactly what I was considering with my comment :-) thank you for
your tim
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626647#comment-17626647
]
ASF GitHub Bot commented on DOXIA-678:
--
michael-o commented on PR #126:
URL: https://
jdimeo commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297266005
I still vote for debug, because it doesn't actually cause a problem (the
tags still render just fine when mixed with Markdown), but yet logging at
`WARN` does cause a *huge* problem when
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626648#comment-17626648
]
ASF GitHub Bot commented on DOXIA-678:
--
jdimeo commented on PR #126:
URL: https://git
jdimeo commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297268799
Or, if you want to keep it as a warning, maybe keep a static thread safe
list of which tags have been WARNed already, and only log it once per tag.
That's a lot of work but then would be
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626649#comment-17626649
]
ASF GitHub Bot commented on DOXIA-678:
--
jdimeo commented on PR #126:
URL: https://git
michael-o commented on PR #170:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/170#issuecomment-1297277927
> Hi! We're using the maven-javadoc-plugin at our company, and our parent
company's IT department is complaining about "dangerous" code that is present
on our build server.
David Grieve created MSHARED-1156:
-
Summary: Upgrade commons-io to 2.11.0
Key: MSHARED-1156
URL: https://issues.apache.org/jira/browse/MSHARED-1156
Project: Maven Shared Components
Issue Type
michael-o commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297280919
> Or, if you want to keep it as a warning, maybe keep a static thread safe
list of which tags have been WARNed already, and only log it once per tag.
That's a lot of work but then wou
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626656#comment-17626656
]
ASF GitHub Bot commented on DOXIA-678:
--
michael-o commented on PR #126:
URL: https://
jdimeo commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297283317
... which is why I have been suggesting we just simply change the level from
WARN to DEBUG :-)
--
This is an automated message from the Apache Git Service.
To respond to the message, p
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626657#comment-17626657
]
ASF GitHub Bot commented on DOXIA-678:
--
jdimeo commented on PR #126:
URL: https://git
michael-o commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297287988
> ... which is why I have been suggesting we just simply change the level
from WARN to DEBUG :-)
Please create separate issue for this. Note that multiple parsers emit this
war
[
https://issues.apache.org/jira/browse/MSCMPUB-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626659#comment-17626659
]
Michael Osipov commented on MSCMPUB-51:
---
OK, now I see. I think that this invalid:
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626660#comment-17626660
]
ASF GitHub Bot commented on DOXIA-678:
--
michael-o commented on PR #126:
URL: https://
Neutius commented on PR #170:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/170#issuecomment-1297293292
> I won't object, it is not a blocker.
Thanks a lot, you made my day a lot easier.
I'm not 100% sure, but it seems the PR still can't be merged?
 filed
[
https://issues.apache.org/jira/browse/MWRAPPER-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626705#comment-17626705
]
ASF GitHub Bot commented on MWRAPPER-81:
ArloL opened a new pull request, #67:
U
michael-o commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297501277
@jdimeo Are we good to merge this one?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626750#comment-17626750
]
ASF GitHub Bot commented on DOXIA-678:
--
michael-o commented on PR #126:
URL: https://
jdimeo commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297502399
Yes!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626751#comment-17626751
]
ASF GitHub Bot commented on DOXIA-678:
--
jdimeo commented on PR #126:
URL: https://git
asfgit merged PR #126:
URL: https://github.com/apache/maven-doxia/pull/126
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apac
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626755#comment-17626755
]
ASF GitHub Bot commented on DOXIA-678:
--
asfgit merged PR #126:
URL: https://github.co
[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIA-678.
Resolution: Fixed
Fixed with
[b9a4ff884a1b7b847eaaeaee9df77e843cc61ec6|https://gitbox.apache.org/re
chicobento commented on PR #136:
URL: https://github.com/apache/maven-enforcer/pull/136#issuecomment-1297560012
Hi, I see that this hasnt been changed in a long time. Are there any plans
on having this brought up again and possibly merged ? Im specially looking into
ways of excudling tests
sman-81 commented on PR #170:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/170#issuecomment-1297678307
> But in this case the title shouldn't contains "to address
[CVE-2022-42889](https://github.com/advisories/GHSA-599f-7c49-w659)" because we
didn't assess it and we can "claim"
mthmulders commented on code in PR #575:
URL: https://github.com/apache/maven-surefire/pull/575#discussion_r1009862231
##
surefire-its/src/test/resources/surefire-1993-jpms-providing-modules/application/pom.xml:
##
@@ -72,7 +72,7 @@
sman-81 commented on PR #170:
URL:
https://github.com/apache/maven-javadoc-plugin/pull/170#issuecomment-1297682585
> I'm not 100% sure, but it seems the PR still can't be merged?
Not due to merge conflicts. Change is binary-compatible. Contributing can at
times feel a little like an
HannesWell commented on code in PR #257:
URL:
https://github.com/apache/maven-dependency-plugin/pull/257#discussion_r1009881713
##
src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml:
##
@@ -0,0 +1,68 @@
+
+
+
+
+
+
+
HannesWell commented on code in PR #257:
URL:
https://github.com/apache/maven-dependency-plugin/pull/257#discussion_r1009883147
##
src/main/java/org/apache/maven/plugins/dependency/AbstractDependencyMojo.java:
##
@@ -59,6 +60,21 @@
@Component
private ArchiverManager a
kwin commented on code in PR #257:
URL:
https://github.com/apache/maven-dependency-plugin/pull/257#discussion_r1009885032
##
src/main/java/org/apache/maven/plugins/dependency/AbstractDependencyMojo.java:
##
@@ -59,6 +60,21 @@
@Component
private ArchiverManager archive
SimonBaars commented on code in PR #575:
URL: https://github.com/apache/maven-surefire/pull/575#discussion_r1009937829
##
surefire-its/src/test/resources/surefire-1993-jpms-providing-modules/application/pom.xml:
##
@@ -72,7 +72,7 @@
[
https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626936#comment-17626936
]
wei cai commented on MRESOLVER-7:
-
[~Chealer]
You may find more details in
https://is
gzm55 opened a new pull request, #730:
URL: https://github.com/apache/maven-mvnd/pull/730
This pr improves native image portability on linux and windows via:
1. Enable mostly static image switch on linux and windows. on linux, the
cost is about 33K file size before compressed, about +0.1%
69 matches
Mail list logo
