[GitHub] [maven-artifact-plugin] hboutemy commented on pull request #24: Update maven-shared-utils to 3.4.2
hboutemy commented on PR #24: URL: https://github.com/apache/maven-artifact-plugin/pull/24#issuecomment-1741980366 thank you -- 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
[GitHub] [maven-parent] hboutemy opened a new pull request, #139: [MPOM-427] use version.artifactId property for dependency versions (like plugins)
hboutemy opened a new pull request, #139: URL: https://github.com/apache/maven-parent/pull/139 finding while doing that: - it happens that multiple components shared the same version: which artifactId should be promoted as the leading? or should we really let every artifactId have its own version defined separately? - it even happens that the version is shared with a plugin (here it happens with sisu, this also can happen with plugin-tools vs plugin annotations) some choices have been done in this PR clearly, the "rule" cannot be a strict technical rule but more guidelines to be adapted to these edge cases -- 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-429) Support development with Java 21 (palantirJavaFormat)
Sylwester Lachiewicz created MPOM-429: - Summary: Support development with Java 21 (palantirJavaFormat) Key: MPOM-429 URL: https://issues.apache.org/jira/browse/MPOM-429 Project: Maven POMs Issue Type: Improvement Components: maven Reporter: Sylwester Lachiewicz Fix For: MAVEN-41 Spotless plugin with palantirJavaFormat extension has issues with Java 21 and that was fixed with upgrade palantirJavaFormat to version 2.36.0+ [https://github.com/diffplug/spotless/issues/1819#issuecomment-1726986315.] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-artifact-plugin] hboutemy commented on pull request #25: move plexus utils to test scopePlexus
hboutemy commented on PR #25: URL: https://github.com/apache/maven-artifact-plugin/pull/25#issuecomment-1741979278 a good little move, thank you: extracting plexus-xml has a nice side effect I did not expect but that is very good -- 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-427) use version.artifactId property for dependency versions (like plugins)
Herve Boutemy created MPOM-427:
--
Summary: use version.artifactId property for dependency versions
(like plugins)
Key: MPOM-427
URL: https://issues.apache.org/jira/browse/MPOM-427
Project: Maven POMs
Issue Type: Task
Components: maven
Affects Versions: MAVEN-40
Reporter: Herve Boutemy
Fix For: MAVEN-41
we defined {{version.}} naming convention in MPOM-289
it would make sense to keep the same convention for dependencies versions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-parent] slachiewicz commented on pull request #132: Bump plexus-xml from 4.0.0 to 4.0.2
slachiewicz commented on PR #132: URL: https://github.com/apache/maven-parent/pull/132#issuecomment-1742022034 @dependabot ignore this major version See #138 138 -- 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
[GitHub] [maven-parent] dependabot[bot] closed pull request #132: Bump plexus-xml from 4.0.0 to 4.0.2
dependabot[bot] closed pull request #132: Bump plexus-xml from 4.0.0 to 4.0.2 URL: https://github.com/apache/maven-parent/pull/132 -- 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
[GitHub] [maven-parent] dependabot[bot] commented on pull request #132: Bump plexus-xml from 4.0.0 to 4.0.2
dependabot[bot] commented on PR #132: URL: https://github.com/apache/maven-parent/pull/132#issuecomment-1742022045 OK, I won't notify you about version 4.x.x again, unless you re-open this PR. -- 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
[GitHub] [maven-artifact-plugin] hboutemy merged pull request #24: Update maven-shared-utils to 3.4.2
hboutemy merged PR #24: URL: https://github.com/apache/maven-artifact-plugin/pull/24 -- 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] (MPOM-426) downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3
[ https://issues.apache.org/jira/browse/MPOM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-426: --- Summary: downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3 (was: downgrade plexus-xml to 3.0.0: 4.0..0 is incompatible with Maven 3) > downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3 > - > > Key: MPOM-426 > URL: https://issues.apache.org/jira/browse/MPOM-426 > Project: Maven POMs > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-40 >Reporter: Herve Boutemy >Priority: Major > Fix For: MAVEN-41 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPOM-426) downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3
[ https://issues.apache.org/jira/browse/MPOM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-426: --- Description: upgrade was done in https://github.com/apache/maven-parent/pull/123 > downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3 > - > > Key: MPOM-426 > URL: https://issues.apache.org/jira/browse/MPOM-426 > Project: Maven POMs > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-40 >Reporter: Herve Boutemy >Priority: Major > Fix For: MAVEN-41 > > > upgrade was done in https://github.com/apache/maven-parent/pull/123 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPOM-426) downgrade plexus-xml to 3.0.0: 4.0..0 is incompatible with Maven 3
Herve Boutemy created MPOM-426: -- Summary: downgrade plexus-xml to 3.0.0: 4.0..0 is incompatible with Maven 3 Key: MPOM-426 URL: https://issues.apache.org/jira/browse/MPOM-426 Project: Maven POMs Issue Type: Improvement Components: maven Affects Versions: MAVEN-40 Reporter: Herve Boutemy Fix For: MAVEN-41 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPOM-289) Use properties to define the versions of plugins
[
https://issues.apache.org/jira/browse/MPOM-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770824#comment-17770824
]
Herve Boutemy commented on MPOM-289:
FTR naming convention finally implemented is {{version.maven-xxx-plugin}} =
{{version}} dot {{artifactId (eventually contains dash)}}
> Use properties to define the versions of plugins
>
>
> Key: MPOM-289
> URL: https://issues.apache.org/jira/browse/MPOM-289
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-30
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: ASF-30
>
>
> Benefit:
> - properties are propagated to child projects and can be used eg in
> integration test
> - easier versions override
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPOM-425) Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.39.0
[ https://issues.apache.org/jira/browse/MPOM-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-425: -- Summary: Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.39.0 (was: Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0) > Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.39.0 > -- > > Key: MPOM-425 > URL: https://issues.apache.org/jira/browse/MPOM-425 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: maven >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: MAVEN-41 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPOM-428) Bump com.diffplug.spotless:spotless-maven-plugin from 2.39.0 to 2.40.0
Sylwester Lachiewicz created MPOM-428: - Summary: Bump com.diffplug.spotless:spotless-maven-plugin from 2.39.0 to 2.40.0 Key: MPOM-428 URL: https://issues.apache.org/jira/browse/MPOM-428 Project: Maven POMs Issue Type: Dependency upgrade Components: maven Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: MAVEN-41 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-parent] hboutemy commented on a diff in pull request #139: [MPOM-427] use version.artifactId property for dependency versions (like plugins)
hboutemy commented on code in PR #139:
URL: https://github.com/apache/maven-parent/pull/139#discussion_r1342109223
##
pom.xml:
##
@@ -956,22 +956,22 @@ under the License.
org.eclipse.sisu
org.eclipse.sisu.inject
-${sisuVersion}
+${sisu-maven-plugin}
Review Comment:
oh yes, typo, I will fix...
--
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
[GitHub] [maven-parent] hboutemy opened a new pull request, #138: [MPOM-426] downgrade plexus-xml to 3.0.0 as 4 is incompatible with Maven 3
hboutemy opened a new pull request, #138: URL: https://github.com/apache/maven-parent/pull/138 supercedes #123 -- 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] (MPOM-425) Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0
[ https://issues.apache.org/jira/browse/MPOM-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-425: -- Summary: Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0 (was: Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.39.0) > Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0 > -- > > Key: MPOM-425 > URL: https://issues.apache.org/jira/browse/MPOM-425 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: maven >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: MAVEN-41 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7873) Export missing Xpp3DomBuilder
[ https://issues.apache.org/jira/browse/MNG-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770814#comment-17770814 ] Herve Boutemy commented on MNG-7873: yes, fixed by plexus-xml 3.0.0: that's what is used by maven-artifact-plugin 3.5.0 release currently in vote https://maven.apache.org/plugins-archives/maven-artifact-plugin-LATEST/dependencies.html no change needed in Maven 3 > Export missing Xpp3DomBuilder > - > > Key: MNG-7873 > URL: https://issues.apache.org/jira/browse/MNG-7873 > Project: Maven > Issue Type: Bug > Components: Core >Reporter: Guillaume Nodet >Priority: Major > Fix For: 3.9.5 > > > See https://lists.apache.org/thread/ltd1g1dbv0lqqdw5q941gmrkfyn6m87m -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-parent] slawekjaranowski commented on a diff in pull request #139: [MPOM-427] use version.artifactId property for dependency versions (like plugins)
slawekjaranowski commented on code in PR #139:
URL: https://github.com/apache/maven-parent/pull/139#discussion_r1342104472
##
pom.xml:
##
@@ -994,7 +994,7 @@ under the License.
org.eclipse.sisu
sisu-maven-plugin
- ${sisuVersion}
+ ${sisu-maven-plugin}
Review Comment:
and here is `version.sisu-maven-plugin`
##
pom.xml:
##
@@ -956,22 +956,22 @@ under the License.
org.eclipse.sisu
org.eclipse.sisu.inject
-${sisuVersion}
+${sisu-maven-plugin}
Review Comment:
there is `version.sisu-maven-plugin`
--
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] [Comment Edited] (MPOM-289) Use properties to define the versions of plugins
[
https://issues.apache.org/jira/browse/MPOM-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770824#comment-17770824
]
Michael Osipov edited comment on MPOM-289 at 10/1/23 9:28 AM:
--
FTR naming convention finally implemented is {{version.maven-xxx-plugin}} =
{{version}} dot {{artifactId}} (eventually contains hyphen)
was (Author: hboutemy):
FTR naming convention finally implemented is {{version.maven-xxx-plugin}} =
{{version}} dot {{artifactId (eventually contains dash)}}
> Use properties to define the versions of plugins
>
>
> Key: MPOM-289
> URL: https://issues.apache.org/jira/browse/MPOM-289
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-30
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: ASF-30
>
>
> Benefit:
> - properties are propagated to child projects and can be used eg in
> integration test
> - easier versions override
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MPOM-425) Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0
[ https://issues.apache.org/jira/browse/MPOM-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPOM-425: -- Summary: Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0 (was: Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.39.0) > Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0 > -- > > Key: MPOM-425 > URL: https://issues.apache.org/jira/browse/MPOM-425 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: maven >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: MAVEN-41 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Deleted] (MPOM-428) Bump com.diffplug.spotless:spotless-maven-plugin from 2.39.0 to 2.40.0
[ https://issues.apache.org/jira/browse/MPOM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz deleted MPOM-428: -- > Bump com.diffplug.spotless:spotless-maven-plugin from 2.39.0 to 2.40.0 > -- > > Key: MPOM-428 > URL: https://issues.apache.org/jira/browse/MPOM-428 > Project: Maven POMs > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-analyzer] elharo opened a new pull request, #96: update to commons-io 2.14.0
elharo opened a new pull request, #96: URL: https://github.com/apache/maven-dependency-analyzer/pull/96 (no comment) -- 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
[GitHub] [maven-parent] slachiewicz merged pull request #137: [MPOM-425] Bump com.diffplug.spotless:spotless-maven-plugin from 2.39.0 to 2.40.0
slachiewicz merged PR #137: URL: https://github.com/apache/maven-parent/pull/137 -- 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] (MSKINS-170) Allow to show name as headline in addition to bannerLeft
[ https://issues.apache.org/jira/browse/MSKINS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSKINS-170: - Assignee: Michael Osipov > Allow to show name as headline in addition to bannerLeft > > > Key: MSKINS-170 > URL: https://issues.apache.org/jira/browse/MSKINS-170 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.9 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Attachments: screenshot-1.png > > > Currently there is a fallback with text in case no bannerLeft is configured: > https://github.com/apache/maven-fluido-skin/blob/f966972c504c8a01a5d7a203de6438464877a8bd/src/main/resources/META-INF/maven/site.vm#L188. > It would be nice to optionally show that next to the banner. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSKINS-235) wrong META-INF/LICENSE and META-INF/NOTICE in release jar
[ https://issues.apache.org/jira/browse/MSKINS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-235: -- Fix Version/s: fluido-2.0.0-M8 > wrong META-INF/LICENSE and META-INF/NOTICE in release jar > - > > Key: MSKINS-235 > URL: https://issues.apache.org/jira/browse/MSKINS-235 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-2.0.0-M5, fluido-2.0.0-M6, fluido-2.0.0-M7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: fluido-2.0.0-M8 > > > seen as testing reproducible builds: > [https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/skins/fluido/README.md] > reference jar has content that seems to be generated from remote-resources > with Jar Resource Bundle https://maven.apache.org/apache-resource-bundles/jar/ > but rebuild has content configured in pom.xml to copy content from Git: > https://github.com/apache/maven-fluido-skin/ > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSKINS-170) Allow to show name as headline in addition to bannerLeft
[ https://issues.apache.org/jira/browse/MSKINS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-170: -- Fix Version/s: fluido-2.0.0-M8 > Allow to show name as headline in addition to bannerLeft > > > Key: MSKINS-170 > URL: https://issues.apache.org/jira/browse/MSKINS-170 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.9 >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-2.0.0-M8 > > Attachments: screenshot-1.png > > > Currently there is a fallback with text in case no bannerLeft is configured: > https://github.com/apache/maven-fluido-skin/blob/f966972c504c8a01a5d7a203de6438464877a8bd/src/main/resources/META-INF/maven/site.vm#L188. > It would be nice to optionally show that next to the banner. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSKINS-235) wrong META-INF/LICENSE and META-INF/NOTICE in release jar
[ https://issues.apache.org/jira/browse/MSKINS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSKINS-235: - Assignee: Herve Boutemy > wrong META-INF/LICENSE and META-INF/NOTICE in release jar > - > > Key: MSKINS-235 > URL: https://issues.apache.org/jira/browse/MSKINS-235 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-2.0.0-M5, fluido-2.0.0-M6, fluido-2.0.0-M7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > > seen as testing reproducible builds: > [https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/skins/fluido/README.md] > reference jar has content that seems to be generated from remote-resources > with Jar Resource Bundle https://maven.apache.org/apache-resource-bundles/jar/ > but rebuild has content configured in pom.xml to copy content from Git: > https://github.com/apache/maven-fluido-skin/ > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPOM-426) downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3
[ https://issues.apache.org/jira/browse/MPOM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPOM-426. -- Assignee: Herve Boutemy Resolution: Fixed > downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3 > - > > Key: MPOM-426 > URL: https://issues.apache.org/jira/browse/MPOM-426 > Project: Maven POMs > Issue Type: Improvement > Components: maven >Affects Versions: MAVEN-40 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: MAVEN-41 > > > upgrade was done in https://github.com/apache/maven-parent/pull/123 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSKINS-235) wrong META-INF/LICENSE and META-INF/NOTICE in release jar
[ https://issues.apache.org/jira/browse/MSKINS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSKINS-235. - Resolution: Fixed Fixed with [85fa18cd3525ac961bf71e7aea0badd3fd08feaf|https://gitbox.apache.org/repos/asf?p=maven-fluido-skin.git;a=commit;h=85fa18cd3525ac961bf71e7aea0badd3fd08feaf]. > wrong META-INF/LICENSE and META-INF/NOTICE in release jar > - > > Key: MSKINS-235 > URL: https://issues.apache.org/jira/browse/MSKINS-235 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-2.0.0-M5, fluido-2.0.0-M6, fluido-2.0.0-M7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: fluido-2.0.0-M8 > > > seen as testing reproducible builds: > [https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/skins/fluido/README.md] > reference jar has content that seems to be generated from remote-resources > with Jar Resource Bundle https://maven.apache.org/apache-resource-bundles/jar/ > but rebuild has content configured in pom.xml to copy content from Git: > https://github.com/apache/maven-fluido-skin/ > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1298) MIssing site report should be detected
[
https://issues.apache.org/jira/browse/MSHARED-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHARED-1298:
Fix Version/s: maven-reporting-exec-2.0.0-M10
> MIssing site report should be detected
> --
>
> Key: MSHARED-1298
> URL: https://issues.apache.org/jira/browse/MSHARED-1298
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-reporting-exec
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-exec-2.0.0-M10
>
>
> When we define as report plugin which not contains any report Mojo
> we should inform by warning or even break a build.
> eg:
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-plugin-plugin
>
>
>
> {code}
> is silently skipped and no report is generated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSHARED-1298) Missing site report should be detected
[
https://issues.apache.org/jira/browse/MSHARED-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHARED-1298:
Summary: Missing site report should be detected (was: MIssing site report
should be detected)
> Missing site report should be detected
> --
>
> Key: MSHARED-1298
> URL: https://issues.apache.org/jira/browse/MSHARED-1298
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-reporting-exec
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-exec-2.0.0-M10
>
>
> When we define as report plugin which not contains any report Mojo
> we should inform by warning or even break a build.
> eg:
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-plugin-plugin
>
>
>
> {code}
> is silently skipped and no report is generated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-jar-plugin] dependabot[bot] commented on pull request #61: Bump plexus-utils from 3.4.2 to 3.5.1
dependabot[bot] commented on PR #61: URL: https://github.com/apache/maven-jar-plugin/pull/61#issuecomment-1742093932 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
[GitHub] [maven-dependency-analyzer] elharo merged pull request #96: update to commons-io 2.14.0
elharo merged PR #96: URL: https://github.com/apache/maven-dependency-analyzer/pull/96 -- 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
[GitHub] [maven-jar-plugin] elharo closed pull request #61: Bump plexus-utils from 3.4.2 to 3.5.1
elharo closed pull request #61: Bump plexus-utils from 3.4.2 to 3.5.1 URL: https://github.com/apache/maven-jar-plugin/pull/61 -- 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] (DOXIASITETOOLS-254) Clarify inconsistencies in Doxia site model
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-254.
-
Resolution: Fixed
Addressed with DOXIASITETOOLS-311.
> Clarify inconsistencies in Doxia site model
> ---
>
> Key: DOXIASITETOOLS-254
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-254
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site model
>Affects Versions: 1.11.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Labels: doxia-2.0.0-stack
> Fix For: 2.0.0-M12
>
>
> [https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
> bannerLeft/bannerRight (see also DOXIASITETOOLS-253):
> * Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
> should they appear? Why is no {{position}} like with other similar elements
> (logo, item)?
> * Does {{href}} truly only apply to the image?
> * Why is there no {{target}}?
> * Must {{title}}/{{alt}} only be used on the image?
> * Why not apply here the same logic as with the other imaged elements?
> * Why {{src}} instead of {{img}} like the rest?
> * Why does it use subelements and not attributes like the rest?
> logo/link item/menu/menu item:
> * Does {{href}} truly only apply to the text? (different to banner)
> * Must {{title}}/{{alt}} only be used on the image?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (DOXIASITETOOLS-174) rename site.xml root tag from "project" to "site"
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned DOXIASITETOOLS-174:
-
Assignee: Michael Osipov
> rename site.xml root tag from "project" to "site"
> -
>
> Key: DOXIASITETOOLS-174
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-174
> Project: Maven Doxia Sitetools
> Issue Type: Wish
> Components: Site model
>Affects Versions: 1.7.4
>Reporter: Herve Boutemy
>Assignee: Michael Osipov
>Priority: Major
> Labels: doxia-2.0.0-stack
>
> when looking at [decoration model
> descriptor|http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.7/doxia-decoration-model/decoration.html],
> naming the root element as {{project}} (like for {{pom.xml}}) is misleading
> if the root element could be renamed as {{doxia-decoration}}, the obvious
> (this descriptor is about site decoration, done with Doxia) could perhaps
> become obvious
> (in IT, calling everything a "project" is an issue...)
> I know that this change of xsd schema will break compatibility, but I think
> it can really make a big difference in usability (and I should have had this
> idea for Doxia Sitetools 1.7, when we already made some breaking changes...)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-253) Clarify "border", "width" and "height" for Banner and LinkItem
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-253. - Fix Version/s: 2.0.0-M12 Resolution: Fixed Fixed with DOXIASITETOOLS-311. > Clarify "border", "width" and "height" for Banner and LinkItem > -- > > Key: DOXIASITETOOLS-253 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-253 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Site model >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Labels: doxia-2.0.0-stack > Fix For: 2.0.0-M12 > > > The elements "border", "width" and "height" in > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_bannerLeft > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_bannerRight > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_item > have a very vague description (same in renamed doxia-site-model > https://maven.apache.org/doxia/doxia-sitetools/doxia-site-model/site.html ). > It should be clarified with regards to whether > 1. this is the format of the same named CSS properties > (https://www.w3.org/TR/CSS2/box.html#border-properties, > https://www.w3.org/TR/CSS2/visudet.html#the-width-property and > https://www.w3.org/TR/CSS2/visudet.html#the-height-property) > 2. or the HTML4 attributes > (https://www.w3.org/TR/html401/struct/objects.html#h-13.7.1 and > https://www.w3.org/TR/html401/struct/objects.html#h-13.7.3) > 3. or another custom format. > Currently the skins use the values as-is for either CSS property or HTML > attribute, but although they are named the same, the supported values differ > a lot. > This came up in the context of > https://github.com/apache/maven-fluido-skin/pull/23#discussion_r866169720. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-174) rename site.xml root tag from "project" to "site"
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-174.
-
Fix Version/s: 2.0.0-M12
Resolution: Fixed
Fixed with DOXIASITETOOLS-311.
> rename site.xml root tag from "project" to "site"
> -
>
> Key: DOXIASITETOOLS-174
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-174
> Project: Maven Doxia Sitetools
> Issue Type: Wish
> Components: Site model
>Affects Versions: 1.7.4
>Reporter: Herve Boutemy
>Assignee: Michael Osipov
>Priority: Major
> Labels: doxia-2.0.0-stack
> Fix For: 2.0.0-M12
>
>
> when looking at [decoration model
> descriptor|http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.7/doxia-decoration-model/decoration.html],
> naming the root element as {{project}} (like for {{pom.xml}}) is misleading
> if the root element could be renamed as {{doxia-decoration}}, the obvious
> (this descriptor is about site decoration, done with Doxia) could perhaps
> become obvious
> (in IT, calling everything a "project" is an issue...)
> I know that this change of xsd schema will break compatibility, but I think
> it can really make a big difference in usability (and I should have had this
> idea for Doxia Sitetools 1.7, when we already made some breaking changes...)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-311) Rework and simplify the site model
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-311. - Resolution: Fixed Fixed with [afcd656218da6d8d8cfd7a89d389cdd3aa96be8e|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=afcd656218da6d8d8cfd7a89d389cdd3aa96be8e]. > Rework and simplify the site model > -- > > Key: DOXIASITETOOLS-311 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-311 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Site model >Affects Versions: 2.0.0-M11 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Labels: doxia-2.0.0-stack > Fix For: 2.0.0-M12 > > > For a long time the current site model has a lot of problems/inconsitencies: > * Image attributes mixed into text nodes > * Incomplete information > * Images added to nodes which do not make sense > * Wrong root element > * Misuse of title attribute > We need to resolve inconsistencies and drop unneeded content. See also linked > issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-254) Clarify inconsistencies in Doxia site model
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-254:
--
Fix Version/s: 2.0.0-M12
> Clarify inconsistencies in Doxia site model
> ---
>
> Key: DOXIASITETOOLS-254
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-254
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site model
>Affects Versions: 1.11.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Labels: doxia-2.0.0-stack
> Fix For: 2.0.0-M12
>
>
> [https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
> bannerLeft/bannerRight (see also DOXIASITETOOLS-253):
> * Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
> should they appear? Why is no {{position}} like with other similar elements
> (logo, item)?
> * Does {{href}} truly only apply to the image?
> * Why is there no {{target}}?
> * Must {{title}}/{{alt}} only be used on the image?
> * Why not apply here the same logic as with the other imaged elements?
> * Why {{src}} instead of {{img}} like the rest?
> * Why does it use subelements and not attributes like the rest?
> logo/link item/menu/menu item:
> * Does {{href}} truly only apply to the text? (different to banner)
> * Must {{title}}/{{alt}} only be used on the image?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-doxia-sitetools] asfgit closed pull request #110: [DOXIASITETOOLS-311] Rework and simplify the site model
asfgit closed pull request #110: [DOXIASITETOOLS-311] Rework and simplify the site model URL: https://github.com/apache/maven-doxia-sitetools/pull/110 -- 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] (DOXIASITETOOLS-311) Rework and simplify the site model
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770903#comment-17770903 ] ASF GitHub Bot commented on DOXIASITETOOLS-311: --- asfgit closed pull request #110: [DOXIASITETOOLS-311] Rework and simplify the site model URL: https://github.com/apache/maven-doxia-sitetools/pull/110 > Rework and simplify the site model > -- > > Key: DOXIASITETOOLS-311 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-311 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Site model >Affects Versions: 2.0.0-M11 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Labels: doxia-2.0.0-stack > Fix For: 2.0.0-M12 > > > For a long time the current site model has a lot of problems/inconsitencies: > * Image attributes mixed into text nodes > * Incomplete information > * Images added to nodes which do not make sense > * Wrong root element > * Misuse of title attribute > We need to resolve inconsistencies and drop unneeded content. See also linked > issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1310) Upgrade to Parent 40
[ https://issues.apache.org/jira/browse/MSHARED-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1310. --- Resolution: Fixed Fixed with [c699de4a35623d473189ddee818fd08ef410b6d5|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=c699de4a35623d473189ddee818fd08ef410b6d5]. > Upgrade to Parent 40 > > > Key: MSHARED-1310 > URL: https://issues.apache.org/jira/browse/MSHARED-1310 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0-M10 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-site] cstamas opened a new pull request, #458: Maven 3.9.5 release notes
cstamas opened a new pull request, #458: URL: https://github.com/apache/maven-site/pull/458 (no comment) -- 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] (MSKINS-235) wrong META-INF/LICENSE and META-INF/NOTICE in release jar
[ https://issues.apache.org/jira/browse/MSKINS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770880#comment-17770880 ] ASF GitHub Bot commented on MSKINS-235: --- asfgit closed pull request #54: [MSKINS-235] use older plugin giving consistent out on Windows URL: https://github.com/apache/maven-fluido-skin/pull/54 > wrong META-INF/LICENSE and META-INF/NOTICE in release jar > - > > Key: MSKINS-235 > URL: https://issues.apache.org/jira/browse/MSKINS-235 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-2.0.0-M5, fluido-2.0.0-M6, fluido-2.0.0-M7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: fluido-2.0.0-M8 > > > seen as testing reproducible builds: > [https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/skins/fluido/README.md] > reference jar has content that seems to be generated from remote-resources > with Jar Resource Bundle https://maven.apache.org/apache-resource-bundles/jar/ > but rebuild has content configured in pom.xml to copy content from Git: > https://github.com/apache/maven-fluido-skin/ > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1310) Upgrade to Parent 40
Michael Osipov created MSHARED-1310: --- Summary: Upgrade to Parent 40 Key: MSHARED-1310 URL: https://issues.apache.org/jira/browse/MSHARED-1310 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-exec Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-exec-2.0.0-M10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOURCES-278) Regression - Changed copy behaviour if file already exists
[ https://issues.apache.org/jira/browse/MRESOURCES-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MRESOURCES-278: - Description: With MSHARED-966 the behavior for the maven-resources-plugin changed dramatically. Now an exception is thown if a file already exists. Before it was only overwritten if newer and no exception was thrown. The new behavior breaks many builds. If this new behavior is a feature the plugin site should be updated with a big (!) warning to everyone. was: With MSHARED-966 the behavior for the maven-resources-plugin changed dramatically. Now an exception is thown if an file already exists. Before it was only overwritten if newer an no exception was thrown. The new behavior breaks many builds. If this new behavior is a feature the plugin site should be updated with a big (!) warning to everyone. > Regression - Changed copy behaviour if file already exists > -- > > Key: MRESOURCES-278 > URL: https://issues.apache.org/jira/browse/MRESOURCES-278 > Project: Maven Resources Plugin > Issue Type: Bug > Components: copy >Affects Versions: 3.3.0 >Reporter: Georg Tsakumagos >Priority: Critical > > With MSHARED-966 the behavior for the maven-resources-plugin changed > dramatically. > Now an exception is thown if a file already exists. > Before it was only overwritten if newer and no exception was thrown. > The new behavior breaks many builds. If this new behavior is a feature the > plugin site should be updated with a big (!) warning to everyone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-253) Clarify "border", "width" and "height" for Banner and LinkItem
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-253: -- Labels: (was: doxia-2.0.0-stack) > Clarify "border", "width" and "height" for Banner and LinkItem > -- > > Key: DOXIASITETOOLS-253 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-253 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Site model >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M12 > > > The elements "border", "width" and "height" in > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_bannerLeft > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_bannerRight > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_item > have a very vague description (same in renamed doxia-site-model > https://maven.apache.org/doxia/doxia-sitetools/doxia-site-model/site.html ). > It should be clarified with regards to whether > 1. this is the format of the same named CSS properties > (https://www.w3.org/TR/CSS2/box.html#border-properties, > https://www.w3.org/TR/CSS2/visudet.html#the-width-property and > https://www.w3.org/TR/CSS2/visudet.html#the-height-property) > 2. or the HTML4 attributes > (https://www.w3.org/TR/html401/struct/objects.html#h-13.7.1 and > https://www.w3.org/TR/html401/struct/objects.html#h-13.7.3) > 3. or another custom format. > Currently the skins use the values as-is for either CSS property or HTML > attribute, but although they are named the same, the supported values differ > a lot. > This came up in the context of > https://github.com/apache/maven-fluido-skin/pull/23#discussion_r866169720. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-311) Rework and simplify the site model
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated DOXIASITETOOLS-311: -- Labels: (was: doxia-2.0.0-stack) > Rework and simplify the site model > -- > > Key: DOXIASITETOOLS-311 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-311 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Site model >Affects Versions: 2.0.0-M11 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M12 > > > For a long time the current site model has a lot of problems/inconsitencies: > * Image attributes mixed into text nodes > * Incomplete information > * Images added to nodes which do not make sense > * Wrong root element > * Misuse of title attribute > We need to resolve inconsistencies and drop unneeded content. See also linked > issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSITE-976) Bump plexus-archiver from 4.7.1 to 4.8.0
[ https://issues.apache.org/jira/browse/MSITE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSITE-976: Assignee: Sylwester Lachiewicz > Bump plexus-archiver from 4.7.1 to 4.8.0 > > > Key: MSITE-976 > URL: https://issues.apache.org/jira/browse/MSITE-976 > Project: Maven Site Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 4.0.0-M10 > > > Fix for CVE-2023-37460 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-254) Clarify inconsistencies in Doxia site model
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-254:
--
Labels: (was: doxia-2.0.0-stack)
> Clarify inconsistencies in Doxia site model
> ---
>
> Key: DOXIASITETOOLS-254
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-254
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site model
>Affects Versions: 1.11.1
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0-M12
>
>
> [https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html]
> bannerLeft/bannerRight (see also DOXIASITETOOLS-253):
> * Are {{name}} and {{src}} (image) mutually exclusive? If yes, in what order
> should they appear? Why is no {{position}} like with other similar elements
> (logo, item)?
> * Does {{href}} truly only apply to the image?
> * Why is there no {{target}}?
> * Must {{title}}/{{alt}} only be used on the image?
> * Why not apply here the same logic as with the other imaged elements?
> * Why {{src}} instead of {{img}} like the rest?
> * Why does it use subelements and not attributes like the rest?
> logo/link item/menu/menu item:
> * Does {{href}} truly only apply to the text? (different to banner)
> * Must {{title}}/{{alt}} only be used on the image?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DOXIASITETOOLS-174) rename site.xml root tag from "project" to "site"
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated DOXIASITETOOLS-174:
--
Labels: (was: doxia-2.0.0-stack)
> rename site.xml root tag from "project" to "site"
> -
>
> Key: DOXIASITETOOLS-174
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-174
> Project: Maven Doxia Sitetools
> Issue Type: Wish
> Components: Site model
>Affects Versions: 1.7.4
>Reporter: Herve Boutemy
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0-M12
>
>
> when looking at [decoration model
> descriptor|http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.7/doxia-decoration-model/decoration.html],
> naming the root element as {{project}} (like for {{pom.xml}}) is misleading
> if the root element could be renamed as {{doxia-decoration}}, the obvious
> (this descriptor is about site decoration, done with Doxia) could perhaps
> become obvious
> (in IT, calling everything a "project" is an issue...)
> I know that this change of xsd schema will break compatibility, but I think
> it can really make a big difference in usability (and I should have had this
> idea for Doxia Sitetools 1.7, when we already made some breaking changes...)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSKINS-237) Rework skin for new site model
[ https://issues.apache.org/jira/browse/MSKINS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770883#comment-17770883 ] ASF GitHub Bot commented on MSKINS-237: --- michael-o opened a new pull request, #56: URL: https://github.com/apache/maven-fluido-skin/pull/56 (no comment) > Rework skin for new site model > -- > > Key: MSKINS-237 > URL: https://issues.apache.org/jira/browse/MSKINS-237 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Affects Versions: fluido-2.0.0-M7 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: fluido-2.0.0-M8 > > > With DOXIASITETOOLS-311 a new, streamlined site model will be introduced. The > skin needs to adapt to the new changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DOXIASITETOOLS-253) Clarify "border", "width" and "height" for Banner and LinkItem
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned DOXIASITETOOLS-253: - Assignee: Michael Osipov > Clarify "border", "width" and "height" for Banner and LinkItem > -- > > Key: DOXIASITETOOLS-253 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-253 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Site model >Reporter: Konrad Windszus >Assignee: Michael Osipov >Priority: Major > Labels: doxia-2.0.0-stack > > The elements "border", "width" and "height" in > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_bannerLeft > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_bannerRight > # > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-1.11.1/doxia-decoration-model/decoration.html#class_item > have a very vague description (same in renamed doxia-site-model > https://maven.apache.org/doxia/doxia-sitetools/doxia-site-model/site.html ). > It should be clarified with regards to whether > 1. this is the format of the same named CSS properties > (https://www.w3.org/TR/CSS2/box.html#border-properties, > https://www.w3.org/TR/CSS2/visudet.html#the-width-property and > https://www.w3.org/TR/CSS2/visudet.html#the-height-property) > 2. or the HTML4 attributes > (https://www.w3.org/TR/html401/struct/objects.html#h-13.7.1 and > https://www.w3.org/TR/html401/struct/objects.html#h-13.7.3) > 3. or another custom format. > Currently the skins use the values as-is for either CSS property or HTML > attribute, but although they are named the same, the supported values differ > a lot. > This came up in the context of > https://github.com/apache/maven-fluido-skin/pull/23#discussion_r866169720. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1309) Upgrade to Doxia Sitetools 2.0.0-M12
[ https://issues.apache.org/jira/browse/MSHARED-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1309. --- Resolution: Fixed Fixed with [bd1fde85f2ac3a28521e90ed1ad5d83c803d2ef2|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=bd1fde85f2ac3a28521e90ed1ad5d83c803d2ef2]. > Upgrade to Doxia Sitetools 2.0.0-M12 > > > Key: MSHARED-1309 > URL: https://issues.apache.org/jira/browse/MSHARED-1309 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0-M10 > > > This also includes to Maven Site Plugin 4.0.0-M9 in ITs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1308) Upgrade to Parent 40
[ https://issues.apache.org/jira/browse/MSHARED-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1308. --- Resolution: Fixed Fixed with [20b2922a14f2c22f2095f77c1adb6c7f92c6ccf9|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=20b2922a14f2c22f2095f77c1adb6c7f92c6ccf9]. > Upgrade to Parent 40 > > > Key: MSHARED-1308 > URL: https://issues.apache.org/jira/browse/MSHARED-1308 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0-M10 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-jar-plugin] elharo opened a new pull request, #63: move plexus-utils to test scope and remove unused imports
elharo opened a new pull request, #63: URL: https://github.com/apache/maven-jar-plugin/pull/63 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAR) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MJAR-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MJAR-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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] (MPOM-427) use version.artifactId property for dependency versions (like plugins)
[
https://issues.apache.org/jira/browse/MPOM-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPOM-427.
--
Assignee: Herve Boutemy
Resolution: Fixed
> use version.artifactId property for dependency versions (like plugins)
> --
>
> Key: MPOM-427
> URL: https://issues.apache.org/jira/browse/MPOM-427
> Project: Maven POMs
> Issue Type: Task
> Components: maven
>Affects Versions: MAVEN-40
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: MAVEN-41
>
>
> we defined {{version.}} naming convention in MPOM-289
> it would make sense to keep the same convention for dependencies versions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-parent] hboutemy merged pull request #138: [MPOM-426] downgrade plexus-xml to 3.0.0 as 4 is incompatible with Maven 3
hboutemy merged PR #138: URL: https://github.com/apache/maven-parent/pull/138 -- 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] (MSKINS-226) Add custom option to explicitly enable AnchorJS along with options
[ https://issues.apache.org/jira/browse/MSKINS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770882#comment-17770882 ] ASF GitHub Bot commented on MSKINS-226: --- michael-o commented on PR #51: URL: https://github.com/apache/maven-fluido-skin/pull/51#issuecomment-1742123370 Branch rebased and I still consider this reasonable to include in the next major for consistency reasons with the other custom options. > Add custom option to explicitly enable AnchorJS along with options > -- > > Key: MSKINS-226 > URL: https://issues.apache.org/jira/browse/MSKINS-226 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-2.0.0-M5 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > > Not every one wants this to be enabled by default. An option should be added > and the user needs to explicitly enable this, like with other JS-based > options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-312) Upgrade to Parent 40
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-312. - Resolution: Fixed Fixed with [8f0a8ec793a462f04e8ff91af61257c30317688c|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=8f0a8ec793a462f04e8ff91af61257c30317688c]. > Upgrade to Parent 40 > > > Key: DOXIASITETOOLS-312 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-312 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Herve Boutemy >Priority: Major > Fix For: 2.0.0-M12 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DOXIASITETOOLS-312) Upgrade to Parent 40
Michael Osipov created DOXIASITETOOLS-312: - Summary: Upgrade to Parent 40 Key: DOXIASITETOOLS-312 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-312 Project: Maven Doxia Sitetools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Herve Boutemy Fix For: 2.0.0-M12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1309) Upgrade to Doxia Sitetools 2.0.0-M12
Michael Osipov created MSHARED-1309: --- Summary: Upgrade to Doxia Sitetools 2.0.0-M12 Key: MSHARED-1309 URL: https://issues.apache.org/jira/browse/MSHARED-1309 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-impl Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-impl-4.0.0-M10 This also includes to Maven Site Plugin 4.0.0-M9 in ITs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1311) Upgrade plugins and components (in ITs)
Michael Osipov created MSHARED-1311: --- Summary: Upgrade plugins and components (in ITs) Key: MSHARED-1311 URL: https://issues.apache.org/jira/browse/MSHARED-1311 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-exec Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-exec-2.0.0-M10 * Upgrade to Maven Site Plugin 4.0.0-M9 * Upgrade to Maven Reporing Impl 4.0.0-M10 * Upgrade to Maven Doxia Sitetools 2.0.0-M12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7873) Export missing Xpp3DomBuilder
[ https://issues.apache.org/jira/browse/MNG-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7873: - Fix Version/s: (was: 3.9.5) > Export missing Xpp3DomBuilder > - > > Key: MNG-7873 > URL: https://issues.apache.org/jira/browse/MNG-7873 > Project: Maven > Issue Type: Bug > Components: Core >Reporter: Guillaume Nodet >Priority: Major > > See https://lists.apache.org/thread/ltd1g1dbv0lqqdw5q941gmrkfyn6m87m -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-site] michael-o commented on a diff in pull request #458: Maven 3.9.5 release notes
michael-o commented on code in PR #458: URL: https://github.com/apache/maven-site/pull/458#discussion_r1342177003 ## content/markdown/docs/3.9.5/release-notes.md: ## @@ -0,0 +1,64 @@ + + +# Release Notes Maven 3.9.5 + +The Apache Maven team would like to announce the release of Maven 3.9.5. + +Maven 3.9.5 is [available for download][0]. + +Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting, and documentation from a central place. + +The core release is independent of plugin releases. Further releases of plugins will be made separately. See the [PluginList][1] for more information. + +If you have any questions, please consult: + +- the web site: [https://maven.apache.org/][2] +- the maven-user mailing list: [https://maven.apache.org/mailing-lists.html](/mailing-lists.html) +- the reference documentation: [https://maven.apache.org/ref/3.9.5/](/ref/3.9.5/) + +## Overview About the Changes + +Regression fixes from Maven 3.9.4. All users already on Maven 3.9.x are advised to upgrade. Review Comment: Not only regression fixes... -- 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
[GitHub] [maven-parent] hboutemy merged pull request #139: [MPOM-427] use version.artifactId property for dependency versions (like plugins)
hboutemy merged PR #139: URL: https://github.com/apache/maven-parent/pull/139 -- 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] (MSKINS-237) Rework skin for new site model
Michael Osipov created MSKINS-237: - Summary: Rework skin for new site model Key: MSKINS-237 URL: https://issues.apache.org/jira/browse/MSKINS-237 Project: Maven Skins Issue Type: Task Components: Fluido Skin Affects Versions: fluido-2.0.0-M7 Reporter: Michael Osipov Assignee: Michael Osipov Fix For: fluido-2.0.0-M8 With DOXIASITETOOLS-311 a new, streamlined site model will be introduced. The skin needs to adapt to the new changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1308) Upgrade to Parent 40
Michael Osipov created MSHARED-1308: --- Summary: Upgrade to Parent 40 Key: MSHARED-1308 URL: https://issues.apache.org/jira/browse/MSHARED-1308 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-reporting-impl Reporter: Michael Osipov Assignee: Michael Osipov Fix For: maven-reporting-impl-4.0.0-M10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MSKINS-235) wrong META-INF/LICENSE and META-INF/NOTICE in release jar
[
https://issues.apache.org/jira/browse/MSKINS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743434#comment-17743434
]
Herve Boutemy edited comment on MSKINS-235 at 10/1/23 6:43 PM:
---
ok, the copy does not happen in maven-remote-resources-plugin but in
maven-resources-plugin:
upgrading maven-resources-plugin from 3.3.0 to 3.3.1 gives more explicit output:
{noformat}[INFO] --- resources:3.3.1:resources (default-resources) @
maven-fluido-skin ---
[INFO] Copying 2 resources from to target/classes/META-INF
[INFO] Copying 33 resources from src/main/resources to target/classes
[INFO] Copying 3 resources from src/main/resources to target/classes
[INFO] Copying 1 resource from src/main/resources to target/classes
[INFO] Copying 2 resources from target/maven-fluido-skin-2.0.0-M8-SNAPSHOT to
target/classes
[INFO] Copying 3 resources from target/maven-shared-archive-resources to
target/classes{noformat}
the first and the last copy lines are the interesting ones:
- first: "Copying 2 resources from to target/classes/META-INF" copies the
content root in Git = the handwritten LICENSE and NOTICE that we expect will be
kept
- last: "Copying 3 resources from target/maven-shared-archive-resources to
target/classes" = the generated content from apache-resource-bundles
I tested on a Linux box and on a Windows box
Surprisingly on Linux, the overwrite from the second copy does not happen
but on Windows, the second copy overwrites
The Windows behaviour looks reasonable, even if it's not the result we want (we
want to keep the hand-written files)
IMHO:
1. there is a bug on Linux on maven-resources-plugin
2. the way maven-fluido-skin expects no force hand-written content looks wrong,
because it's overwritten by generated content
was (Author: hboutemy):
ok, the copy does not happen in maven-remote-resources-plugin but in
maven-resources-plugin:
upgrading maven-resources-plugin from 3.3.0 to 3.3.1 gives more explicit output:
{noformat}[INFO] --- resources:3.3.1:resources (default-resources) @
maven-fluido-skin ---
[INFO] Copying 2 resources from to target/classes/META-INF
[INFO] Copying 33 resources from src/main/resources to target/classes
[INFO] Copying 3 resources from src/main/resources to target/classes
[INFO] Copying 1 resource from src/main/resources to target/classes
[INFO] Copying 2 resources from target/maven-fluido-skin-2.0.0-M8-SNAPSHOT to
target/classes
[INFO] Copying 3 resources from target/maven-shared-archive-resources to
target/classes{noformat}
the first and the last copy lines are the interesting ones:
- first: "Copying 2 resources from to target/classes/META-INF" copies the
content root in Git = the handwritten LICENSE and NOTICE that we expect will be
kept
- last: "Copying 3 resources from target/maven-shared-archive-resources to
target/classes" = the generated content from apache-resource-bundles
I tested on a Linux box and on a Widows box
Suprisingly on Linux, the overwrite from the second copy does not happen
but on Windows, the second copy overwrites
The Windows behaviour looks reasonable, even if it's not the result we want (we
want to keep the hand-written files)
IMHO:
1. there is a bug on Linux on maven-remote-resources
2. the way maven-fluido-skin expects no force hand-written content looks wrong,
because it's overwritten by generated content
> wrong META-INF/LICENSE and META-INF/NOTICE in release jar
> -
>
> Key: MSKINS-235
> URL: https://issues.apache.org/jira/browse/MSKINS-235
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-2.0.0-M5, fluido-2.0.0-M6, fluido-2.0.0-M7
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: fluido-2.0.0-M8
>
>
> seen as testing reproducible builds:
> [https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/skins/fluido/README.md]
> reference jar has content that seems to be generated from remote-resources
> with Jar Resource Bundle https://maven.apache.org/apache-resource-bundles/jar/
> but rebuild has content configured in pom.xml to copy content from Git:
> https://github.com/apache/maven-fluido-skin/
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MRESOURCES-278) Regression - Changed copy behaviour if file already exists
[ https://issues.apache.org/jira/browse/MRESOURCES-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MRESOURCES-278: - Summary: Regression - Changed copy behaviour if file already exists (was: Regression - Changed copy behaviour if files already exists) > Regression - Changed copy behaviour if file already exists > -- > > Key: MRESOURCES-278 > URL: https://issues.apache.org/jira/browse/MRESOURCES-278 > Project: Maven Resources Plugin > Issue Type: Bug > Components: copy >Affects Versions: 3.3.0 >Reporter: Georg Tsakumagos >Priority: Critical > > With MSHARED-966 the behavior for the maven-resources-plugin changed > dramatically. > Now an exception is thown if an file already exists. > Before it was only overwritten if newer an no exception was thrown. > The new behavior breaks many builds. If this new behavior is a feature the > plugin site should be updated with a big (!) warning to everyone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-reporting-exec] michael-o opened a new pull request, #19: [MSHARED-1298] Missing site report should be detected
michael-o opened a new pull request, #19: URL: https://github.com/apache/maven-reporting-exec/pull/19 This closes #19 Output: ``` [INFO] Configuring report plugin maven-plugin-plugin:3.9.0 [WARNING] Ignoring org.apache.maven.plugins:maven-plugin-plugin:3.9.0:addPluginArtifactMetadata goal since it is not a report: should be removed from reporting configuration in POM [WARNING] Ignoring org.apache.maven.plugins:maven-plugin-plugin:3.9.0:descriptor goal since it is not a report: should be removed from reporting configuration in POM [WARNING] Ignoring org.apache.maven.plugins:maven-plugin-plugin:3.9.0:help goal since it is not a report: should be removed from reporting configuration in POM [WARNING] Ignoring org.apache.maven.plugins:maven-plugin-plugin:3.9.0:helpmojo goal since it is not a report: should be removed from reporting configuration in POM ``` -- 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-1298) Missing site report should be detected
[
https://issues.apache.org/jira/browse/MSHARED-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770916#comment-17770916
]
ASF GitHub Bot commented on MSHARED-1298:
-
michael-o opened a new pull request, #19:
URL: https://github.com/apache/maven-reporting-exec/pull/19
This closes #19
Output:
```
[INFO] Configuring report plugin maven-plugin-plugin:3.9.0
[WARNING] Ignoring
org.apache.maven.plugins:maven-plugin-plugin:3.9.0:addPluginArtifactMetadata
goal since it is not a report: should be removed from reporting configuration
in POM
[WARNING] Ignoring
org.apache.maven.plugins:maven-plugin-plugin:3.9.0:descriptor goal since it is
not a report: should be removed from reporting configuration in POM
[WARNING] Ignoring org.apache.maven.plugins:maven-plugin-plugin:3.9.0:help
goal since it is not a report: should be removed from reporting configuration
in POM
[WARNING] Ignoring
org.apache.maven.plugins:maven-plugin-plugin:3.9.0:helpmojo goal since it is
not a report: should be removed from reporting configuration in POM
```
> Missing site report should be detected
> --
>
> Key: MSHARED-1298
> URL: https://issues.apache.org/jira/browse/MSHARED-1298
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-reporting-exec
>Reporter: Slawomir Jaranowski
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-exec-2.0.0-M10
>
>
> When we define as report plugin which not contains any report Mojo
> we should inform by warning or even break a build.
> eg:
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-plugin-plugin
>
>
>
> {code}
> is silently skipped and no report is generated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-parent] dependabot[bot] opened a new pull request, #140: Bump org.codehaus.plexus:plexus-xml from 3.0.0 to 4.0.0
dependabot[bot] opened a new pull request, #140: URL: https://github.com/apache/maven-parent/pull/140 Bumps [org.codehaus.plexus:plexus-xml](https://github.com/codehaus-plexus/plexus-xml) from 3.0.0 to 4.0.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-xml/releases;>org.codehaus.plexus:plexus-xml's releases. 4.0.0 Use spotless (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/8;>#8) https://github.com/gnodet;>@gnodet Fix site generation (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/15;>#15) https://github.com/gnodet;>@gnodet Switch build ci workflow to master branch (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/14;>#14) https://github.com/gnodet;>@gnodet Fix SCM urls (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/13;>#13) https://github.com/gnodet;>@gnodet MXParser tokenization fails when PI is before first tag (fixes https://redirect.github.com/codehaus-plexus/plexus-xml/issues/7;>#7) (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/12;>#12) https://github.com/gnodet;>@gnodet Deprecate Xpp3DomUtils (fixes https://redirect.github.com/codehaus-plexus/plexus-xml/issues/6;>#6) (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/9;>#9) https://github.com/gnodet;>@gnodet Use a ArrayDeque (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/5;>#5) https://github.com/gnodet;>@gnodet Upgrade plugins and clean build warnings (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/4;>#4) https://github.com/gnodet;>@gnodet Switch to junit 5 (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/2;>#2) https://github.com/gnodet;>@gnodet Fix parsing an UTF-8 file without BOM and ISO-8859-1 encoding (https://redirect.github.com/codehaus-plexus/plexus-xml/pull/1;>#1) https://github.com/gnodet;>@gnodet Commits https://github.com/codehaus-plexus/plexus-xml/commit/cac55e8c167b168c6c36dd4a057dedfadec03c0e;>cac55e8 [maven-release-plugin] prepare release plexus-xml-4.0.0 https://github.com/codehaus-plexus/plexus-xml/commit/17787e5ff7dea8acf347fd3f92bd855e110d6dfe;>17787e5 Reformat using spotless https://github.com/codehaus-plexus/plexus-xml/commit/d58719dc833c66c97d0f2f0d63235931282ffb9c;>d58719d Upgrade to plexus 13 https://github.com/codehaus-plexus/plexus-xml/commit/9547a2d9c78c78871ce6d372f5141f1b51cb9669;>9547a2d Fix Xpp3DomUtils imports https://github.com/codehaus-plexus/plexus-xml/commit/b1794a39037eb63e0f3ebc8db67f890ce593c1ed;>b1794a3 Fix site generation (https://redirect.github.com/codehaus-plexus/plexus-xml/issues/15;>#15) https://github.com/codehaus-plexus/plexus-xml/commit/e1f38f157a898aa9284606272b992f5219fd13eb;>e1f38f1 Switch build ci workflow to master branch (https://redirect.github.com/codehaus-plexus/plexus-xml/issues/14;>#14) https://github.com/codehaus-plexus/plexus-xml/commit/9ba44ebfdb3eba3063385197bf6c032b2b61ccd4;>9ba44eb Fix SCM urls (https://redirect.github.com/codehaus-plexus/plexus-xml/issues/13;>#13) https://github.com/codehaus-plexus/plexus-xml/commit/792f94742e997577cf5fea84ba879115bc9c79c2;>792f947 MXParser tokenization fails when PI is before first tag (fixes https://redirect.github.com/codehaus-plexus/plexus-xml/issues/7;>#7) (https://redirect.github.com/codehaus-plexus/plexus-xml/issues/12;>#12) https://github.com/codehaus-plexus/plexus-xml/commit/85fe71e68e91de21000ba2f0d97ff73e020fd143;>85fe71e Deprecate Xpp3DomUtils (fixes https://redirect.github.com/codehaus-plexus/plexus-xml/issues/6;>#6) (https://redirect.github.com/codehaus-plexus/plexus-xml/issues/9;>#9) https://github.com/codehaus-plexus/plexus-xml/commit/8351c4ec5eb6bdeeccdb9bc49c03f167d6c64269;>8351c4e Use a ArrayDeque and enable test only for JDK 1.8 (https://redirect.github.com/codehaus-plexus/plexus-xml/issues/5;>#5) Additional commits viewable in https://github.com/codehaus-plexus/plexus-xml/compare/plexus-xml-3.0.0...plexus-xml-4.0.0;>compare view Most Recent Ignore Conditions Applied to This Pull Request | Dependency Name | Ignore Conditions | | --- | --- | | org.codehaus.plexus:plexus-xml | [< 5, > 4.0.0] | [](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
[GitHub] [maven-assembly-plugin] dependabot[bot] opened a new pull request, #154: Bump com.github.luben:zstd-jni from 1.5.5-5 to 1.5.5-6
dependabot[bot] opened a new pull request, #154: URL: https://github.com/apache/maven-assembly-plugin/pull/154 Bumps [com.github.luben:zstd-jni](https://github.com/luben/zstd-jni) from 1.5.5-5 to 1.5.5-6. Commits https://github.com/luben/zstd-jni/commit/92e7862b74112036a14359e184509875f310b32c;>92e7862 Fix documentation https://github.com/luben/zstd-jni/commit/e0c66f1230377d4980ad6abc0767b36c860af538;>e0c66f1 Fix copy/paste error https://github.com/luben/zstd-jni/commit/2cbe15fd7228232847817325cd044310b784106c;>2cbe15f v1.5.5-6 https://github.com/luben/zstd-jni/commit/dbb8bcd62c158b8b71e86ba1a946192d8835914f;>dbb8bcd Add tests, fix spelling and omissions https://github.com/luben/zstd-jni/commit/3f6c55e87a38255bdbeeca3e773f99bf9e8a7b7f;>3f6c55e Restore decompressedSize behaviour... See full diff in https://github.com/luben/zstd-jni/compare/v.1.5.5-5...v1.5.5-6;>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 close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[GitHub] [maven-shade-plugin] dependabot[bot] opened a new pull request, #200: Bump asmVersion from 9.5 to 9.6
dependabot[bot] opened a new pull request, #200: URL: https://github.com/apache/maven-shade-plugin/pull/200 Bumps `asmVersion` from 9.5 to 9.6. Updates `org.ow2.asm:asm` from 9.5 to 9.6 Updates `org.ow2.asm:asm-commons` from 9.5 to 9.6 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 close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[GitHub] [maven-dependency-analyzer] dependabot[bot] opened a new pull request, #97: Bump org.ow2.asm:asm from 9.5 to 9.6
dependabot[bot] opened a new pull request, #97: URL: https://github.com/apache/maven-dependency-analyzer/pull/97 Bumps org.ow2.asm:asm from 9.5 to 9.6. [](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 close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[GitHub] [maven-parent] dependabot[bot] closed pull request #140: Bump org.codehaus.plexus:plexus-xml from 3.0.0 to 4.0.0
dependabot[bot] closed pull request #140: Bump org.codehaus.plexus:plexus-xml from 3.0.0 to 4.0.0 URL: https://github.com/apache/maven-parent/pull/140 -- 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
[GitHub] [maven-parent] dependabot[bot] commented on pull request #140: Bump org.codehaus.plexus:plexus-xml from 3.0.0 to 4.0.0
dependabot[bot] commented on PR #140: URL: https://github.com/apache/maven-parent/pull/140#issuecomment-1742435452 OK, I won't notify you about version 4.x.x again, unless you re-open this PR. -- 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
[GitHub] [maven-parent] slachiewicz commented on pull request #140: Bump org.codehaus.plexus:plexus-xml from 3.0.0 to 4.0.0
slachiewicz commented on PR #140: URL: https://github.com/apache/maven-parent/pull/140#issuecomment-1742435427 @dependabot ignore this major 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
