[GitHub] [maven-indexer] mbien commented on a diff in pull request #277: IndexDataReader could use Sets.
mbien commented on code in PR #277: URL: https://github.com/apache/maven-indexer/pull/277#discussion_r1032837233 ## indexer-core/src/main/java/org/apache/maven/index/updater/IndexDataReader.java: ## @@ -165,8 +165,8 @@ private IndexDataReadResult readIndexMT( IndexWriter w, IndexingContext context final Document theEnd = new Document(); -ConcurrentMap rootGroups = new ConcurrentHashMap<>(); -ConcurrentMap allGroups = new ConcurrentHashMap<>(); +Set rootGroups = ConcurrentHashMap.newKeySet(); +Set allGroups = ConcurrentHashMap.newKeySet(); Review Comment: I tried to size them appropriately (central has about 70k groups, and resizing CHMs has a larger impact than normal maps), but since this made no performance difference I left the defaults as is. (tested only twice so the sample size is small though, noise is a bit high) -- 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-indexer] mbien commented on a diff in pull request #277: IndexDataReader could use Sets.
mbien commented on code in PR #277:
URL: https://github.com/apache/maven-indexer/pull/277#discussion_r1032837361
##
indexer-core/src/main/java/org/apache/maven/index/updater/IndexDataReader.java:
##
@@ -277,17 +277,17 @@ private IndexWriter tempWriter( final String name )
throws IOException
}
private void addToIndex( final Document doc, final IndexingContext
context, final IndexWriter indexWriter,
- final ConcurrentMap rootGroups,
- final ConcurrentMap allGroups )
+ final Set rootGroups,
+ final Set allGroups )
throws IOException
{
ArtifactInfo ai = IndexUtils.constructArtifactInfo( doc, context );
if ( ai != null )
{
indexWriter.addDocument( IndexUtils.updateDocument( doc, context,
false, ai ) );
-rootGroups.putIfAbsent( ai.getRootGroup(), Boolean.TRUE );
-allGroups.putIfAbsent( ai.getGroupId(), Boolean.TRUE );
+rootGroups.add( ai.getRootGroup() );
+allGroups.add( ai.getGroupId() );
Review Comment:
`add` should be a little bit faster compared to `putIfAbsent` in the
concurrent case. But since so much IO is going on it goes down in the noise.
##
indexer-core/src/main/java/org/apache/maven/index/updater/IndexDataReader.java:
##
@@ -165,8 +165,8 @@ private IndexDataReadResult readIndexMT( IndexWriter w,
IndexingContext context
final Document theEnd = new Document();
-ConcurrentMap rootGroups = new ConcurrentHashMap<>();
-ConcurrentMap allGroups = new ConcurrentHashMap<>();
+Set rootGroups = ConcurrentHashMap.newKeySet();
+Set allGroups = ConcurrentHashMap.newKeySet();
Review Comment:
I tried to size them appropriately (central has about 70k groups, and
resizing CHMs has a larger impact than normal maps), but since this made no
performance difference I left the defaults as is.
--
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-indexer] mbien opened a new pull request, #277: IndexDataReader could use Sets.
mbien opened a new pull request, #277: URL: https://github.com/apache/maven-indexer/pull/277 Noticed that both, the single threaded and the multi threaded impl used CHMs. Instead of only changing `readIndexST` to plain maps, I switched everything to Sets. -- 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] (MDEP-837) Upgrade Parent to 38
[ https://issues.apache.org/jira/browse/MDEP-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-837: Fix Version/s: version-next (was: 3.4.0) > Upgrade Parent to 38 > > > Key: MDEP-837 > URL: https://issues.apache.org/jira/browse/MDEP-837 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: version-next > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-832) Remove commons-collections-4
[
https://issues.apache.org/jira/browse/MDEP-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-832:
Fix Version/s: version-next
(was: 3.4.0)
> Remove commons-collections-4
>
>
> Key: MDEP-832
> URL: https://issues.apache.org/jira/browse/MDEP-832
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.3.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: version-next
>
>
> Remove the dependency:
> {code:xml}
>
> org.apache.commons
> commons-collections4
> 4.2
>
> {code}
> which is used only for a single method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-831) Remove not used dependencies / Replace parts
[
https://issues.apache.org/jira/browse/MDEP-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MDEP-831:
Fix Version/s: version-next
(was: 3.4.0)
> Remove not used dependencies / Replace parts
>
>
> Key: MDEP-831
> URL: https://issues.apache.org/jira/browse/MDEP-831
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.3.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: version-next
>
>
> Currently the dependency is not used at all:
> {code:xml}
>
> commons-beanutils
> commons-beanutils
> 1.9.4
>
> {code}
> The dependency is only used for a single method:
> {code:xml}
>
> org.apache.commons
> commons-collections4
> 4.2
>
> {code}
> The dependency is only used for two methods of StringUtils.
> {code:xml}
>
> org.apache.commons
> commons-lang3
> 3.12.0
>
> {code}
> The dependency is only used in tests for deleting a directory.
> {code:xml}
>
> commons-io
> commons-io
> 2.11.0
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MDEP-834) Bump maven-common-artifact-filters from 3.3.1 to 3.3.2
[ https://issues.apache.org/jira/browse/MDEP-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MDEP-834: --- Assignee: Sylwester Lachiewicz > Bump maven-common-artifact-filters from 3.3.1 to 3.3.2 > -- > > Key: MDEP-834 > URL: https://issues.apache.org/jira/browse/MDEP-834 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-674) maven-dependency-plugin should leverage plexus-build-api to support IDEs
[ https://issues.apache.org/jira/browse/MDEP-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MDEP-674. --- > maven-dependency-plugin should leverage plexus-build-api to support IDEs > > > Key: MDEP-674 > URL: https://issues.apache.org/jira/browse/MDEP-674 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: copy >Reporter: Mickael Istria >Assignee: Konrad Windszus >Priority: Minor > Fix For: 3.4.0 > > > I often use the maven-dependency-plugon:copy goal for packaging purpose. > However, Eclipse m2e complains that "plugin execution isn't covered...". > This could be improved by adding just m2e lifecycle mapping metadata and > leveraging the BuildContext API: > https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MWRAPPER-44) maven-wrapper may use outdated MavenWrapperDownloader.class
[ https://issues.apache.org/jira/browse/MWRAPPER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639553#comment-17639553 ] ASF GitHub Bot commented on MWRAPPER-44: nhojpatrick commented on PR #15: URL: https://github.com/apache/maven-wrapper/pull/15#issuecomment-1328109765 @slawekjaranowski i think it's still needed if you swap to source, it should delete the class. i just retested and i think it's still needed. > maven-wrapper may use outdated MavenWrapperDownloader.class > --- > > Key: MWRAPPER-44 > URL: https://issues.apache.org/jira/browse/MWRAPPER-44 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Scripts >Affects Versions: 3.1.0 >Reporter: Jeremy Norris >Priority: Major > Fix For: 3.1.1 > > > When the mvnw script falls back to using MavenWrapperDownloader, it will use > an existing copy of MavenWrapperDownloader.class that may have originated > from compiling with an older version of MavenWrapperDownloader.java instead > of the current release version that is checked into the repository. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-wrapper] nhojpatrick commented on pull request #15: MWRAPPER-44 clean up MavenWrapperDownloader upon plugin execution
nhojpatrick commented on PR #15: URL: https://github.com/apache/maven-wrapper/pull/15#issuecomment-1328109765 @slawekjaranowski i think it's still needed if you swap to source, it should delete the class. i just retested and i think it's still needed. -- 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-reporting-impl] michael-o opened a new pull request, #12: [MSHARED-1160] Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
michael-o opened a new pull request, #12: URL: https://github.com/apache/maven-reporting-impl/pull/12 This closes #12 -- 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-assembly-plugin] michael-o commented on pull request #102: [MASSEMBLY-973] Support zstd format
michael-o commented on PR #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102#issuecomment-1328104245 > Ok i think i understand your point. Does the latest change fix the issue? The change is incomplete which you handle the exception, you ignore it in the test and don't skip the test: ``` Caused by: org.apache.maven.plugins.assembly.archive.ArchiveCreationException: Unable to find native library for assembly 'format-test' at org.apache.maven.plugins.assembly.archive.DefaultAssemblyArchiver.createArchive (DefaultAssemblyArchiver.java:197) at org.apache.maven.plugins.assembly.mojos.AbstractAssemblyMojo.execute (AbstractAssemblyMojo.java:523) at org.apache.maven.plugins.assembly.mojos.SingleAssemblyMojo.execute (SingleAssemblyMojo.java:60) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) ``` Moreover, you might want to map `.tzst` as well: ``` http://maven.apache.org/ASSEMBLY/2.1.1 https://maven.apache.org/xsd/assembly-2.1.1.xsd; xmlns="http://maven.apache.org/ASSEMBLY/2.1.1; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> format-test dir zip tar tar.gz tgz tar.bz2 tbz2 jar war tar.snappy tar.xz txz tar.zst ``` -- 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] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639549#comment-17639549 ] Hudson commented on MNG-7586: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #139 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/139/ > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7473) Backport Maven BOM to Maven 3.9.x
[ https://issues.apache.org/jira/browse/MNG-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639548#comment-17639548 ] ASF GitHub Bot commented on MNG-7473: - cstamas commented on PR #859: URL: https://github.com/apache/maven/pull/859#issuecomment-1328103099 Am somewhat aligned with @kwin here, and am now on the other side: backporting the BOM from master to 3.9.x (as is) does not makes much sense (plus as said above, where is compat, where is maven etc), so am rather to close this out w/o merge. Will give 24h for anyone interested to respond (or just +1) this comment as sign for "I agree: close out this PR w/o merge". > Backport Maven BOM to Maven 3.9.x > - > > Key: MNG-7473 > URL: https://issues.apache.org/jira/browse/MNG-7473 > Project: Maven > Issue Type: Task > Components: POM >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0-candidate > > > It will ease lives of plugin developers a lot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] cstamas commented on pull request #859: [3.9.x] [MNG-7473] Backport Maven BOM to 3.9.0
cstamas commented on PR #859: URL: https://github.com/apache/maven/pull/859#issuecomment-1328103099 Am somewhat aligned with @kwin here, and am now on the other side: backporting the BOM from master to 3.9.x (as is) does not makes much sense (plus as said above, where is compat, where is maven etc), so am rather to close this out w/o merge. Will give 24h for anyone interested to respond (or just +1) this comment as sign for "I agree: close out this PR w/o merge". -- 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] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639547#comment-17639547 ] Hudson commented on MNG-7586: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #86 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/86/ > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639545#comment-17639545 ] ASF GitHub Bot commented on MNG-7586: - cstamas merged PR #882: URL: https://github.com/apache/maven/pull/882 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-7586. Resolution: Fixed > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7586) Update Maven Resolver to 1.9.2
[ https://issues.apache.org/jira/browse/MNG-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639544#comment-17639544 ] ASF GitHub Bot commented on MNG-7586: - cstamas merged PR #881: URL: https://github.com/apache/maven/pull/881 > Update Maven Resolver to 1.9.2 > -- > > Key: MNG-7586 > URL: https://issues.apache.org/jira/browse/MNG-7586 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-3 > > > Update Maven Resolver to 1.9.2 (releases 1.9.0 and 1.9.1 are fluke due > different reasons). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] cstamas merged pull request #882: [MNG-7586] Update Maven Resolver to 1.9.2
cstamas merged PR #882: URL: https://github.com/apache/maven/pull/882 -- 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] cstamas merged pull request #881: [MNG-7586] Update Maven Resolver to 1.9.2
cstamas merged PR #881: URL: https://github.com/apache/maven/pull/881 -- 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-assembly-plugin] pleeplop commented on pull request #102: [MASSEMBLY-973] Support zstd format
pleeplop commented on PR #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102#issuecomment-1328091471 Ok i think i understand your point. Is the latest change fix the issue? -- 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-assembly-plugin] michael-o commented on pull request #102: [MASSEMBLY-973] Support zstd format
michael-o commented on PR #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102#issuecomment-1328082071 Test: ``` mosipov@bsd1srv:/tmp/maven-assembly-plugin (zstd =) $ zip -d /home/mosipov/.m2/repository/com/github/luben/zstd-jni/1.5.2-5/zstd-jni-1.5.2-5.jar freebsd/amd64/ freebsd/amd64/libzstd-jni-1.5.2-5.so deleting: freebsd/amd64/ deleting: freebsd/amd64/libzstd-jni-1.5.2-5.so ``` results in: ``` [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.160 s [INFO] Finished at: 2022-11-26T18:08:23+01:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.5.0-SNAPSHOT:single (default-cli) on project format-test: Execution default-cli of goal org.apache.maven.plugins:maven-assembly-plugin:3.5.0-SNAPSHOT:single failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin:3.5.0-SNAPSHOT:single: java.lang.UnsatisfiedLinkError: no zstd-jni-1.5.2-5 in java.library.path [ERROR] Unsupported OS/arch, cannot find /freebsd/amd64/libzstd-jni-1.5.2-5.so or load zstd-jni-1.5.2-5 from system libraries. Please try building from source the jar or providing libzstd-jni-1.5.2-5 in your system. [ERROR] - [ERROR] realm = plugin>org.apache.maven.plugins:maven-assembly-plugin:3.5.0-SNAPSHOT [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/tmp/maven-assembly-plugin/target/local-repo/org/apache/maven/plugins/maven-assembly-plugin/3.5.0-SNAPSHOT/maven-assembly-plugin-3.5.0-SNAPSHOT.jar [ERROR] urls[1] = file:/tmp/maven-assembly-plugin/target/local-repo/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar [ERROR] urls[2] = file:/tmp/maven-assembly-plugin/target/local-repo/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar [ERROR] urls[3] = file:/tmp/maven-assembly-plugin/target/local-repo/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar [ERROR] urls[4] = file:/tmp/maven-assembly-plugin/target/local-repo/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar [ERROR] urls[5] = file:/tmp/maven-assembly-plugin/target/local-repo/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar [ERROR] urls[6] = file:/tmp/maven-assembly-plugin/target/local-repo/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar [ERROR] urls[7] = file:/tmp/maven-assembly-plugin/target/local-repo/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar [ERROR] urls[8] = file:/tmp/maven-assembly-plugin/target/local-repo/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar [ERROR] urls[9] = file:/tmp/maven-assembly-plugin/target/local-repo/org/codehaus/plexus/plexus-interpolation/1.26/plexus-interpolation-1.26.jar [ERROR] urls[10] = file:/tmp/maven-assembly-plugin/target/local-repo/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar [ERROR] urls[11] = file:/tmp/maven-assembly-plugin/target/local-repo/org/apache/maven/shared/maven-filtering/3.3.0/maven-filtering-3.3.0.jar [ERROR] urls[12] = file:/tmp/maven-assembly-plugin/target/local-repo/org/sonatype/plexus/plexus-build-api/0.0.7/plexus-build-api-0.0.7.jar [ERROR] urls[13] = file:/tmp/maven-assembly-plugin/target/local-repo/org/codehaus/plexus/plexus-io/3.4.0/plexus-io-3.4.0.jar [ERROR] urls[14] = file:/tmp/maven-assembly-plugin/target/local-repo/org/codehaus/plexus/plexus-archiver/4.6.0/plexus-archiver-4.6.0.jar [ERROR] urls[15] = file:/tmp/maven-assembly-plugin/target/local-repo/org/apache/commons/commons-compress/1.21/commons-compress-1.21.jar [ERROR] urls[16] = file:/tmp/maven-assembly-plugin/target/local-repo/org/iq80/snappy/snappy/0.4/snappy-0.4.jar [ERROR] urls[17] = file:/tmp/maven-assembly-plugin/target/local-repo/org/tukaani/xz/1.9/xz-1.9.jar [ERROR] urls[18] = file:/tmp/maven-assembly-plugin/target/local-repo/com/github/luben/zstd-jni/1.5.2-5/zstd-jni-1.5.2-5.jar [ERROR] urls[19] = file:/tmp/maven-assembly-plugin/target/local-repo/org/apache/maven/maven-archiver/3.6.0/maven-archiver-3.6.0.jar [ERROR] urls[20] = file:/tmp/maven-assembly-plugin/target/local-repo/org/codehaus/plexus/plexus-utils/3.4.2/plexus-utils-3.4.2.jar [ERROR] Number of foreign imports: 1 [ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]] [ERROR] [ERROR] - [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.5.0-SNAPSHOT:single (default-cli) on project format-test:
[jira] [Commented] (MASSEMBLY-969) Excludes filtering in 3.4.0 and 3.4.1 differs from 3.3.0
[
https://issues.apache.org/jira/browse/MASSEMBLY-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639508#comment-17639508
]
Michael Osipov commented on MASSEMBLY-969:
--
The IT is flawed. It isn't portable:
{noformat}
[ERROR] Failed to execute goal on project massembly-969: Could not resolve
dependencies for project test:massembly-969:jar:1: The following artifacts
could not be resolved: org.openjfx:javafx-base:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-controls:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-web:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-media:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-swing:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-graphics:jar:${javafx.platform}:18.0.1: Could not find
artifact org.openjfx:javafx-base:jar:${javafx.platform}:18.0.1 in local.central
(file:///home/mosipov/.m2/repository) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project massembly-969: Could not resolve dependencies for project
test:massembly-969:jar:1: The following artifacts could not be resolved:
org.openjfx:javafx-base:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-controls:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-web:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-media:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-swing:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-graphics:jar:${javafx.platform}:18.0.1: Could not find
artifact org.openjfx:javafx-base:jar:${javafx.platform}:18.0.1 in local.central
(file:///home/mosipov/.m2/repository)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:269)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:147)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
(MojoExecutor.java:248)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:202)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not
resolve dependencies for project test:massembly-969:jar:1: The following
artifacts could not be resolved:
org.openjfx:javafx-base:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-controls:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-web:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-media:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-swing:jar:${javafx.platform}:18.0.1,
org.openjfx:javafx-graphics:jar:${javafx.platform}:18.0.1: Could not find
artifact org.openjfx:javafx-base:jar:${javafx.platform}:18.0.1 in local.central
(file:///home/mosipov/.m2/repository)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve
(DefaultProjectDependenciesResolver.java:209)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:243)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:147)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
(MojoExecutor.java:248)
[GitHub] [maven-assembly-plugin] pleeplop commented on pull request #102: [MASSEMBLY-973] Support zstd format
pleeplop commented on PR #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102#issuecomment-1328077115 > zstd-jni should be on classpath because it is a dependency of plexus-archiver. -- 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-assembly-plugin] michael-o commented on pull request #102: [MASSEMBLY-973] Support zstd format
michael-o commented on PR #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102#issuecomment-1328075340 I don't understand how this is supposed to run when zstd is not on the classpath? -- 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-assembly-plugin] pleeplop commented on a diff in pull request #102: [MASSEMBLY-973] Support zstd format
pleeplop commented on code in PR #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102#discussion_r1032806908 ## src/test/java/org/apache/maven/plugins/assembly/archive/DefaultAssemblyArchiverTest.java: ## @@ -467,6 +467,25 @@ public void testCreateTarArchiver_TXzFormat_ShouldInitializeXzCompression() verify( archiverManager ).getArchiver( "tar" ); } +@Test +public void testCreateTarArchiver_TarZstFormat_ShouldInitializeXzCompression() Review Comment: It should be fixed now. -- 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-assembly-plugin] michael-o commented on a diff in pull request #102: [MASSEMBLY-973] Support zstd format
michael-o commented on code in PR #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102#discussion_r1032806481 ## src/test/java/org/apache/maven/plugins/assembly/archive/DefaultAssemblyArchiverTest.java: ## @@ -467,6 +467,25 @@ public void testCreateTarArchiver_TXzFormat_ShouldInitializeXzCompression() verify( archiverManager ).getArchiver( "tar" ); } +@Test +public void testCreateTarArchiver_TarZstFormat_ShouldInitializeXzCompression() Review Comment: method name still says XZ -- 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] (MASSEMBLY-973) Support tar.zst format
[ https://issues.apache.org/jira/browse/MASSEMBLY-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pleeplop updated MASSEMBLY-973: --- Description: Plexus archiver version 4.5.0 supports zstd format. Maybe maven-assembly should support it as well. Pull request https://github.com/apache/maven-assembly-plugin/pull/102 was: Plexus archiver version 4.5.0 supports zstd format. Maybe maven-assembly should support it as well. > Support tar.zst format > -- > > Key: MASSEMBLY-973 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-973 > Project: Maven Assembly Plugin > Issue Type: New Feature > Components: maven-archiver >Reporter: Pleeplop >Priority: Minor > > Plexus archiver version 4.5.0 supports zstd format. > Maybe maven-assembly should support it as well. > > Pull request https://github.com/apache/maven-assembly-plugin/pull/102 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-assembly-plugin] pleeplop opened a new pull request, #102: [MASSEMBLY-973] Support zstd format
pleeplop opened a new pull request, #102: URL: https://github.com/apache/maven-assembly-plugin/pull/102 This pull request provides support for zstd format (provided by plexus-archiver and zstd-jni) https://github.com/facebook/zstd https://github.com/luben/zstd-jni Let me know if you have any feedback. -- 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] (MASSEMBLY-973) Support tar.zst format
Pleeplop created MASSEMBLY-973: -- Summary: Support tar.zst format Key: MASSEMBLY-973 URL: https://issues.apache.org/jira/browse/MASSEMBLY-973 Project: Maven Assembly Plugin Issue Type: New Feature Components: maven-archiver Reporter: Pleeplop Plexus archiver version 4.5.0 supports zstd format. Maybe maven-assembly should support it as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DOXIASITETOOLS-274) Upgrade htmlunit to 2.67.0
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned DOXIASITETOOLS-274: - Assignee: Michael Osipov > Upgrade htmlunit to 2.67.0 > -- > > Key: DOXIASITETOOLS-274 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-274 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-271) Overhaul locale support (make Locale#ROOT instead of Locale#ENGLISH default and use full locale)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIASITETOOLS-271.
-
Resolution: Fixed
Fixed with
[54338f42b27520a645fb728276318a4ded54dba7|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=54338f42b27520a645fb728276318a4ded54dba7].
> Overhaul locale support (make Locale#ROOT instead of Locale#ENGLISH default
> and use full locale)
>
>
> Key: DOXIASITETOOLS-271
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-271
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Integration Tools, Site renderer
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 2.0.0-M4
>
>
> The current locale setup has its flaws:
> * It forces you assume that the default locale is English which leads to
> problems that {{site_en.xml}} is often not found
> * Full locale cannot be used to create a localized site: only language is
> used, no country nor region: region is critical for example for Simplified
> chinese vs Traditional, see MSITE-904
> This overhaul will implement two changes:
> # The default locale will not be English anymore, but rather {{ROOT}} as a
> language-agnostic one.
> # One can provide a full locale and Doxia Sitetools will incrementally reduce
> the locale from variant down to root to find the most specific site
> descriptor, e.g., {{'de_DE_BY', 'de_DE', 'de', ''}}. Assuming that the user
> has requested {{'de_DE_BY'}} as in German in Germany, specifically in Bavaria.
> Both approaches apply the logic from
> [{{ResouceBundle#getBundle()}}|https://docs.oracle.com/javase/8/docs/api/java/util/ResourceBundle.html#getBundle-java.lang.String-java.util.Locale-java.lang.ClassLoader-].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-doxia-sitetools] asfgit merged pull request #67: [DOXIASITETOOLS-271] Overhaul locale support (make Locale#ROOT instead of Locale#ENGLISH default and use full locale)
asfgit merged PR #67: URL: https://github.com/apache/maven-doxia-sitetools/pull/67 -- 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] (MASSEMBLY-941) file permissions removed during assembly:single since 3.2.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638842#comment-17638842 ] Herve Boutemy edited comment on MASSEMBLY-941 at 11/26/22 3:18 PM: --- fixed in https://github.com/apache/maven-assembly-plugin/commit/f42194b6c0e49bedad506821e524be076e839a79 with an IT to check the 3 different results possible given the 3 types of environment: - Windows 644 (executable flag not detected) - *nix with 755 based on umask - *nix with 775 based on different umask was (Author: hboutemy): fixed in https://github.com/apache/maven-assembly-plugin/commit/f42194b6c0e49bedad506821e524be076e839a79 with an IT to check the 3 different results possible given the 3 types of environment: - Windows (executable flag not detected) - *nix with 755 based on umask - *nix with 775 based on different umask > file permissions removed during assembly:single since 3.2.0 > --- > > Key: MASSEMBLY-941 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-941 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: permissions >Affects Versions: 3.2.0, 3.3.0 >Reporter: Christopher Tubbs >Assignee: Herve Boutemy >Priority: Critical > Fix For: next-release > > > Since 3.2.0, existing file permissions seem to be ignored when creating a > tarball assembly, and files stored in the assembly do not have their original > file permissions preserved. > Using version 3.1.1 of this plugin and earlier, when creating a tar.gz, > existing file permissions are normally preserved. This is now broken in > 3.2.0, unless the component descriptor explicitly sets the fileModes. > This was discovered trying to prepare a release candidate for Apache Accumulo > using the apache-23.pom parent POM's predefined `source-release-tar` > descriptor using the `single` goal. We noticed that the resulting > source-release tarball had stripped all the executable permissions from our > scripts, instead of preserving them. This makes the resulting source release > more difficult to build from source. > A source-release assembly, and any other assembly that does not specify the > file permissions explicitly, should preserve the existing file permissions, > just as it used to with 3.1.1 and earlier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1165) Upgrade plugins and components in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639330#comment-17639330 ] Hudson commented on MSHARED-1165: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-impl » master #35 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-impl/job/master/35/ > Upgrade plugins and components in ITs > - > > Key: MSHARED-1165 > URL: https://issues.apache.org/jira/browse/MSHARED-1165 > 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-M3 > > > * Upgrade Maven Install Plugin to 3.1.0 > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 > * Upgrade Maven Reporting API to 4.0.0-M3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1165) Upgrade plugins and components in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1165. --- Resolution: Fixed Fixed with [ffeaf7e798b2b5d2ef37e2e2f17318ec2dc1a6cf|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=ffeaf7e798b2b5d2ef37e2e2f17318ec2dc1a6cf]. > Upgrade plugins and components in ITs > - > > Key: MSHARED-1165 > URL: https://issues.apache.org/jira/browse/MSHARED-1165 > 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-M3 > > > * Upgrade Maven Install Plugin to 3.1.0 > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 > * Upgrade Maven Reporting API to 4.0.0-M3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo
[
https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MSHARED-480:
Assignee: Michael Osipov
Reopening for the moment since I found a non-too-intrusive way to solve this
problem. Will share a possible solution next after Doxia Sitetools 2.0.0-M4
release.
> use maven-site-plugin's site.xml to use site's skin instead of default when
> run as mojo
> ---
>
> Key: MSHARED-480
> URL: https://issues.apache.org/jira/browse/MSHARED-480
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-reporting-impl
>Affects Versions: maven-reporting-impl 2.4
>Reporter: Herve Boutemy
>Assignee: Michael Osipov
>Priority: Minor
>
> currently, when a reporting mojo is not used as maven-site-plugin's report
> but as direct mojo invocation, maven-site-renderer default skin is always
> used: would be more consistent if using site decoration consistently with
> maven-site-plugin
> Or more precisely, I didn't currently find any reporting plugin that did the
> effort to mimic maven-site-plugin's decoration model/skin: every reporting
> plugin I know of uses features of {{maven-reporting-impl}} for site rendring
> (with this known limitation)
> implementing the feature in {{maven-reporting-impl}} will make it accessible
> to any reporting plugin once it upgrades it dependency version
> once done, we can activate skin resources copy, that was commented while
> working on MSHARED-120 (and would not give expected result if skin used is
> not consistent)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSHARED-1160) Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
[ https://issues.apache.org/jira/browse/MSHARED-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1160: Summary: Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 (was: Upgrade Maven Reporting API to 4.0.0-M3) > Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 > > > Key: MSHARED-1160 > URL: https://issues.apache.org/jira/browse/MSHARED-1160 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1165) Upgrade plugins and components in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1165: Description: * Upgrade Maven Install Plugin to 3.1.0 * Upgrade Maven Site Plugin to 4.0.0-M3 * Upgrade Maven Project Info Reports Plugin to 3.4.1 * Upgrade Maven Reporting API to 4.0.0-M3 was: * Upgrade Maven Install Plugin to 3.1.0 * Upgrade Maven Site Plugin to 4.0.0-M3 * Upgrade Maven Project Info Reports Plugin to 3.4.1 > Upgrade plugins and components in ITs > - > > Key: MSHARED-1165 > URL: https://issues.apache.org/jira/browse/MSHARED-1165 > 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-M3 > > > * Upgrade Maven Install Plugin to 3.1.0 > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 > * Upgrade Maven Reporting API to 4.0.0-M3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1165) Upgrade plugins and components in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1165: Description: * Upgrade Maven Install Plugin to 3.1.0 * Upgrade Maven Site Plugin to 4.0.0-M3 * Upgrade Maven Project Info Reports Plugin to 3.4.1 was: * Upgrade Maven Install Plugin to 3.1.0 * Upgrade Maven Site Plugin to 4.0.0-M4 * Upgrade Maven Project Info Reports Plugin to 3.4.1 > Upgrade plugins and components in ITs > - > > Key: MSHARED-1165 > URL: https://issues.apache.org/jira/browse/MSHARED-1165 > 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-M3 > > > * Upgrade Maven Install Plugin to 3.1.0 > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1167) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639288#comment-17639288 ] Hudson commented on MSHARED-1167: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-exec » master #30 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-exec/job/master/30/ > Upgrade plugins in ITs > -- > > Key: MSHARED-1167 > URL: https://issues.apache.org/jira/browse/MSHARED-1167 > 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-M3 > > > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1167) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1167. --- Resolution: Fixed Fixed with [ee34d2762c6c793fb52132621150bcef02dc90bd|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=ee34d2762c6c793fb52132621150bcef02dc90bd]. > Upgrade plugins in ITs > -- > > Key: MSHARED-1167 > URL: https://issues.apache.org/jira/browse/MSHARED-1167 > 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-M3 > > > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1167) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MSHARED-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1167: Component/s: maven-reporting-exec (was: maven-reporting-impl) Fix Version/s: maven-reporting-exec-2.0.0-M3 (was: maven-reporting-impl-4.0.0-M3) Description: * Upgrade Maven Site Plugin to 4.0.0-M3 * Upgrade Maven Project Info Reports Plugin to 3.4.1 was: * Upgrade Maven Install Plugin to 3.1.0 * Upgrade Maven Site Plugin to 4.0.0-M4 * Upgrade Maven Project Info Reports Plugin to 3.4.1 > Upgrade plugins in ITs > -- > > Key: MSHARED-1167 > URL: https://issues.apache.org/jira/browse/MSHARED-1167 > 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-M3 > > > * Upgrade Maven Site Plugin to 4.0.0-M3 > * Upgrade Maven Project Info Reports Plugin to 3.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1166) Upgrade Plexus Utils to 3.5.0
[ https://issues.apache.org/jira/browse/MSHARED-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639263#comment-17639263 ] Hudson commented on MSHARED-1166: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-exec » master #29 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-exec/job/master/29/ > Upgrade Plexus Utils to 3.5.0 > - > > Key: MSHARED-1166 > URL: https://issues.apache.org/jira/browse/MSHARED-1166 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1167) Upgrade plugins in ITs
Michael Osipov created MSHARED-1167: --- Summary: Upgrade plugins in ITs Key: MSHARED-1167 URL: https://issues.apache.org/jira/browse/MSHARED-1167 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-M3 * Upgrade Maven Install Plugin to 3.1.0 * Upgrade Maven Site Plugin to 4.0.0-M4 * Upgrade Maven Project Info Reports Plugin to 3.4.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1163) Upgrade Maven Reporting API to 4.0.0-M3
[ https://issues.apache.org/jira/browse/MSHARED-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639264#comment-17639264 ] Hudson commented on MSHARED-1163: - Build succeeded in Jenkins: Maven » Maven TLP » maven-reporting-exec » master #29 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-reporting-exec/job/master/29/ > Upgrade Maven Reporting API to 4.0.0-M3 > --- > > Key: MSHARED-1163 > URL: https://issues.apache.org/jira/browse/MSHARED-1163 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MSHARED-1166) Upgrade Plexus Utils to 3.5.0
[ https://issues.apache.org/jira/browse/MSHARED-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639241#comment-17639241 ] Michael Osipov edited comment on MSHARED-1166 at 11/26/22 2:29 PM: --- Fixed with [a153cb1e1f801f12b34bf83f127b0a83ae863306|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=a153cb1e1f801f12b34bf83f127b0a83ae863306]. was (Author: michael-o): Fixed with [83a9767f54833b7c18c61a8896df9c086189e3f0|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=83a9767f54833b7c18c61a8896df9c086189e3f0]. > Upgrade Plexus Utils to 3.5.0 > - > > Key: MSHARED-1166 > URL: https://issues.apache.org/jira/browse/MSHARED-1166 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MSHARED-1163) Upgrade Maven Reporting API to 4.0.0-M3
[ https://issues.apache.org/jira/browse/MSHARED-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17639249#comment-17639249 ] Michael Osipov edited comment on MSHARED-1163 at 11/26/22 2:29 PM: --- Fixed with [d9599003a6e4058fbc0cf0848bb0e3569b52affc|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=d9599003a6e4058fbc0cf0848bb0e3569b52affc]. was (Author: michael-o): Fixed with [e072034d600120cadad242c06dc86407c9393322|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=e072034d600120cadad242c06dc86407c9393322]. > Upgrade Maven Reporting API to 4.0.0-M3 > --- > > Key: MSHARED-1163 > URL: https://issues.apache.org/jira/browse/MSHARED-1163 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1163) Upgrade Maven Reporting API to 4.0.0-M3
[ https://issues.apache.org/jira/browse/MSHARED-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1163. --- Resolution: Fixed Fixed with [e072034d600120cadad242c06dc86407c9393322|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=e072034d600120cadad242c06dc86407c9393322]. > Upgrade Maven Reporting API to 4.0.0-M3 > --- > > Key: MSHARED-1163 > URL: https://issues.apache.org/jira/browse/MSHARED-1163 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1166) Upgrade Plexus Utils to 3.5.0
[ https://issues.apache.org/jira/browse/MSHARED-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1166. --- Resolution: Fixed Fixed with [83a9767f54833b7c18c61a8896df9c086189e3f0|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=83a9767f54833b7c18c61a8896df9c086189e3f0]. > Upgrade Plexus Utils to 3.5.0 > - > > Key: MSHARED-1166 > URL: https://issues.apache.org/jira/browse/MSHARED-1166 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1163) Upgrade Maven Reporting API to 4.0.0-M3
[ https://issues.apache.org/jira/browse/MSHARED-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1163: Component/s: maven-reporting-exec (was: maven-reporting-impl) Fix Version/s: maven-reporting-exec-2.0.0-M3 (was: maven-reporting-impl-4.0.0-M3) > Upgrade Maven Reporting API to 4.0.0-M3 > --- > > Key: MSHARED-1163 > URL: https://issues.apache.org/jira/browse/MSHARED-1163 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1166) Upgrade Plexus Utils to 3.5.0
[ https://issues.apache.org/jira/browse/MSHARED-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1166: Component/s: maven-reporting-exec (was: maven-reporting-impl) Fix Version/s: maven-reporting-exec-2.0.0-M3 (was: maven-reporting-impl-4.0.0-M3) > Upgrade Plexus Utils to 3.5.0 > - > > Key: MSHARED-1166 > URL: https://issues.apache.org/jira/browse/MSHARED-1166 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1164) Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
[ https://issues.apache.org/jira/browse/MSHARED-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1164: Fix Version/s: maven-reporting-exec-2.0.0-M3 (was: maven-reporting-impl-4.0.0-M3) > Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 > > > Key: MSHARED-1164 > URL: https://issues.apache.org/jira/browse/MSHARED-1164 > 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-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1166) Upgrade Plexus Utils to 3.5.0
Michael Osipov created MSHARED-1166: --- Summary: Upgrade Plexus Utils to 3.5.0 Key: MSHARED-1166 URL: https://issues.apache.org/jira/browse/MSHARED-1166 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-M3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1164) Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4
[ https://issues.apache.org/jira/browse/MSHARED-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1164: Component/s: maven-reporting-exec (was: maven-reporting-impl) > Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 > > > Key: MSHARED-1164 > URL: https://issues.apache.org/jira/browse/MSHARED-1164 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DOXIASITETOOLS-277) Upgrade L10N Maven Plugin to 1.0.0
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-277. - Resolution: Fixed Fixed with [7bb6eb27ce9580691ccb6014c62dbbeaa2156905|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=7bb6eb27ce9580691ccb6014c62dbbeaa2156905]. > Upgrade L10N Maven Plugin to 1.0.0 > -- > > Key: DOXIASITETOOLS-277 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-277 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-doxia-sitetools] dependabot[bot] commented on pull request #57: Bump l10n-maven-plugin from 1.0-alpha-2 to 1.0.0
dependabot[bot] commented on PR #57: URL: https://github.com/apache/maven-doxia-sitetools/pull/57#issuecomment-1328049729 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-doxia-sitetools] michael-o closed pull request #57: Bump l10n-maven-plugin from 1.0-alpha-2 to 1.0.0
michael-o closed pull request #57: Bump l10n-maven-plugin from 1.0-alpha-2 to 1.0.0 URL: https://github.com/apache/maven-doxia-sitetools/pull/57 -- 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-doxia-sitetools] michael-o commented on pull request #57: Bump l10n-maven-plugin from 1.0-alpha-2 to 1.0.0
michael-o commented on PR #57: URL: https://github.com/apache/maven-doxia-sitetools/pull/57#issuecomment-1328049721 Superseded. -- 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] (DOXIASITETOOLS-277) Upgrade L10N Maven Plugin to 1.0.0
Michael Osipov created DOXIASITETOOLS-277: - Summary: Upgrade L10N Maven Plugin to 1.0.0 Key: DOXIASITETOOLS-277 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-277 Project: Maven Doxia Sitetools Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 2.0.0-M4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-doxia-sitetools] dependabot[bot] commented on pull request #72: Bump plexus-utils from 3.4.2 to 3.5.0
dependabot[bot] commented on PR #72: URL: https://github.com/apache/maven-doxia-sitetools/pull/72#issuecomment-1328048265 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-doxia-sitetools] michael-o closed pull request #72: Bump plexus-utils from 3.4.2 to 3.5.0
michael-o closed pull request #72: Bump plexus-utils from 3.4.2 to 3.5.0 URL: https://github.com/apache/maven-doxia-sitetools/pull/72 -- 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-doxia-sitetools] michael-o commented on pull request #72: Bump plexus-utils from 3.4.2 to 3.5.0
michael-o commented on PR #72: URL: https://github.com/apache/maven-doxia-sitetools/pull/72#issuecomment-1328048254 Superseded. -- 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-275) Upgrade Maven Reporting API to 4.0.0-M3
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DOXIASITETOOLS-275. - Assignee: Michael Osipov Resolution: Fixed Fixed with [1706bf4842cbafee3bc8ac668f3417efd8d66dcb|https://gitbox.apache.org/repos/asf?p=maven-doxia-sitetools.git;a=commit;h=1706bf4842cbafee3bc8ac668f3417efd8d66dcb]. > Upgrade Maven Reporting API to 4.0.0-M3 > --- > > Key: DOXIASITETOOLS-275 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-275 > Project: Maven Doxia Sitetools > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MASSEMBLY-972) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MASSEMBLY-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MASSEMBLY-972: - Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 38 > - > > Key: MASSEMBLY-972 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-972 > Project: Maven Assembly Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dependency-tree] dependabot[bot] commented on pull request #31: Bump slf4j-api from 1.7.36 to 2.0.5
dependabot[bot] commented on PR #31: URL: https://github.com/apache/maven-dependency-tree/pull/31#issuecomment-1328034335 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-tree] slawekjaranowski closed pull request #31: Bump slf4j-api from 1.7.36 to 2.0.5
slawekjaranowski closed pull request #31: Bump slf4j-api from 1.7.36 to 2.0.5 URL: https://github.com/apache/maven-dependency-tree/pull/31 -- 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] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638861#comment-17638861 ] Slawomir Jaranowski commented on MCLEAN-103: Similar checkstye site report has 599 errors. > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638859#comment-17638859 ] Hudson commented on MCLEAN-103: --- Build succeeded in Jenkins: Maven » Maven TLP » maven-clean-plugin » master #26 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-clean-plugin/job/master/26/ > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MASSEMBLY-972) Upgrade maven-plugin parent to 38
Karl Heinz Marbaise created MASSEMBLY-972: - Summary: Upgrade maven-plugin parent to 38 Key: MASSEMBLY-972 URL: https://issues.apache.org/jira/browse/MASSEMBLY-972 Project: Maven Assembly Plugin Issue Type: Dependency upgrade Reporter: Karl Heinz Marbaise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-clean-plugin] dependabot[bot] closed pull request #21: Bump maven-plugins from 35 to 38
dependabot[bot] closed pull request #21: Bump maven-plugins from 35 to 38 URL: https://github.com/apache/maven-clean-plugin/pull/21 -- 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] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MCLEAN-103. -- Resolution: Done > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638857#comment-17638857 ] Karl Heinz Marbaise commented on MCLEAN-103: Done in [e62edebff1ea91539b10fae219d87ebe085e72d8|https://gitbox.apache.org/repos/asf?p=maven-clean-plugin.git;a=commitdiff;h=e62edebff1ea91539b10fae219d87ebe085e72d8] > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-clean-plugin] dependabot[bot] commented on pull request #21: Bump maven-plugins from 35 to 38
dependabot[bot] commented on PR #21: URL: https://github.com/apache/maven-clean-plugin/pull/21#issuecomment-1328030478 Looks like org.apache.maven.plugins:maven-plugins is up-to-date now, so this is no longer needed. -- 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] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638858#comment-17638858 ] Slawomir Jaranowski commented on MENFORCER-438: --- [~khmarbaise] did you check output of checkstyle site report Eg, there is: 4716 errors for enforcer-rules module - is it acceptable for us. Does such report be more usable? > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638856#comment-17638856 ] Hudson commented on MENFORCER-438: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer » master #80 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/80/ > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MENFORCER-438: -- Affects Version/s: 3.1.0 > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MENFORCER-438: -- Fix Version/s: next-release > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MCLEAN-103: --- Affects Version/s: 3.2.0 > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.2.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MCLEAN-103: --- Fix Version/s: 3.3.0 > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MENFORCER-438. - Resolution: Done > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638845#comment-17638845 ] Karl Heinz Marbaise commented on MENFORCER-438: --- Done in [40637c64ae6e60de8bbef101991e2840903286da|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commitdiff;h=40637c64ae6e60de8bbef101991e2840903286da] > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MASSEMBLY-941) file permissions removed during assembly:single since 3.2.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638844#comment-17638844 ] Hudson commented on MASSEMBLY-941: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-assembly-plugin » master #37 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-assembly-plugin/job/master/37/ > file permissions removed during assembly:single since 3.2.0 > --- > > Key: MASSEMBLY-941 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-941 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: permissions >Affects Versions: 3.2.0, 3.3.0 >Reporter: Christopher Tubbs >Assignee: Herve Boutemy >Priority: Critical > Fix For: next-release > > > Since 3.2.0, existing file permissions seem to be ignored when creating a > tarball assembly, and files stored in the assembly do not have their original > file permissions preserved. > Using version 3.1.1 of this plugin and earlier, when creating a tar.gz, > existing file permissions are normally preserved. This is now broken in > 3.2.0, unless the component descriptor explicitly sets the fileModes. > This was discovered trying to prepare a release candidate for Apache Accumulo > using the apache-23.pom parent POM's predefined `source-release-tar` > descriptor using the `single` goal. We noticed that the resulting > source-release tarball had stripped all the executable permissions from our > scripts, instead of preserving them. This makes the resulting source release > more difficult to build from source. > A source-release assembly, and any other assembly that does not specify the > file permissions explicitly, should preserve the existing file permissions, > just as it used to with 3.1.1 and earlier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCLEAN-103) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MCLEAN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MCLEAN-103: -- Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 38 > - > > Key: MCLEAN-103 > URL: https://issues.apache.org/jira/browse/MCLEAN-103 > Project: Maven Clean Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MCLEAN-103) Upgrade maven-plugin parent to 38
Karl Heinz Marbaise created MCLEAN-103: -- Summary: Upgrade maven-plugin parent to 38 Key: MCLEAN-103 URL: https://issues.apache.org/jira/browse/MCLEAN-103 Project: Maven Clean Plugin Issue Type: Dependency upgrade Reporter: Karl Heinz Marbaise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MASSEMBLY-941) file permissions removed during assembly:single since 3.2.0
[ https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MASSEMBLY-941. --- Resolution: Fixed fixed in https://github.com/apache/maven-assembly-plugin/commit/f42194b6c0e49bedad506821e524be076e839a79 with an IT to check the 3 different results possible given the 3 types of environment: - Windows (executable flag not detected) - *nix with 755 based on umask - *nix with 775 based on different umask > file permissions removed during assembly:single since 3.2.0 > --- > > Key: MASSEMBLY-941 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-941 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: permissions >Affects Versions: 3.2.0, 3.3.0 >Reporter: Christopher Tubbs >Assignee: Herve Boutemy >Priority: Critical > Fix For: next-release > > > Since 3.2.0, existing file permissions seem to be ignored when creating a > tarball assembly, and files stored in the assembly do not have their original > file permissions preserved. > Using version 3.1.1 of this plugin and earlier, when creating a tar.gz, > existing file permissions are normally preserved. This is now broken in > 3.2.0, unless the component descriptor explicitly sets the fileModes. > This was discovered trying to prepare a release candidate for Apache Accumulo > using the apache-23.pom parent POM's predefined `source-release-tar` > descriptor using the `single` goal. We noticed that the resulting > source-release tarball had stripped all the executable permissions from our > scripts, instead of preserving them. This makes the resulting source release > more difficult to build from source. > A source-release assembly, and any other assembly that does not specify the > file permissions explicitly, should preserve the existing file permissions, > just as it used to with 3.1.1 and earlier. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-358) Upgrade to PMD 6.52.0
[ https://issues.apache.org/jira/browse/MPMD-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638841#comment-17638841 ] Hudson commented on MPMD-358: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pmd-plugin » master #70 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/70/ > Upgrade to PMD 6.52.0 > - > > Key: MPMD-358 > URL: https://issues.apache.org/jira/browse/MPMD-358 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-assembly-plugin] hboutemy merged pull request #96: MASSEMBLY-941 keep file permission in Reproducible mode
hboutemy merged PR #96: URL: https://github.com/apache/maven-assembly-plugin/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
[jira] [Assigned] (MENFORCER-438) Upgrade maven-plugin parent to 38
[ https://issues.apache.org/jira/browse/MENFORCER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MENFORCER-438: - Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 38 > - > > Key: MENFORCER-438 > URL: https://issues.apache.org/jira/browse/MENFORCER-438 > Project: Maven Enforcer Plugin > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPMD-358) Upgrade to PMD 6.52.0
[ https://issues.apache.org/jira/browse/MPMD-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-358. --- > Upgrade to PMD 6.52.0 > - > > Key: MPMD-358 > URL: https://issues.apache.org/jira/browse/MPMD-358 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MPMD-358) Upgrade to PMD 6.52.0
[ https://issues.apache.org/jira/browse/MPMD-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-358. - Resolution: Fixed > Upgrade to PMD 6.52.0 > - > > Key: MPMD-358 > URL: https://issues.apache.org/jira/browse/MPMD-358 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade > Components: CPD, PMD >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-pmd-plugin] dependabot[bot] closed pull request #102: Bump slf4jVersion from 1.7.36 to 2.0.4
dependabot[bot] closed pull request #102: Bump slf4jVersion from 1.7.36 to 2.0.4 URL: https://github.com/apache/maven-pmd-plugin/pull/102 -- 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-pmd-plugin] dependabot[bot] commented on pull request #102: Bump slf4jVersion from 1.7.36 to 2.0.4
dependabot[bot] commented on PR #102: URL: https://github.com/apache/maven-pmd-plugin/pull/102#issuecomment-1328023720 Superseded by #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
[GitHub] [maven-pmd-plugin] dependabot[bot] opened a new pull request, #105: Bump slf4jVersion from 1.7.36 to 2.0.5
dependabot[bot] opened a new pull request, #105: URL: https://github.com/apache/maven-pmd-plugin/pull/105 Bumps `slf4jVersion` from 1.7.36 to 2.0.5. Updates `slf4j-api` from 1.7.36 to 2.0.5 Commits https://github.com/qos-ch/slf4j/commit/7e62e1e6917e19e6eeb8faf97daa9e2469bc946d;>7e62e1e prepare release 2.0.5 https://github.com/qos-ch/slf4j/commit/d250ad79ebbd46f098b07c0868d1cbc8c09c8d6c;>d250ad7 in jcl-over-slf4j rename LICENSE.TXT as LICENSE, add LICENSE file to log4j-ov... https://github.com/qos-ch/slf4j/commit/3bc58f3e81cfbe5ef9011c5124c0bd13dceee3a9;>3bc58f3 add SecurityManager support https://github.com/qos-ch/slf4j/commit/207bb299c319886aededb999269c1555abb9deae;>207bb29 start work on 2.0.5-SNAPSHOT https://github.com/qos-ch/slf4j/commit/35dd7ff1e75cf83ffb6784a9537ff92c865e78b2;>35dd7ff removed unused META-INF/services entry https://github.com/qos-ch/slf4j/commit/440c2f3000fc0e2d7646f0b3d6e36e8bc2ef2485;>440c2f3 prepare release 2.0.4 https://github.com/qos-ch/slf4j/commit/43a36303e5a2338c22ec9aad5b01a401034eb553;>43a3630 use the class loader that loaded LoggerFactory (instead of the threadContextC... https://github.com/qos-ch/slf4j/commit/557bf7c0bd4e2c2cd85ef389729107461938dd15;>557bf7c [SLF4J-548] Fix ServiceLoader usage in servlet environment https://github.com/qos-ch/slf4j/commit/632410565b26e4d67fc7ef2ce4c212380b4e59d1;>6324105 enhance manifest with capabilities https://github.com/qos-ch/slf4j/commit/e540299d58bc5f53cab3236cc1b2f29281982074;>e540299 edit blurb on release championing Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.5;>compare view Updates `jul-to-slf4j` from 1.7.36 to 2.0.5 Commits https://github.com/qos-ch/slf4j/commit/7e62e1e6917e19e6eeb8faf97daa9e2469bc946d;>7e62e1e prepare release 2.0.5 https://github.com/qos-ch/slf4j/commit/d250ad79ebbd46f098b07c0868d1cbc8c09c8d6c;>d250ad7 in jcl-over-slf4j rename LICENSE.TXT as LICENSE, add LICENSE file to log4j-ov... https://github.com/qos-ch/slf4j/commit/3bc58f3e81cfbe5ef9011c5124c0bd13dceee3a9;>3bc58f3 add SecurityManager support https://github.com/qos-ch/slf4j/commit/207bb299c319886aededb999269c1555abb9deae;>207bb29 start work on 2.0.5-SNAPSHOT https://github.com/qos-ch/slf4j/commit/35dd7ff1e75cf83ffb6784a9537ff92c865e78b2;>35dd7ff removed unused META-INF/services entry https://github.com/qos-ch/slf4j/commit/440c2f3000fc0e2d7646f0b3d6e36e8bc2ef2485;>440c2f3 prepare release 2.0.4 https://github.com/qos-ch/slf4j/commit/43a36303e5a2338c22ec9aad5b01a401034eb553;>43a3630 use the class loader that loaded LoggerFactory (instead of the threadContextC... https://github.com/qos-ch/slf4j/commit/557bf7c0bd4e2c2cd85ef389729107461938dd15;>557bf7c [SLF4J-548] Fix ServiceLoader usage in servlet environment https://github.com/qos-ch/slf4j/commit/632410565b26e4d67fc7ef2ce4c212380b4e59d1;>6324105 enhance manifest with capabilities https://github.com/qos-ch/slf4j/commit/e540299d58bc5f53cab3236cc1b2f29281982074;>e540299 edit blurb on release championing Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.5;>compare view Updates `slf4j-simple` from 1.7.36 to 2.0.5 Commits https://github.com/qos-ch/slf4j/commit/7e62e1e6917e19e6eeb8faf97daa9e2469bc946d;>7e62e1e prepare release 2.0.5 https://github.com/qos-ch/slf4j/commit/d250ad79ebbd46f098b07c0868d1cbc8c09c8d6c;>d250ad7 in jcl-over-slf4j rename LICENSE.TXT as LICENSE, add LICENSE file to log4j-ov... https://github.com/qos-ch/slf4j/commit/3bc58f3e81cfbe5ef9011c5124c0bd13dceee3a9;>3bc58f3 add SecurityManager support https://github.com/qos-ch/slf4j/commit/207bb299c319886aededb999269c1555abb9deae;>207bb29 start work on 2.0.5-SNAPSHOT https://github.com/qos-ch/slf4j/commit/35dd7ff1e75cf83ffb6784a9537ff92c865e78b2;>35dd7ff removed unused META-INF/services entry https://github.com/qos-ch/slf4j/commit/440c2f3000fc0e2d7646f0b3d6e36e8bc2ef2485;>440c2f3 prepare release 2.0.4 https://github.com/qos-ch/slf4j/commit/43a36303e5a2338c22ec9aad5b01a401034eb553;>43a3630 use the class loader that loaded LoggerFactory (instead of the threadContextC... https://github.com/qos-ch/slf4j/commit/557bf7c0bd4e2c2cd85ef389729107461938dd15;>557bf7c [SLF4J-548] Fix ServiceLoader usage in servlet environment https://github.com/qos-ch/slf4j/commit/632410565b26e4d67fc7ef2ce4c212380b4e59d1;>6324105 enhance manifest with capabilities https://github.com/qos-ch/slf4j/commit/e540299d58bc5f53cab3236cc1b2f29281982074;>e540299 edit blurb on release championing Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.5;>compare view 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`. [//]:
[GitHub] [maven-pmd-plugin] adangel merged pull request #104: [MPMD-358] - Upgrade to PMD 6.52.0
adangel merged PR #104: URL: https://github.com/apache/maven-pmd-plugin/pull/104 -- 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-assembly-plugin] michael-o commented on pull request #96: MASSEMBLY-941 keep file permission in Reproducible mode
michael-o commented on PR #96: URL: https://github.com/apache/maven-assembly-plugin/pull/96#issuecomment-1328022890 > > It is not related, I just noticed it. If you really just need a LF then a comment should tell about your intent. > > AFAIK there is nothing related to LF in this PR, then I suppose I should just ignore that comment that looks to me just a mistake (no pun intended, it happens to me also to completely be out of context because I misread something): if you think there is one place in the PR where it applies, please precise the location Agreed. -- 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-doxia-sitetools] michael-o commented on pull request #67: [DOXIASITETOOLS-271] Overhaul locale support (make Locale#ROOT instead of Locale#ENGLISH default and use full locale)
michael-o commented on PR #67: URL: https://github.com/apache/maven-doxia-sitetools/pull/67#issuecomment-1328022817 @hboutemy Fixed spots. -- 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] (MENFORCER-438) Upgrade maven-plugin parent to 38
Karl Heinz Marbaise created MENFORCER-438: - Summary: Upgrade maven-plugin parent to 38 Key: MENFORCER-438 URL: https://issues.apache.org/jira/browse/MENFORCER-438 Project: Maven Enforcer Plugin Issue Type: Dependency upgrade Reporter: Karl Heinz Marbaise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-assembly-plugin] hboutemy commented on pull request #96: MASSEMBLY-941 keep file permission in Reproducible mode
hboutemy commented on PR #96: URL: https://github.com/apache/maven-assembly-plugin/pull/96#issuecomment-1328022605 > It is not related, I just noticed it. If you really just need a LF then a comment should tell about your intent. AFAIK there is nothing related to LF in this PR, then I suppose I should just ignore that comment that looks to me just a mistake (no pun intended, it happens to me also to completely be out of context because I misread something): if you think there is one place in the PR where it applies, please precise the location -- 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
