Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
lprimak commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869956490 @kwin See https://github.com/apache/shiro/pull/1245 for an example Introducing test failure doesn't actually produce a failure, due to maven resolver pulling the older snapshot from repo. When the next commit re-introduces disabling of the snapshot repository, the tests break as expected. However, that breaks dependabot (maybe I introduce @olamy 's fix!) but still, a lot of work just due to the repository entry in parent pom. Better to remove it :) As you can see I am not the only one with similar problem. Perhaps @gnodet 's pending fix will alleviate this for 4.x, but 3.x is still broken. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Where can I download Maven 3.6.3 version? [maven-mvnd]
YANGJINJUE commented on issue #903: URL: https://github.com/apache/maven-mvnd/issues/903#issuecomment-1869955176 > The newest version of mvnd that uses Maven 3.6.3 is 0.4.3 : https://github.com/apache/maven-mvnd/releases/tag/0.4.3 Thanks -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
lprimak commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869863388 Will try that. Thank you! Even if that works I still think the repository entries should be removed. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
olamy commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869851414 Maybe configure dependabot # Add Maven Central explicitly to work around: # https://github.com/dependabot/dependabot-core/issues/8329 registries: maven-central: type: maven-repository url: https://repo.maven.apache.org/maven2 updates: - package-ecosystem: maven directory: "/" schedule: interval: "daily" target-branch: "main" registries: - maven-central -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MNGSITE-530) Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
[
https://issues.apache.org/jira/browse/MNGSITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned MNGSITE-530:
---
Assignee: Guillaume Nodet
> Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
> --
>
> Key: MNGSITE-530
> URL: https://issues.apache.org/jira/browse/MNGSITE-530
> Project: Maven Project Web Site
> Issue Type: Bug
> Environment: Chrome
>Reporter: Matthias Bünger
>Assignee: Guillaume Nodet
>Priority: Major
>
> The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
> The [alpha-10 maven-model
> page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html]
> lists links to all current XSD, including the one for the 4.1.0 version of
> Maven 4:
> But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
> existing and throws a "404 Page not found" (as of 2023-12-26), while all
> others are working.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MPMD-390) Dynamically calculate xrefLocation/xrefTestLocation
Michael Osipov created MPMD-390: --- Summary: Dynamically calculate xrefLocation/xrefTestLocation Key: MPMD-390 URL: https://issues.apache.org/jira/browse/MPMD-390 Project: Maven PMD Plugin Issue Type: Improvement Components: PMD Affects Versions: 3.21.2 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 4.0.0-M1 After MSHARED-1327 we need to dynamically calculate where (Test) XRef report resides. Unless an explicit value has been provided. The calculation considers both standalone mode *and* site mode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JXR-189) Dynamically calculate javadocLocation/testJavadocLocation
[
https://issues.apache.org/jira/browse/JXR-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated JXR-189:
---
Issue Type: Improvement (was: Task)
> Dynamically calculate javadocLocation/testJavadocLocation
> -
>
> Key: JXR-189
> URL: https://issues.apache.org/jira/browse/JXR-189
> Project: Maven JXR
> Issue Type: Improvement
> Components: maven-jxr-plugin
>Affects Versions: 3.3.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M1
>
>
> After MSHARED-1327 we need to dynamically calculate where (Test) Javadoc
> report resides. Unless an explicit value has been provided.
> The calculation considers both standalone mode *and* site mode.
> Also, for consistency reasons the parameter {{javadocDir}} will be renamed to
> {{javadocLocation}} as done with XRef in other plugins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MPMD-389) Upgrade to Doxia 2.0.0 Milestone Stack
Michael Osipov created MPMD-389:
---
Summary: Upgrade to Doxia 2.0.0 Milestone Stack
Key: MPMD-389
URL: https://issues.apache.org/jira/browse/MPMD-389
Project: Maven PMD Plugin
Issue Type: Dependency upgrade
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 4.0.0-M1
* Upgrade to Maven Site Plugin 4.0.0-M13
* Upgrade to Maven Project Info Reports Plugin 4.0.0-M1
* Upgrade to Maven JXR Plugin 4.0.0-M1
* Upgrade to Doxia 2.0.0-M8
* Upgrade to Maven Reporting Impl 4.0.0-M13
Also, for consistency reasons the parameter {{includeXmlInSite}} will be
renamed to {{includeXmlInReports}} to better reflect that this plugin does not
only run in site mode, but also in standalone mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[
https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800630#comment-17800630
]
ASF GitHub Bot commented on MPLUGIN-499:
michael-o commented on code in PR #250:
URL:
https://github.com/apache/maven-plugin-tools/pull/250#discussion_r1436622008
##
maven-plugin-report-plugin/src/main/java/org/apache/maven/plugin/plugin/report/PluginOverviewRenderer.java:
##
@@ -144,15 +145,26 @@ private void renderGoalsSection(boolean hasMavenReport) {
}
}
-String description;
+sink.tableCell();
if (StringUtils.isNotEmpty(mojo.getDeprecated())) {
-description = "" + getI18nString("goal.deprecated") +
" " + mojo.getDeprecated();
-} else if (StringUtils.isNotEmpty(mojo.getDescription())) {
+sink.division();
+sink.inline(SinkEventAttributeSet.Semantics.STRONG);
+sink.text(getI18nString("goal.deprecated"));
+sink.text(".");
+sink.inline_();
+sink.rawText(mojo.getDeprecated());
Review Comment:
Should be preceded with a space.
> Deprecate descriptions are missing in description table
> ---
>
> Key: MPLUGIN-499
> URL: https://issues.apache.org/jira/browse/MPLUGIN-499
> Project: Maven Plugin Tools
> Issue Type: Bug
>Affects Versions: 3.10.2
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.11.0
>
>
> We have only *Deprecated.* label without description.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
michael-o commented on code in PR #250:
URL:
https://github.com/apache/maven-plugin-tools/pull/250#discussion_r1436622008
##
maven-plugin-report-plugin/src/main/java/org/apache/maven/plugin/plugin/report/PluginOverviewRenderer.java:
##
@@ -144,15 +145,26 @@ private void renderGoalsSection(boolean hasMavenReport) {
}
}
-String description;
+sink.tableCell();
if (StringUtils.isNotEmpty(mojo.getDeprecated())) {
-description = "" + getI18nString("goal.deprecated") +
" " + mojo.getDeprecated();
-} else if (StringUtils.isNotEmpty(mojo.getDescription())) {
+sink.division();
+sink.inline(SinkEventAttributeSet.Semantics.STRONG);
+sink.text(getI18nString("goal.deprecated"));
+sink.text(".");
+sink.inline_();
+sink.rawText(mojo.getDeprecated());
Review Comment:
Should be preceded with a space.
--
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.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (JXR-189) Dynamically calculate javadocLocation/testJavadocLocation
[
https://issues.apache.org/jira/browse/JXR-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated JXR-189:
---
Description:
After MSHARED-1327 we need to dynamically calculate where (Test) Javadoc report
resides. Unless an explicit value has been provided.
The calculation considers both standalone mode *and* site mode.
Also, for consistency reasons the parameter {{javadocDir}} will be renamed to
{{javadocLocation}} as done with XRef in other plugins.
was:
After MSHARED-1327 we need to dynamically calculate where (Test) Javadoc report
resides. Unless an explicit value has been provided.
The calculation considers both standalone mode *and* site mode.
> Dynamically calculate javadocLocation/testJavadocLocation
> -
>
> Key: JXR-189
> URL: https://issues.apache.org/jira/browse/JXR-189
> Project: Maven JXR
> Issue Type: Task
> Components: maven-jxr-plugin
>Affects Versions: 3.3.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-M1
>
>
> After MSHARED-1327 we need to dynamically calculate where (Test) Javadoc
> report resides. Unless an explicit value has been provided.
> The calculation considers both standalone mode *and* site mode.
> Also, for consistency reasons the parameter {{javadocDir}} will be renamed to
> {{javadocLocation}} as done with XRef in other plugins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (JXR-189) Dynamically calculate javadocLocation/testJavadocLocation
Michael Osipov created JXR-189: -- Summary: Dynamically calculate javadocLocation/testJavadocLocation Key: JXR-189 URL: https://issues.apache.org/jira/browse/JXR-189 Project: Maven JXR Issue Type: Task Components: maven-jxr-plugin Affects Versions: 3.3.2 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 4.0.0-M1 After MSHARED-1327 we need to dynamically calculate where (Test) Javadoc report resides. Unless an explicit value has been provided. The calculation considers both standalone mode *and* site mode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JXR-169) Use of deprecated velocity configuration keys
[
https://issues.apache.org/jira/browse/JXR-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated JXR-169:
---
Fix Version/s: 4.0.0-M1
> Use of deprecated velocity configuration keys
> --
>
> Key: JXR-169
> URL: https://issues.apache.org/jira/browse/JXR-169
> Project: Maven JXR
> Issue Type: Improvement
> Components: maven-jxr-plugin
>Affects Versions: 3.2.0
>Reporter: Dave Wichers
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 4.0.0-M1
>
>
> When I run: mvn site, using my project's pom:
> [https://github.com/nahsra/antisamy/blob/main/pom.xml]
> I'm seeing the following warnings. I think this means these jxr-plugins are
> using old resource names. Unless I'm doing something wrong in my pom. But I
> can't find any references to these resources in my project, so I'm assuming
> its a problem in your project. Can you confirm this is an issue in maven-jxr
> and you can fix it? Or is it my fault?
> The velocity configuration key changes are described here:
> https://velocity.apache.org/engine/devel/configuration-property-changes-in-2.1.html
> [*INFO*] Generating "{*}Source Xref{*}" report *---*
> maven-jxr-plugin:3.2.0:jxr
> [*WARNING*] configuration key 'resource.loader' has been deprecated in favor
> of 'resource.loaders'
> [*WARNING*] configuration key 'classpath.resource.loader.class' has been
> deprecated in favor of 'resource.loader.classpath.class'
> [*WARNING*] configuration key 'velocimacro.library' has been deprecated in
> favor of 'velocimacro.library.path'
> [*INFO*] Generating "{*}Test Source Xref{*}" report *---*
> maven-jxr-plugin:3.2.0:test-jxr
> [*WARNING*] configuration key 'resource.loader' has been deprecated in favor
> of 'resource.loaders'
> [*WARNING*] configuration key 'classpath.resource.loader.class' has been
> deprecated in favor of 'resource.loader.classpath.class'
> [*WARNING*] configuration key 'velocimacro.library' has been deprecated in
> favor of 'velocimacro.library.path'
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800627#comment-17800627 ] ASF GitHub Bot commented on MPLUGIN-499: michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869771986 > Now it will be as:  Good. There should be a space between "Deprecated." and the actual text. Let me test meanwhile. > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869771986 > Now it will be as:  Good. There should be a space between "Deprecated." and the actual text. Let me test meanwhile. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800626#comment-17800626 ] ASF GitHub Bot commented on MPLUGIN-499: slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869768581 Now it will be as:  > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869768581 Now it will be as:  -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (JXR-188) Upgrade to Doxia 2.0.0 Milestone Stack
Michael Osipov created JXR-188: -- Summary: Upgrade to Doxia 2.0.0 Milestone Stack Key: JXR-188 URL: https://issues.apache.org/jira/browse/JXR-188 Project: Maven JXR Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 4.0.0-M1 * Upgrade to Maven Reporting API 4.0.0-M9 * Upgrade to Maven Reporting Impl 4.0.0-M13 * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Velocity Engine 2.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800595#comment-17800595 ] ASF GitHub Bot commented on MPLUGIN-499: michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869757432 > But it is a next issue on list of goals - plugin-info.htm when goal is deprecated we don't have a description. This isn't right. Deprecation should be first, line break, description. > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869757432 > But it is a next issue on list of goals - plugin-info.htm when goal is deprecated we don't have a description. This isn't right. Deprecation should be first, line break, description. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800592#comment-17800592 ] ASF GitHub Bot commented on MPLUGIN-499: michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869757202 > Missing dot on list of goals is by accident. The same resources is used on goal details page: > >  > > It was: > > ``` > Deprecated.: > ``` Yes, one fixed the other one broken :-D Can you address? > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869757202 > Missing dot on list of goals is by accident. The same resources is used on goal details page: > >  > > It was: > > ``` > Deprecated.: > ``` Yes, one fixed the other one broken :-D Can you address? -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869755793 But it is a next issue on list of goals - plugin-info.htm when goal is deprecated we don't have a description. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800585#comment-17800585 ] ASF GitHub Bot commented on MPLUGIN-499: slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869755793 But it is a next issue on list of goals - plugin-info.htm when goal is deprecated we don't have a description. > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800578#comment-17800578 ] ASF GitHub Bot commented on MPLUGIN-499: slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869754589 Missing dot on list of goals is by accident. The same resources is used on goal details page:  It was: ``` Deprecated.: ``` > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869754589 Missing dot on list of goals is by accident. The same resources is used on goal details page:  It was: ``` Deprecated.: ``` -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Where can I download Maven 3.6.3 version? [maven-mvnd]
ppalaga closed issue #903: Where can I download Maven 3.6.3 version? URL: https://github.com/apache/maven-mvnd/issues/903 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Where can I download Maven 3.6.3 version? [maven-mvnd]
ppalaga commented on issue #903: URL: https://github.com/apache/maven-mvnd/issues/903#issuecomment-1869737235 The newest version of mvnd that uses Maven 3.6.3 is 0.4.3 : https://github.com/apache/maven-mvnd/releases/tag/0.4.3 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.commons:commons-lang3 from 3.12.0 to 3.14.0 [maven-jxr]
elharo merged PR #103: URL: https://github.com/apache/maven-jxr/pull/103 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump commons-io:commons-io from 2.14.0 to 2.15.1 [maven-jxr]
elharo merged PR #105: URL: https://github.com/apache/maven-jxr/pull/105 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (JXR-169) Use of deprecated velocity configuration keys
[
https://issues.apache.org/jira/browse/JXR-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned JXR-169:
--
Assignee: Michael Osipov
> Use of deprecated velocity configuration keys
> --
>
> Key: JXR-169
> URL: https://issues.apache.org/jira/browse/JXR-169
> Project: Maven JXR
> Issue Type: Improvement
> Components: maven-jxr-plugin
>Affects Versions: 3.2.0
>Reporter: Dave Wichers
>Assignee: Michael Osipov
>Priority: Minor
>
> When I run: mvn site, using my project's pom:
> [https://github.com/nahsra/antisamy/blob/main/pom.xml]
> I'm seeing the following warnings. I think this means these jxr-plugins are
> using old resource names. Unless I'm doing something wrong in my pom. But I
> can't find any references to these resources in my project, so I'm assuming
> its a problem in your project. Can you confirm this is an issue in maven-jxr
> and you can fix it? Or is it my fault?
> The velocity configuration key changes are described here:
> https://velocity.apache.org/engine/devel/configuration-property-changes-in-2.1.html
> [*INFO*] Generating "{*}Source Xref{*}" report *---*
> maven-jxr-plugin:3.2.0:jxr
> [*WARNING*] configuration key 'resource.loader' has been deprecated in favor
> of 'resource.loaders'
> [*WARNING*] configuration key 'classpath.resource.loader.class' has been
> deprecated in favor of 'resource.loader.classpath.class'
> [*WARNING*] configuration key 'velocimacro.library' has been deprecated in
> favor of 'velocimacro.library.path'
> [*INFO*] Generating "{*}Test Source Xref{*}" report *---*
> maven-jxr-plugin:3.2.0:test-jxr
> [*WARNING*] configuration key 'resource.loader' has been deprecated in favor
> of 'resource.loaders'
> [*WARNING*] configuration key 'classpath.resource.loader.class' has been
> deprecated in favor of 'resource.loader.classpath.class'
> [*WARNING*] configuration key 'velocimacro.library' has been deprecated in
> favor of 'velocimacro.library.path'
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
lprimak commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869719981 Also see this Slack discussion: https://the-asf.slack.com/archives/C7Q9JB404/p1703540867035689 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
lprimak commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869719758 Just did a quick google search "why repository in pom bad" and found this: https://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/#:~:text=This%20causes%20a%20few%20problems,one%20developer%20but%20not%20another. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (JXR-187) Upgrade components
[ https://issues.apache.org/jira/browse/JXR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed JXR-187. -- Resolution: Fixed Fixed with [ec1e1a9ce992a9baa52aa041a25bd6079ca94261|https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=commit;h=ec1e1a9ce992a9baa52aa041a25bd6079ca94261]. > Upgrade components > -- > > Key: JXR-187 > URL: https://issues.apache.org/jira/browse/JXR-187 > Project: Maven JXR > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: version-next > > > * Upgrade to Commons Lang 3.14.0 > * Upgrade to Commons IO 2.15.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JXR-187) Upgrade components
Michael Osipov created JXR-187: -- Summary: Upgrade components Key: JXR-187 URL: https://issues.apache.org/jira/browse/JXR-187 Project: Maven JXR Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: version-next * Upgrade to Commons Lang 3.14.0 * Upgrade to Commons IO 2.15.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
kwin commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869714292 Please give some reasons, except for unclear downstream issues. This is very helpful for most ASF projects is my argument for keeping it in that place! -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
lprimak commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869713540 There is also a matter of pragmatism here. The repository entries really shouldn't be there in the first place. No matter what the downstream issues are, those should be removed anyway IMHO -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MPLUGIN-492) Documentation for plugins in general: Goals comprises more than that
[ https://issues.apache.org/jira/browse/MPLUGIN-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPLUGIN-492. -- Resolution: Fixed Fixed with [9bb13f0427d8795d2c47c5068fc4c8ba552892e2|https://gitbox.apache.org/repos/asf?p=maven-plugin-tools.git;a=commit;h=9bb13f0427d8795d2c47c5068fc4c8ba552892e2]. > Documentation for plugins in general: Goals comprises more than that > > > Key: MPLUGIN-492 > URL: https://issues.apache.org/jira/browse/MPLUGIN-492 > Project: Maven Plugin Tools > Issue Type: Improvement >Affects Versions: 3.10.2 >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > Fix For: 3.11.0 > > > In the `site.xml` of all plugins, there is an entry > ``` > > ``` > leading to an according entry in the sidebar menu. > The item name is misleading: it should be Plugin Info or Plugin > Documentation, > because it is more than just Goals. > Interesting enough, the goals do not have a separate subsection. > Or it is called Goals and related.. I dont know. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-492) Documentation for plugins in general: Goals comprises more than that
[ https://issues.apache.org/jira/browse/MPLUGIN-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800545#comment-17800545 ] ASF GitHub Bot commented on MPLUGIN-492: asfgit merged PR #252: URL: https://github.com/apache/maven-plugin-tools/pull/252 > Documentation for plugins in general: Goals comprises more than that > > > Key: MPLUGIN-492 > URL: https://issues.apache.org/jira/browse/MPLUGIN-492 > Project: Maven Plugin Tools > Issue Type: Improvement >Affects Versions: 3.10.2 >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > Fix For: 3.11.0 > > > In the `site.xml` of all plugins, there is an entry > ``` > > ``` > leading to an according entry in the sidebar menu. > The item name is misleading: it should be Plugin Info or Plugin > Documentation, > because it is more than just Goals. > Interesting enough, the goals do not have a separate subsection. > Or it is called Goals and related.. I dont know. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-492] Documentation for plugins in general: Goals comprises m… [maven-plugin-tools]
asfgit merged PR #252: URL: https://github.com/apache/maven-plugin-tools/pull/252 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800544#comment-17800544 ] ASF GitHub Bot commented on MPLUGIN-499: michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869712204 Looks better now. I see one difference: Before:  After:  The full stop is gone. Is that on purpose? > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869712204 Looks better now. I see one difference: Before:  After:  The full stop is gone. Is that on purpose? -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
kwin commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869711752 IMHO adding the ASF snapshot repo shouldn't do any harm for projects not leveraging it. So let us rather track the downstream issues separately here. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]
lprimak commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1869707135 > This sounds like an issue with your reactor then. Not sure what it could possibly be. It took me 3+ hours of debugging to figure out why the builds weren't working correctly when I finally found that this was the issue. Not sure I have it in me to spend more hours figuring this out. However, it's pretty clear that the repository section in POMs are frowned upon. I realize that this update is incompatible but IMHO this needs to be done for multiple reasons -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MPOM-452) Apache Parent POM - Use property for Apache Repository IDs
Lenny Primak created MPOM-452: - Summary: Apache Parent POM - Use property for Apache Repository IDs Key: MPOM-452 URL: https://issues.apache.org/jira/browse/MPOM-452 Project: Maven POMs Issue Type: Improvement Affects Versions: ASF-31 Reporter: Lenny Primak Add ability to override Apache Release and Snapshot repository IDs via properties Useful to deploy to different instances of repositories -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-450) Prevent the SCM elements from being inherited
[ https://issues.apache.org/jira/browse/MPOM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800542#comment-17800542 ] Lenny Primak commented on MPOM-450: --- Yes you are right. I was a little too zealous referencing your issue. I will open a new one > Prevent the SCM elements from being inherited > - > > Key: MPOM-450 > URL: https://issues.apache.org/jira/browse/MPOM-450 > Project: Maven POMs > Issue Type: Bug > Components: asf >Affects Versions: ASF-31 >Reporter: Konrad Windszus >Priority: Major > > Currently the SCM elements are not encapsulated in a profile, i.e. they are > automatically inherited by all derived projects. As those never share > anything with the SCM URLs of the ASF parent it would make sense to only > conditionally set those SCM elements (in a profile). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800533#comment-17800533 ] ASF GitHub Bot commented on MPLUGIN-499: michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869677136 Checking... > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
michael-o commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869677136 Checking... -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-492) Documentation for plugins in general: Goals comprises more than that
[ https://issues.apache.org/jira/browse/MPLUGIN-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800532#comment-17800532 ] ASF GitHub Bot commented on MPLUGIN-492: michael-o commented on PR #252: URL: https://github.com/apache/maven-plugin-tools/pull/252#issuecomment-1869675395 > I hope that translations are ok 😄 It is, hand-crafted, native level. > Documentation for plugins in general: Goals comprises more than that > > > Key: MPLUGIN-492 > URL: https://issues.apache.org/jira/browse/MPLUGIN-492 > Project: Maven Plugin Tools > Issue Type: Improvement >Affects Versions: 3.10.2 >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > Fix For: 3.11.0 > > > In the `site.xml` of all plugins, there is an entry > ``` > > ``` > leading to an according entry in the sidebar menu. > The item name is misleading: it should be Plugin Info or Plugin > Documentation, > because it is more than just Goals. > Interesting enough, the goals do not have a separate subsection. > Or it is called Goals and related.. I dont know. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-492] Documentation for plugins in general: Goals comprises m… [maven-plugin-tools]
michael-o commented on PR #252: URL: https://github.com/apache/maven-plugin-tools/pull/252#issuecomment-1869675395 > I hope that translations are ok 😄 It is, hand-crafted, native level. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800529#comment-17800529 ] ASF GitHub Bot commented on MPLUGIN-499: slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869673167 ok, next version > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-499] Add deprecate description in parameters table [maven-plugin-tools]
slawekjaranowski commented on PR #250: URL: https://github.com/apache/maven-plugin-tools/pull/250#issuecomment-1869673167 ok, next version -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-500) Parameter tables should contain only first sentence of description
[ https://issues.apache.org/jira/browse/MPLUGIN-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800528#comment-17800528 ] Michael Osipov commented on MPLUGIN-500: https://github.com/checkstyle/checkstyle/blob/92e5e1e42b760171c19d92f48aa7eb61ebd9dc4f/src/main/java/com/puppycrawl/tools/checkstyle/checks/javadoc/SummaryJavadocCheck.java#L584-L606 > Parameter tables should contain only first sentence of description > -- > > Key: MPLUGIN-500 > URL: https://issues.apache.org/jira/browse/MPLUGIN-500 > Project: Maven Plugin Tools > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Priority: Major > > In parameter tables we should contain only first sentence of description. > Full description should be printed in Parameter Details sections. > Such way can be like Javadoc style. > > The most problematic is how to extract first sentence ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.commons:commons-lang3 from 3.8.1 to 3.14.0 [maven-plugin-tools]
dependabot[bot] commented on PR #243: URL: https://github.com/apache/maven-plugin-tools/pull/243#issuecomment-1869667106 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.commons:commons-lang3 from 3.8.1 to 3.14.0 [maven-plugin-tools]
michael-o commented on PR #243: URL: https://github.com/apache/maven-plugin-tools/pull/243#issuecomment-1869667087 Superseded by #212. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.commons:commons-lang3 from 3.8.1 to 3.14.0 [maven-plugin-tools]
michael-o closed pull request #243: Bump org.apache.commons:commons-lang3 from 3.8.1 to 3.14.0 URL: https://github.com/apache/maven-plugin-tools/pull/243 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.codehaus.plexus:plexus-velocity from 1.2 to 2.1.0 [maven-plugin-tools]
dependabot[bot] commented on PR #251: URL: https://github.com/apache/maven-plugin-tools/pull/251#issuecomment-1869666996 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.codehaus.plexus:plexus-velocity from 1.2 to 2.1.0 [maven-plugin-tools]
michael-o closed pull request #251: Bump org.codehaus.plexus:plexus-velocity from 1.2 to 2.1.0 URL: https://github.com/apache/maven-plugin-tools/pull/251 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.codehaus.plexus:plexus-velocity from 1.2 to 2.1.0 [maven-plugin-tools]
michael-o commented on PR #251: URL: https://github.com/apache/maven-plugin-tools/pull/251#issuecomment-1869666973 Superseded by #212. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MPLUGIN-414) Upgrade to Velocity Engine 2.3
[ https://issues.apache.org/jira/browse/MPLUGIN-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPLUGIN-414: --- Summary: Upgrade to Velocity Engine 2.3 (was: Upgrade Velocity Engine to 2.3) > Upgrade to Velocity Engine 2.3 > -- > > Key: MPLUGIN-414 > URL: https://issues.apache.org/jira/browse/MPLUGIN-414 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > > This will also include the ugprade of Plexus Velocity to 2.1.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPLUGIN-501) Upgrade to Doxia 2.0.0 Milestone Stack
Michael Osipov created MPLUGIN-501: -- Summary: Upgrade to Doxia 2.0.0 Milestone Stack Key: MPLUGIN-501 URL: https://issues.apache.org/jira/browse/MPLUGIN-501 Project: Maven Plugin Tools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov * Upgrade to Doxia 2.0.0-M8 * Upgrade to Doxia Sitetools 2.0.0-M16 * Upgrade to Commons Lang 3.14.0 * Upgrade to Maven Site Plugin 4.0.0-M13 * Upgrade to Maven Project Info Reports Plugin 4.0.0-M1 * Upgrade to Plexus Velocity 2.1.0 * Upgrade to Maven Reporting API 4.0.0-M9 * Upgrade to Maven Reporting Impl 4.0.0-M13 * Upgrade to Velocity Engine 2.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPIR-454) Upgrade to Doxia 2.0.0 Milestone Stack
[ https://issues.apache.org/jira/browse/MPIR-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-454: Issue Type: Dependency upgrade (was: Improvement) > Upgrade to Doxia 2.0.0 Milestone Stack > -- > > Key: MPIR-454 > URL: https://issues.apache.org/jira/browse/MPIR-454 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M1 > > > * Upgrade to Doxia 2.0.0-M8 > * Upgrade to Doxia Sitetools 2.0.0-M16 > * Upgrade to Maven Site Plugin 4.0.0-M13 > * Upgrade to Maven Fluido Skin 2.0.0-M8 > * Upgrade to Maven Reporting API 4.0.0-M9 > * Upgrade to Maven Reporting Impl 4.0.0-M13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPLUGIN-414) Upgrade Velocity Engine to 2.3
[ https://issues.apache.org/jira/browse/MPLUGIN-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPLUGIN-414: --- Description: This will also include the ugprade of Plexus Velocity to 2.1. (was: This will also include the ugprade of Plexus Velocity to 2.0.) > Upgrade Velocity Engine to 2.3 > -- > > Key: MPLUGIN-414 > URL: https://issues.apache.org/jira/browse/MPLUGIN-414 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Priority: Major > > This will also include the ugprade of Plexus Velocity to 2.1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPLUGIN-414) Upgrade Velocity Engine to 2.3
[ https://issues.apache.org/jira/browse/MPLUGIN-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPLUGIN-414: -- Assignee: Michael Osipov > Upgrade Velocity Engine to 2.3 > -- > > Key: MPLUGIN-414 > URL: https://issues.apache.org/jira/browse/MPLUGIN-414 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > > This will also include the ugprade of Plexus Velocity to 2.1.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPLUGIN-414) Upgrade Velocity Engine to 2.3
[ https://issues.apache.org/jira/browse/MPLUGIN-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPLUGIN-414: --- Description: This will also include the ugprade of Plexus Velocity to 2.1.0. (was: This will also include the ugprade of Plexus Velocity to 2.1.) > Upgrade Velocity Engine to 2.3 > -- > > Key: MPLUGIN-414 > URL: https://issues.apache.org/jira/browse/MPLUGIN-414 > Project: Maven Plugin Tools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Priority: Major > > This will also include the ugprade of Plexus Velocity to 2.1.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-495) WARNINGs based on usage of @Component for session/MavenProject instead of @Parameter
[
https://issues.apache.org/jira/browse/MPLUGIN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800518#comment-17800518
]
Michael Osipov commented on MPLUGIN-495:
[~cstamas]...
> WARNINGs based on usage of @Component for session/MavenProject instead of
> @Parameter
>
>
> Key: MPLUGIN-495
> URL: https://issues.apache.org/jira/browse/MPLUGIN-495
> Project: Maven Plugin Tools
> Issue Type: Improvement
>Affects Versions: 3.10.2
>Reporter: Karl Heinz Marbaise
>Assignee: Guillaume Nodet
>Priority: Critical
>
> A change of parameters like this:
> {code:java}
> @Parameter(defaultValue = "${project}", readonly = true, required = true)
> {code}
> into:
> {code:java}
> @Component
> {code}
> This will result in WARNINGs like this:
> {code}
> Warning: Deprecated @Component annotation for 'session' field in
> org.apache.maven.plugins.dependency.GetMojo: replace with @Parameter(
> defaultValue = "${session}", readonly = true )
> {code}
> The shown deprecation message is wrong. It is fine to use that for components
> to be injected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MPLUGIN-492] Documentation for plugins in general: Goals comprises m… [maven-plugin-tools]
michael-o commented on PR #252: URL: https://github.com/apache/maven-plugin-tools/pull/252#issuecomment-1869645836 @Reissner 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 comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPLUGIN-492) Documentation for plugins in general: Goals comprises more than that
[ https://issues.apache.org/jira/browse/MPLUGIN-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800516#comment-17800516 ] ASF GitHub Bot commented on MPLUGIN-492: michael-o commented on PR #252: URL: https://github.com/apache/maven-plugin-tools/pull/252#issuecomment-1869645836 @Reissner have a look. > Documentation for plugins in general: Goals comprises more than that > > > Key: MPLUGIN-492 > URL: https://issues.apache.org/jira/browse/MPLUGIN-492 > Project: Maven Plugin Tools > Issue Type: Improvement >Affects Versions: 3.10.2 >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > Fix For: 3.11.0 > > > In the `site.xml` of all plugins, there is an entry > ``` > > ``` > leading to an according entry in the sidebar menu. > The item name is misleading: it should be Plugin Info or Plugin > Documentation, > because it is more than just Goals. > Interesting enough, the goals do not have a separate subsection. > Or it is called Goals and related.. I dont know. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-492) Documentation for plugins in general: Goals comprises more than that
[ https://issues.apache.org/jira/browse/MPLUGIN-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800514#comment-17800514 ] ASF GitHub Bot commented on MPLUGIN-492: michael-o opened a new pull request, #252: URL: https://github.com/apache/maven-plugin-tools/pull/252 …ore than that This closes #252 > Documentation for plugins in general: Goals comprises more than that > > > Key: MPLUGIN-492 > URL: https://issues.apache.org/jira/browse/MPLUGIN-492 > Project: Maven Plugin Tools > Issue Type: Improvement >Affects Versions: 3.10.2 >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > Fix For: 3.11.0 > > > In the `site.xml` of all plugins, there is an entry > ``` > > ``` > leading to an according entry in the sidebar menu. > The item name is misleading: it should be Plugin Info or Plugin > Documentation, > because it is more than just Goals. > Interesting enough, the goals do not have a separate subsection. > Or it is called Goals and related.. I dont know. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [MPLUGIN-492] Documentation for plugins in general: Goals comprises m… [maven-plugin-tools]
michael-o opened a new pull request, #252: URL: https://github.com/apache/maven-plugin-tools/pull/252 …ore than that This closes #252 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MPLUGIN-499) Deprecate descriptions are missing in description table
[ https://issues.apache.org/jira/browse/MPLUGIN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPLUGIN-499: --- Summary: Deprecate descriptions are missing in description table (was: Deprecate descriptions is missing in description table) > Deprecate descriptions are missing in description table > --- > > Key: MPLUGIN-499 > URL: https://issues.apache.org/jira/browse/MPLUGIN-499 > Project: Maven Plugin Tools > Issue Type: Bug >Affects Versions: 3.10.2 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.11.0 > > > We have only *Deprecated.* label without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Moved] (MNGSITE-530) Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
[
https://issues.apache.org/jira/browse/MNGSITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov moved MNG-7990 to MNGSITE-530:
-
Key: MNGSITE-530 (was: MNG-7990)
Affects Version/s: (was: 4.0.0-alpha-10)
Project: Maven Project Web Site (was: Maven)
> Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
> --
>
> Key: MNGSITE-530
> URL: https://issues.apache.org/jira/browse/MNGSITE-530
> Project: Maven Project Web Site
> Issue Type: Bug
> Environment: Chrome
>Reporter: Matthias Bünger
>Priority: Major
>
> The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
> The [alpha-10 maven-model
> page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html]
> lists links to all current XSD, including the one for the 4.1.0 version of
> Maven 4:
> But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
> existing and throws a "404 Page not found" (as of 2023-12-26), while all
> others are working.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPLUGIN-500) Parameter tables should contain only first sentence of description
[ https://issues.apache.org/jira/browse/MPLUGIN-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800512#comment-17800512 ] Michael Osipov commented on MPLUGIN-500: I'd recommend looking at the Javadoc doclet in JDK source code and apply the same logic. > Parameter tables should contain only first sentence of description > -- > > Key: MPLUGIN-500 > URL: https://issues.apache.org/jira/browse/MPLUGIN-500 > Project: Maven Plugin Tools > Issue Type: Improvement >Reporter: Slawomir Jaranowski >Priority: Major > > In parameter tables we should contain only first sentence of description. > Full description should be printed in Parameter Details sections. > Such way can be like Javadoc style. > > The most problematic is how to extract first sentence ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNGSITE-530) Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
[
https://issues.apache.org/jira/browse/MNGSITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800511#comment-17800511
]
Michael Osipov commented on MNGSITE-530:
[~gnodet], this one is for you.
> Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
> --
>
> Key: MNGSITE-530
> URL: https://issues.apache.org/jira/browse/MNGSITE-530
> Project: Maven Project Web Site
> Issue Type: Bug
> Environment: Chrome
>Reporter: Matthias Bünger
>Priority: Major
>
> The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
> The [alpha-10 maven-model
> page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html]
> lists links to all current XSD, including the one for the 4.1.0 version of
> Maven 4:
> But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
> existing and throws a "404 Page not found" (as of 2023-12-26), while all
> others are working.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.codehaus.plexus:plexus-velocity from 1.2 to 2.1.0 [maven-plugin-tools]
dependabot[bot] opened a new pull request, #251: URL: https://github.com/apache/maven-plugin-tools/pull/251 Bumps [org.codehaus.plexus:plexus-velocity](https://github.com/codehaus-plexus/plexus-velocity) from 1.2 to 2.1.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-velocity/releases";>org.codehaus.plexus:plexus-velocity's releases. 2.1.0 Update component (https://redirect.github.com/codehaus-plexus/plexus-velocity/pull/67";>#67) https://github.com/cstamas";>@cstamas 📦 Dependency updates Bump org.junit.jupiter:junit-jupiter from 5.10.0 to 5.10.1 (https://redirect.github.com/codehaus-plexus/plexus-velocity/pull/63";>#63) https://github.com/dependabot";>@dependabot 👻 Maintenance Bump parent pom to plexus 16, update version to 2.1.0-SNAPSHOT (https://redirect.github.com/codehaus-plexus/plexus-velocity/pull/68";>#68) https://github.com/slachiewicz";>@slachiewicz Reuse plexus-pom action for CI (https://redirect.github.com/codehaus-plexus/plexus-velocity/pull/65";>#65) https://github.com/slachiewicz";>@slachiewicz Move to JUnit5 (https://redirect.github.com/codehaus-plexus/plexus-velocity/pull/60";>#60) https://github.com/slachiewicz";>@slachiewicz 2.0.0 What's Changed Upgrade Velocity Engine from 2.0 to 2.3 Full Changelog: https://github.com/codehaus-plexus/plexus-velocity/compare/plexus-velocity-1.3...plexus-velocity-2.0";>https://github.com/codehaus-plexus/plexus-velocity/compare/plexus-velocity-1.3...plexus-velocity-2.0 plexus-velocity-1.3 Upgrade to Velocity Engine 2.0 (https://redirect.github.com/codehaus-plexus/plexus-velocity/issues/11";>#11) https://github.com/slachiewicz";>@slachiewicz Bump commons-collections from 3.1 to 3.2.2 (https://redirect.github.com/codehaus-plexus/plexus-velocity/issues/8";>#8) https://github.com/dependabot";>@dependabot Commits https://github.com/codehaus-plexus/plexus-velocity/commit/7017cd2e43c0f7c357c1db617bfcded73e2b14cb";>7017cd2 [maven-release-plugin] prepare release plexus-velocity-2.1.0 https://github.com/codehaus-plexus/plexus-velocity/commit/59a98d41cca1273a80e4a17a55ab608a554d4f33";>59a98d4 Bump parent pom to plexus 16, update version to 2.1.0-SNAPSHOT https://github.com/codehaus-plexus/plexus-velocity/commit/e0c3648db003793f4fe3d79a0003b430a37427a6";>e0c3648 Merge pull request https://redirect.github.com/codehaus-plexus/plexus-velocity/issues/67";>#67 from codehaus-plexus/update-component https://github.com/codehaus-plexus/plexus-velocity/commit/2a90dbc8505e6a46296fbde2973f37a4dbad4d2f";>2a90dbc Update component https://github.com/codehaus-plexus/plexus-velocity/commit/f7d9d35af1a1db5ba876310d91ac4374c37fc4bc";>f7d9d35 Reuse plexus-pom action for CI https://github.com/codehaus-plexus/plexus-velocity/commit/265f2a3e72432ea42a7068e572b1fd8a810546da";>265f2a3 Bump actions/setup-java from 3 to 4 https://github.com/codehaus-plexus/plexus-velocity/commit/3bd53850a86edf2748415620c3165e5bba1b9d62";>3bd5385 Bump org.junit.jupiter:junit-jupiter from 5.10.0 to 5.10.1 https://github.com/codehaus-plexus/plexus-velocity/commit/ed5c0f36d9120a214b772d8cd8b6cf86d3c0807b";>ed5c0f3 Bump actions/checkout from 3 to 4 https://github.com/codehaus-plexus/plexus-velocity/commit/f08980a18c4421af26745f04903f9623bfd973f7";>f08980a Bump org.junit.jupiter:junit-jupiter from 5.9.3 to 5.10.0 https://github.com/codehaus-plexus/plexus-velocity/commit/49891e0e0393352b97f3457935288d6e170ed250";>49891e0 Move to JUnit5 Additional commits viewable in https://github.com/codehaus-plexus/plexus-velocity/compare/plexus-velocity-1.2...plexus-velocity-2.1.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will c
[jira] [Commented] (MPIR-451) Rename "Dependency Information" to "Maven Coordinates".
[ https://issues.apache.org/jira/browse/MPIR-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800483#comment-17800483 ] Elliotte Rusty Harold commented on MPIR-451: When I read "Maven Dependency Coordinates" I think coordinates of the dependencies of this project. "Maven Coordinates" suggests to me the coordinates of this project, which is what I want. I have occasionally used Maven coordinates to locate an artifact in a context where it is not a dependency. > Rename "Dependency Information" to "Maven Coordinates". > > > Key: MPIR-451 > URL: https://issues.apache.org/jira/browse/MPIR-451 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Major > > From a thread on commons-math where I noticed I was unable to find the Maven > coordinates for the project on the project's website: > The only way to get to that page is scroll about two thirds of the way down a > sidebar and click one of the four links that mention "dependencies" that > seems as likely to bring you to a list of commons-math's own dependencies > rather than how to add this project as a dependency. I'm a Maven comitter > who's spent way more time in the depths of Maven Project website generation > than 99.9% of Java programmers and I still couldn't find this the first time > I looked for it. That's de facto evidence that this information is not easy > to find. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7990) Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
[
https://issues.apache.org/jira/browse/MNG-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Bünger updated MNG-7990:
-
Description:
The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
The [alpha-10 maven-model
page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html] lists
links to all current XSD, including the one for the 4.1.0 version of Maven 4:
But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
existing and throws a "404 Page not found" (as of 2023-12-26), while all others
are working.
was:
The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
The [maven-model
page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html] lists
links to all current XSD, including the one for the 4.1.0 version of Maven 4:
But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
existing and throws a "404 Page not found" (as of 2023-12-26), while all others
are working.
> Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
> --
>
> Key: MNG-7990
> URL: https://issues.apache.org/jira/browse/MNG-7990
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-10
> Environment: Chrome
>Reporter: Matthias Bünger
>Priority: Major
>
> The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
> The [alpha-10 maven-model
> page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html]
> lists links to all current XSD, including the one for the 4.1.0 version of
> Maven 4:
> But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
> existing and throws a "404 Page not found" (as of 2023-12-26), while all
> others are working.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7990) Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
[
https://issues.apache.org/jira/browse/MNG-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Bünger updated MNG-7990:
-
Description:
The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
The [maven-model
page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html] lists
links to all current XSD, including the one for the 4.1.0 version of Maven 4:
But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
existing and throws a "404 Page not found" (as of 2023-12-26), while all others
are working.
was:
The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
The [maven-model
pagehttps://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html] lists
links to all current XSD, including the one for the 4.1.0 version of Maven 4:
But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
existing and throws a "404 Page not found" (as of 2023-12-26), while all others
are working.
> Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
> --
>
> Key: MNG-7990
> URL: https://issues.apache.org/jira/browse/MNG-7990
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-10
> Environment: Chrome
>Reporter: Matthias Bünger
>Priority: Major
>
> The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
> The [maven-model
> page|https://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html]
> lists links to all current XSD, including the one for the 4.1.0 version of
> Maven 4:
> But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
> existing and throws a "404 Page not found" (as of 2023-12-26), while all
> others are working.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7990) Link to Maven 4.1.0 XSD is broken / shows "404 Page not found"
Matthias Bünger created MNG-7990:
Summary: Link to Maven 4.1.0 XSD is broken / shows "404 Page not
found"
Key: MNG-7990
URL: https://issues.apache.org/jira/browse/MNG-7990
Project: Maven
Issue Type: Bug
Affects Versions: 4.0.0-alpha-10
Environment: Chrome
Reporter: Matthias Bünger
The link on the maven-model page to the Maven 4.1.0-XSD is broken/dead.
The [maven-model
pagehttps://maven.apache.org/ref/4.0.0-alpha-10/maven-model/maven.html] lists
links to all current XSD, including the one for the 4.1.0 version of Maven 4:
But the linked file: {{https://maven.apache.org/xsd/maven-4.1.0.xsd}} is not
existing and throws a "404 Page not found" (as of 2023-12-26), while all others
are working.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.apache.maven:maven-archiver from 3.6.0 to 3.6.1 [maven-acr-plugin]
dependabot[bot] opened a new pull request, #28: URL: https://github.com/apache/maven-acr-plugin/pull/28 Bumps [org.apache.maven:maven-archiver](https://github.com/apache/maven-archiver) from 3.6.0 to 3.6.1. Release notes Sourced from https://github.com/apache/maven-archiver/releases";>org.apache.maven:maven-archiver's releases. 3.6.1 What's Changed [MSHARED-1179] - Upgrade Parent to 39 by https://github.com/jorsol";>@jorsol in https://redirect.github.com/apache/maven-archiver/pull/27";>apache/maven-archiver#27 [MSHARED-1179] Back to 3.6.1-SNAPSHOT by https://github.com/elharo";>@elharo in https://redirect.github.com/apache/maven-archiver/pull/31";>apache/maven-archiver#31 Bump plexus-archiver from 1.0-alpha-7 to 3.6.0 in /src/test/resources by https://github.com/dependabot";>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/26";>apache/maven-archiver#26 Bump plexus-utils from 3.4.2 to 3.5.1 by https://github.com/dependabot";>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/30";>apache/maven-archiver#30 Bump plexus-io from 3.4.0 to 3.4.1 by https://github.com/dependabot";>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/28";>apache/maven-archiver#28 Bump junit-jupiter from 5.9.2 to 5.9.3 by https://github.com/dependabot";>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/32";>apache/maven-archiver#32 [MNG-6829] Replace StringUtils#isEmpty(String) & #isNotEmpty(String) by https://github.com/timtebeek";>@timtebeek in https://redirect.github.com/apache/maven-archiver/pull/34";>apache/maven-archiver#34 [MSHARED-1251] - Deprecate the JAR Index feature (JDK-8302819) by https://github.com/jorsol";>@jorsol in https://redirect.github.com/apache/maven-archiver/pull/33";>apache/maven-archiver#33 [MSHARED-1291] Bump org.junit:junit-bom from 5.9.3 to 5.10.0 by https://github.com/dependabot";>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/37";>apache/maven-archiver#37 [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver from 4.4.0 to 4.8.0 by https://github.com/dependabot";>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/39";>apache/maven-archiver#39 [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver from 3.6.0 to 4.8.0 in /src/test/resources by https://github.com/dependabot";>@dependabot in https://redirect.github.com/apache/maven-archiver/pull/38";>apache/maven-archiver#38 [MSHARED-1294] Upgrade Parent to 40 by https://github.com/slawekjaranowski";>@slawekjaranowski in https://redirect.github.com/apache/maven-archiver/pull/40";>apache/maven-archiver#40 [MSHARED-1293] Refresh download page by https://github.com/slawekjaranowski";>@slawekjaranowski in https://redirect.github.com/apache/maven-archiver/pull/41";>apache/maven-archiver#41 [MSHARED-1297] Prefer JDK features over plexus-utils, plexus-io by https://github.com/slawekjaranowski";>@slawekjaranowski in https://redirect.github.com/apache/maven-archiver/pull/42";>apache/maven-archiver#42 New Contributors https://github.com/dependabot";>@dependabot made their first contribution in https://redirect.github.com/apache/maven-archiver/pull/26";>apache/maven-archiver#26 https://github.com/timtebeek";>@timtebeek made their first contribution in https://redirect.github.com/apache/maven-archiver/pull/34";>apache/maven-archiver#34 https://github.com/slawekjaranowski";>@slawekjaranowski made their first contribution in https://redirect.github.com/apache/maven-archiver/pull/40";>apache/maven-archiver#40 Full Changelog: https://github.com/apache/maven-archiver/compare/maven-archiver-3.6.0...maven-archiver-3.6.1";>https://github.com/apache/maven-archiver/compare/maven-archiver-3.6.0...maven-archiver-3.6.1 Commits https://github.com/apache/maven-archiver/commit/1602aa4d149d318f992433ca9f0a660ff55e95c5";>1602aa4 [maven-release-plugin] prepare release maven-archiver-3.6.1 https://github.com/apache/maven-archiver/commit/482ec069255bb49e7ccaa1c50eb9ea5ed38c6cb4";>482ec06 [MSHARED-1297] Prefer JDK features over plexus-utils, plexus-io https://github.com/apache/maven-archiver/commit/87edd76eab050c75ac3bb7619678b32a5503e2e8";>87edd76 [MSHARED-1293] Refresh download page https://github.com/apache/maven-archiver/commit/b459dae7964ddabff60e2d166fef9828ca745b5a";>b459dae [MSHARED-1294] Upgrade Parent to 40 https://github.com/apache/maven-archiver/commit/c8a2edb7387a22f3b92a1f9d1103e3e679bdcdf6";>c8a2edb [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver in /src/test/resource... https://github.com/apache/maven-archiver/commit/0fcec499b3d484f7e493972d60908fed9e4a800b";>0fcec49 [MSHARED-1292] Bump org.codehaus.plexus:plexus-archiver from 4.4.0 to 4.8.0 (... https://github.com/apache/maven-archiver/commit/6528ddb5c047d4e883b18f894d46f9ccc0f381e2";>6528ddb [MSHARED-1291] Bump org.junit
[jira] [Commented] (MSHADE-385) Support for Multi-Release-JARs
[ https://issues.apache.org/jira/browse/MSHADE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800472#comment-17800472 ] Uwe Schindler commented on MSHADE-385: -- Hi, Please reopen this issue and fix it correctly. Maven Shade should automatically enable the multi release manifest entry if one of the original source jar files have it enabled. In Lucene we get questions and users open issues all the time when they use Maven Shade / Assembly plugins. Apache Lucene uses the Multi-Release JAR file feature extensively (in addition to Service Provider files and Java Modules). As somebody managing the pom file with dependencies has no idea if one of the dependencies uses a multi release JAR, there should be support in the tooling. The use can't know this. P.S.: if you shade a jar, any module-info.class files should be removed, too, because uber-jars cannot be modules anymore. Not sure if this is already fixed. A summary of all issues people fight with can be found here: https://github.com/apache/lucene/issues/12307#issuecomment-1803320694 (this issue was not about Maven, but we refer to this comment on all opened issues about this). Uwe > Support for Multi-Release-JARs > -- > > Key: MSHADE-385 > URL: https://issues.apache.org/jira/browse/MSHADE-385 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 3.3.0 >Reporter: Markus Karg >Priority: Major > > Maven Shade Plugin currently is unable to deal with multi-release JARs, hence > it always (and only) picks the lowest commen nominator (fallback) class. > > Actually the plugin should instead produce a multi-release JAR, hence pick > all class versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-498) Move section rendering to separate methods
[ https://issues.apache.org/jira/browse/MPLUGIN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800466#comment-17800466 ] ASF GitHub Bot commented on MPLUGIN-498: asfgit merged PR #248: URL: https://github.com/apache/maven-plugin-tools/pull/248 > Move section rendering to separate methods > -- > > Key: MPLUGIN-498 > URL: https://issues.apache.org/jira/browse/MPLUGIN-498 > Project: Maven Plugin Tools > Issue Type: Task > Components: Plugin Reporting Plugin >Affects Versions: 3.10.2 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: next-release > > > All of our reporting plugin renderers use a method per section to render > content for ease of overview. This reporting plugin's renderer should do the > same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-498) Move section rendering to separate methods
[ https://issues.apache.org/jira/browse/MPLUGIN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800467#comment-17800467 ] ASF GitHub Bot commented on MPLUGIN-498: asfgit merged PR #248: URL: https://github.com/apache/maven-plugin-tools/pull/248 > Move section rendering to separate methods > -- > > Key: MPLUGIN-498 > URL: https://issues.apache.org/jira/browse/MPLUGIN-498 > Project: Maven Plugin Tools > Issue Type: Task > Components: Plugin Reporting Plugin >Affects Versions: 3.10.2 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: next-release > > > All of our reporting plugin renderers use a method per section to render > content for ease of overview. This reporting plugin's renderer should do the > same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPLUGIN-498) Move section rendering to separate methods
[ https://issues.apache.org/jira/browse/MPLUGIN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPLUGIN-498. -- Resolution: Fixed Fixed with [fc412185093fcb24430191c4697e3217f822a967|https://gitbox.apache.org/repos/asf?p=maven-plugin-tools.git;a=commit;h=fc412185093fcb24430191c4697e3217f822a967]. > Move section rendering to separate methods > -- > > Key: MPLUGIN-498 > URL: https://issues.apache.org/jira/browse/MPLUGIN-498 > Project: Maven Plugin Tools > Issue Type: Task > Components: Plugin Reporting Plugin >Affects Versions: 3.10.2 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: next-release > > > All of our reporting plugin renderers use a method per section to render > content for ease of overview. This reporting plugin's renderer should do the > same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MPLUGIN-498] Move section rendering to separate methods [maven-plugin-tools]
asfgit merged PR #248: URL: https://github.com/apache/maven-plugin-tools/pull/248 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MPLUGIN-498] Move section rendering to separate methods [maven-plugin-tools]
asfgit merged PR #248: URL: https://github.com/apache/maven-plugin-tools/pull/248 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (DOXIA-699) Xhtml5Parser may emit sectionX() without sectionX_() when using both and
[
https://issues.apache.org/jira/browse/DOXIA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated DOXIA-699:
--
Summary: Xhtml5Parser may emit sectionX() without sectionX_() when using
both and (was: Xhtml5Parser may emit sectionX() without
sectionX_())
> Xhtml5Parser may emit sectionX() without sectionX_() when using both and
>
> ---
>
> Key: DOXIA-699
> URL: https://issues.apache.org/jira/browse/DOXIA-699
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M5
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M9
>
> Attachments: test.xhtml5
>
>
> Due to the logic in
> https://github.com/apache/maven-doxia/blob/37173794270ee68894aac0e252dcb87545770952/doxia-core/src/main/java/org/apache/maven/doxia/parser/Xhtml5BaseParser.java#L631
> there may calls of {{Sink.sectionX()}} without the according call of
> {{Sink.sectionX_()}}.
> The attached XHTML5 being parsed and then converted back through the Sink to
> XHTML5 is invalid (lacks one closing section tag).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (DOXIA-699) Xhtml5Parser may emit sectionX() without sectionX_()
[
https://issues.apache.org/jira/browse/DOXIA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved DOXIA-699.
---
Fix Version/s: 2.0.0
2.0.0-M9
Resolution: Fixed
Fixed in
https://github.com/apache/maven-doxia/commit/ef41ffaa282ba5ff19548f09979bcc3febf0feaa.
> Xhtml5Parser may emit sectionX() without sectionX_()
>
>
> Key: DOXIA-699
> URL: https://issues.apache.org/jira/browse/DOXIA-699
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M5
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-M9
>
> Attachments: test.xhtml5
>
>
> Due to the logic in
> https://github.com/apache/maven-doxia/blob/37173794270ee68894aac0e252dcb87545770952/doxia-core/src/main/java/org/apache/maven/doxia/parser/Xhtml5BaseParser.java#L631
> there may calls of {{Sink.sectionX()}} without the according call of
> {{Sink.sectionX_()}}.
> The attached XHTML5 being parsed and then converted back through the Sink to
> XHTML5 is invalid (lacks one closing section tag).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DOXIA-699) Xhtml5Parser may emit sectionX() without sectionX_()
[
https://issues.apache.org/jira/browse/DOXIA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800458#comment-17800458
]
ASF GitHub Bot commented on DOXIA-699:
--
kwin merged PR #162:
URL: https://github.com/apache/maven-doxia/pull/162
> Xhtml5Parser may emit sectionX() without sectionX_()
>
>
> Key: DOXIA-699
> URL: https://issues.apache.org/jira/browse/DOXIA-699
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.0.0-M5
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Attachments: test.xhtml5
>
>
> Due to the logic in
> https://github.com/apache/maven-doxia/blob/37173794270ee68894aac0e252dcb87545770952/doxia-core/src/main/java/org/apache/maven/doxia/parser/Xhtml5BaseParser.java#L631
> there may calls of {{Sink.sectionX()}} without the according call of
> {{Sink.sectionX_()}}.
> The attached XHTML5 being parsed and then converted back through the Sink to
> XHTML5 is invalid (lacks one closing section tag).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [DOXIA-699] Correctly generate sections for headings [maven-doxia]
kwin merged PR #162: URL: https://github.com/apache/maven-doxia/pull/162 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-1347) maven-dependency-plugin ignores class of object passed as a parameter to method references
[
https://issues.apache.org/jira/browse/MSHARED-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800454#comment-17800454
]
ASF GitHub Bot commented on MSHARED-1347:
-
vbreivik commented on PR #102:
URL:
https://github.com/apache/maven-dependency-analyzer/pull/102#issuecomment-1869410488
> @vbreivik please fix formatting issues
@slawekjaranowski done.
Guess spotless tricked me, it does not run on java 8.
Switched to 17 and ran spotless:apply and pushed
> maven-dependency-plugin ignores class of object passed as a parameter to
> method references
> --
>
> Key: MSHARED-1347
> URL: https://issues.apache.org/jira/browse/MSHARED-1347
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.2
>Reporter: Vidar Breivik
>Priority: Minor
>
> Text copied from [MDEP-576|https://issues.apache.org/jira/browse/MDEP-576]
> Hi there, i created a project on
> [github|https://github.com/vdergachev/dependency-plugin-vs-java-lambda] that
> can help you to reproduce the issue. Just clone it and make
> {code:java}
> mvn clean install{code}
> In my case plugin ignored Server class from jetty-server.jar and a as result
> i got message
> {code:java}
> Unused declared dependencies found{code}
>
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1347] - Include invoke dynamic bootstrap types in analysis [maven-dependency-analyzer]
vbreivik commented on PR #102: URL: https://github.com/apache/maven-dependency-analyzer/pull/102#issuecomment-1869410488 > @vbreivik please fix formatting issues @slawekjaranowski done. Guess spotless tricked me, it does not run on java 8. Switched to 17 and ran spotless:apply and pushed -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MASSEMBLY-1008) Assembly plugin handles scopes wrongly
[ https://issues.apache.org/jira/browse/MASSEMBLY-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski reassigned MASSEMBLY-1008: -- Assignee: Slawomir Jaranowski > Assembly plugin handles scopes wrongly > -- > > Key: MASSEMBLY-1008 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-1008 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: dependencySet >Reporter: Tamas Cservenak >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.7.0 > > > This affects all assembly releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MASSEMBLY-1008) Assembly plugin handles scopes wrongly
[ https://issues.apache.org/jira/browse/MASSEMBLY-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MASSEMBLY-1008: --- Fix Version/s: 3.7.0 > Assembly plugin handles scopes wrongly > -- > > Key: MASSEMBLY-1008 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-1008 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: dependencySet >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.7.0 > > > This affects all assembly releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MASSEMBLY-992) Facility to define assembly descriptor in body of POM
[
https://issues.apache.org/jira/browse/MASSEMBLY-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed MASSEMBLY-992.
-
Resolution: Fixed
> Facility to define assembly descriptor in body of POM
> -
>
> Key: MASSEMBLY-992
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-992
> Project: Maven Assembly Plugin
> Issue Type: New Feature
>Reporter: Garret Wilson
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.7.0
>
>
> The Maven Assembly Plugin allows custom descriptors to be defined, but only
> in an external file. Please add the capability to define the descriptor in
> the body of the POM itself.
> Requiring a separate descriptor file makes it almost impossible to declare an
> assembly in a parent POM so that it can be inherited by child POMs. The
> documentation describe a way to [share
> descriptors|https://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html],
> but it is complex and doesn't obviously support Maven property interpolation.
> Without this facility, in order to easily inherit an assembly from a parent
> POM, I'm currently resorting to workaround involving AntRun to generate an
> assembly descriptor on the fly. See [this
> {{pom.xml}}|https://github.com/globalmentor/globalmentor-root/blob/main/pom.xml].
> It's pretty convoluted and tedious to get right. In addition, it has to be
> placed in a phase that is guaranteed to run before the execution of the Maven
> Assembly Plugin itself.
> {code:xml}
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
>
> generate-bin-assembly-descriptor
> prepare-package
>
> run
>
>
> ${_isSkipGenerateExe}
>
> encoding="UTF-8">
>
>
>
>
>
>
>
> {code}
> This was requested and finally implemented for Versions Maven Plugin; see
> [#258|https://github.com/mojohaus/versions/issues/258] and
> [#684|https://github.com/mojohaus/versions/issues/684], along with [_Versions
> Maven Plugin rules that are
> inheritable_|https://stackoverflow.com/q/72416739] on Stack Overflow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHARED-1347) maven-dependency-plugin ignores class of object passed as a parameter to method references
[
https://issues.apache.org/jira/browse/MSHARED-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800445#comment-17800445
]
ASF GitHub Bot commented on MSHARED-1347:
-
slawekjaranowski commented on PR #102:
URL:
https://github.com/apache/maven-dependency-analyzer/pull/102#issuecomment-1869371499
@vbreivik please fix formatting issues
> maven-dependency-plugin ignores class of object passed as a parameter to
> method references
> --
>
> Key: MSHARED-1347
> URL: https://issues.apache.org/jira/browse/MSHARED-1347
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.2
>Reporter: Vidar Breivik
>Priority: Minor
>
> Text copied from [MDEP-576|https://issues.apache.org/jira/browse/MDEP-576]
> Hi there, i created a project on
> [github|https://github.com/vdergachev/dependency-plugin-vs-java-lambda] that
> can help you to reproduce the issue. Just clone it and make
> {code:java}
> mvn clean install{code}
> In my case plugin ignored Server class from jetty-server.jar and a as result
> i got message
> {code:java}
> Unused declared dependencies found{code}
>
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1347] - Include invoke dynamic bootstrap types in analysis [maven-dependency-analyzer]
slawekjaranowski commented on PR #102: URL: https://github.com/apache/maven-dependency-analyzer/pull/102#issuecomment-1869371499 @vbreivik please fix formatting issues -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
