[jira] [Comment Edited] (DOXIATOOLS-84) Parser: Emit Velocity directives and variables in special Sink events

[ https://issues.apache.org/jira/browse/DOXIATOOLS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823354#comment-17823354 ] Konrad Windszus edited comment on DOXIATOOLS-84 at 3/5/24 11:54 AM:

[jira] [Updated] (DOXIATOOLS-84) Parser: Emit Velocity directives and variables in special Sink events

[ https://issues.apache.org/jira/browse/DOXIATOOLS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated DOXIATOOLS-84: -- Description: Velocity is often used together with markup

[jira] [Moved] (DOXIATOOLS-84) Parser: Emit Velocity directives and variables in special Sink events

[ https://issues.apache.org/jira/browse/DOXIATOOLS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus moved DOXIA-729 to DOXIATOOLS-84: - Component/s: Doxia Converter (was:

[jira] [Updated] (DOXIA-729) Parser: Emit Velocity directives and variables in special Sink events

[ https://issues.apache.org/jira/browse/DOXIA-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated DOXIA-729: -- Summary: Parser: Emit Velocity directives and variables in special Sink events (was: Parser:

[jira] [Assigned] (DOXIA-729) Parser: Emit velocity directives and variables in special Sink events

[ https://issues.apache.org/jira/browse/DOXIA-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned DOXIA-729: - Assignee: Konrad Windszus > Parser: Emit velocity directives and variables in special

[jira] [Commented] (DOXIA-729) Parser: Emit velocity directives and variables in special Sink events

[ https://issues.apache.org/jira/browse/DOXIA-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823354#comment-17823354 ] Konrad Windszus commented on DOXIA-729: --- This should be possible to achieve with a special

[jira] [Updated] (SLING-12261) Sling Event: Update to sling-bundle-parent 60

[ https://issues.apache.org/jira/browse/SLING-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12261: Affects Version/s: Event 4.3.14 > Sling Event: Update to sling-bundle-parent 60 >

[jira] [Updated] (SLING-12261) Sling Event: Update to sling-bundle-parent 60

[ https://issues.apache.org/jira/browse/SLING-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12261: Component/s: Event > Sling Event: Update to sling-bundle-parent 60 >

[jira] [Created] (SLING-12261) Sling Event: Update to sling-bundle-parent 60

Konrad Windszus created SLING-12261: --- Summary: Sling Event: Update to sling-bundle-parent 60 Key: SLING-12261 URL: https://issues.apache.org/jira/browse/SLING-12261 Project: Sling Issue

[jira] [Updated] (SLING-12260) Sling Events does not build on Java 21

[ https://issues.apache.org/jira/browse/SLING-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12260: Summary: Sling Events does not build on Java 21 (was: Sling Events does not Build on

[jira] [Updated] (SLING-12260) Sling Events does not Build on Java 21

[ https://issues.apache.org/jira/browse/SLING-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12260: Description: Attempting to build Sling Events with Java 21 fails with: {code:java}

[jira] [Assigned] (SLING-12260) Sling Events does not Build on Java 21

[ https://issues.apache.org/jira/browse/SLING-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-12260: --- Assignee: Konrad Windszus (was: Rishabh Daim) > Sling Events does not Build on

[jira] [Updated] (SLING-12260) Sling Events does not Build on Java 21

[ https://issues.apache.org/jira/browse/SLING-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12260: Fix Version/s: (was: Event 4.3.14) > Sling Events does not Build on Java 21 >

[jira] [Updated] (SLING-12260) Sling Events does not Build on Java 21

[ https://issues.apache.org/jira/browse/SLING-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12260: Reporter: Konrad Windszus (was: Dan Klco) > Sling Events does not Build on Java 21 >

[jira] [Updated] (SLING-12260) Sling Events does not Build on Java 21

[ https://issues.apache.org/jira/browse/SLING-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12260: Affects Version/s: Event 4.3.14 (was: Event 4.3.12) > Sling

[jira] [Created] (SLING-12260) Sling Events does not Build on Java 21

Konrad Windszus created SLING-12260: --- Summary: Sling Events does not Build on Java 21 Key: SLING-12260 URL: https://issues.apache.org/jira/browse/SLING-12260 Project: Sling Issue Type: Bug

[jira] [Resolved] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount

[ https://issues.apache.org/jira/browse/OAK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved OAK-10655. --- Fix Version/s: 1.62.0 Resolution: Fixed Fixed in

[jira] [Commented] (SLING-8702) Investigate automatically onboarding Sling projects to SonarCloud

[ https://issues.apache.org/jira/browse/SLING-8702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822539#comment-17822539 ] Konrad Windszus commented on SLING-8702: I see there is

[jira] [Commented] (SLING-12247) Provide component property type for (External)ResourceChangeListener

[ https://issues.apache.org/jira/browse/SLING-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822538#comment-17822538 ] Konrad Windszus commented on SLING-12247: - [~bellingard] Can you please onboard

[jira] [Resolved] (SLING-12247) Provide component property type for (External)ResourceChangeListener

[ https://issues.apache.org/jira/browse/SLING-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-12247. - Fix Version/s: Resource Observation Annotations 1.0.0 Resolution: Fixed >

[jira] [Commented] (SLING-12246) Support Event.NODE_MOVED in JcrResourceListener

[ https://issues.apache.org/jira/browse/SLING-12246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822513#comment-17822513 ] Konrad Windszus commented on SLING-12246: - I added some more tests in

[jira] [Resolved] (SLING-12246) Support Event.NODE_MOVED in JcrResourceListener

[ https://issues.apache.org/jira/browse/SLING-12246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-12246. - Resolution: Invalid > Support Event.NODE_MOVED in JcrResourceListener >

[jira] [Commented] (HTTPCLIENT-2321) Clarify the default connection manager being used

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822007#comment-17822007 ] Konrad Windszus commented on HTTPCLIENT-2321: - bq. Generally HttpClient builders should

[jira] [Commented] (HTTPCLIENT-2320) Support IPv6 proxy exceptions in OSGiHttpRoutePlanner

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821848#comment-17821848 ] Konrad Windszus commented on HTTPCLIENT-2320: - [~jsedding] I see that the original logic

[jira] [Commented] (HTTPCLIENT-2322) Javadoc lists each class twice

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821845#comment-17821845 ] Konrad Windszus commented on HTTPCLIENT-2322: - Found it:

[jira] [Updated] (MNG-5726) Update OS Activation To Allow Wildcards In OS Version

[ https://issues.apache.org/jira/browse/MNG-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MNG-5726: - Fix Version/s: 4.0.0 4.0.0-alpha-13 > Update OS Activation To Allow Wildcards

[jira] [Resolved] (MNG-5726) Update OS Activation To Allow Wildcards In OS Version

[ https://issues.apache.org/jira/browse/MNG-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MNG-5726. -- Resolution: Fixed > Update OS Activation To Allow Wildcards In OS Version >

[jira] [Comment Edited] (HTTPCLIENT-2321) Clarify the default connection manager being used

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821745#comment-17821745 ] Konrad Windszus edited comment on HTTPCLIENT-2321 at 2/28/24 4:22 PM:

[jira] [Commented] (HTTPCLIENT-2321) Clarify the default connection manager being used

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821745#comment-17821745 ] Konrad Windszus commented on HTTPCLIENT-2321: - Probably listing for each {{setter}} and

[jira] [Created] (HTTPCLIENT-2322) Javadoc lists each class twice

Konrad Windszus created HTTPCLIENT-2322: --- Summary: Javadoc lists each class twice Key: HTTPCLIENT-2322 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2322 Project: HttpComponents

[jira] [Updated] (HTTPCLIENT-2321) Clarify the default connection manager being used

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated HTTPCLIENT-2321: Description: Neither from reading

[jira] [Updated] (HTTPCLIENT-2321) Clarify the default connection manager being used

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated HTTPCLIENT-2321: Description: Neither from reading

[jira] [Created] (HTTPCLIENT-2321) Clarify the default connection manager being used

Konrad Windszus created HTTPCLIENT-2321: --- Summary: Clarify the default connection manager being used Key: HTTPCLIENT-2321 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2321 Project:

[jira] [Commented] (HTTPCLIENT-2320) Support IPv6 proxy exceptions in OSGiHttpRoutePlanner

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820825#comment-17820825 ] Konrad Windszus commented on HTTPCLIENT-2320: - The logic is also not 100% clear to me.

[jira] [Created] (HTTPCLIENT-2320) Support IPv6 proxy exceptions in OSGiHttpRoutePlanner

Konrad Windszus created HTTPCLIENT-2320: --- Summary: Support IPv6 proxy exceptions in OSGiHttpRoutePlanner Key: HTTPCLIENT-2320 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2320 Project:

[jira] [Resolved] (MCOMPILER-577) Rename parameter "forceJavacCompilerUse"

[ https://issues.apache.org/jira/browse/MCOMPILER-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MCOMPILER-577. --- Resolution: Fixed > Rename parameter "forceJavacCompilerUse" >

[jira] [Assigned] (MCOMPILER-577) Rename parameter "forceJavacCompilerUse"

[ https://issues.apache.org/jira/browse/MCOMPILER-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned MCOMPILER-577: - Assignee: Konrad Windszus > Rename parameter "forceJavacCompilerUse" >

[jira] [Updated] (MCOMPILER-577) Rename parameter "forceJavacCompilerUse"

[ https://issues.apache.org/jira/browse/MCOMPILER-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MCOMPILER-577: -- Description: The name {{forceJavacCompilerUse}}

[jira] [Updated] (MCOMPILER-577) Rename parameter "forceJavacCompilerUse"

[ https://issues.apache.org/jira/browse/MCOMPILER-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MCOMPILER-577: -- Description: The name {{forceJavacCompilerUse}}

[jira] [Created] (MCOMPILER-577) Rename parameter "forceJavacCompilerUse"

Konrad Windszus created MCOMPILER-577: - Summary: Rename parameter "forceJavacCompilerUse" Key: MCOMPILER-577 URL: https://issues.apache.org/jira/browse/MCOMPILER-577 Project: Maven Compiler Plugin

[jira] [Resolved] (MCOMPILER-570) Javadoc: Add link to javac references from JDK17

[ https://issues.apache.org/jira/browse/MCOMPILER-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MCOMPILER-570. --- Resolution: Fixed > Javadoc: Add link to javac references from JDK17 >

[jira] [Resolved] (MCOMPILER-576) Deprecate parameter "compilerVersion"

[ https://issues.apache.org/jira/browse/MCOMPILER-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MCOMPILER-576. --- Resolution: Fixed > Deprecate parameter "compilerVersion" >

[jira] [Updated] (MCOMPILER-570) Javadoc: Add link to javac references from JDK17

[ https://issues.apache.org/jira/browse/MCOMPILER-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MCOMPILER-570: -- Fix Version/s: next-release > Javadoc: Add link to javac references from JDK17 >

[jira] [Assigned] (MCOMPILER-570) Javadoc: Add link to javac references from JDK17

[ https://issues.apache.org/jira/browse/MCOMPILER-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned MCOMPILER-570: - Assignee: Konrad Windszus > Javadoc: Add link to javac references from JDK17

[jira] [Closed] (MCOMPILER-573) Deprecate parameter "compilerVersion"

[ https://issues.apache.org/jira/browse/MCOMPILER-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus closed MCOMPILER-573. - Resolution: Duplicate > Deprecate parameter "compilerVersion" >

[jira] [Assigned] (MCOMPILER-576) Deprecate parameter "compilerVersion"

[ https://issues.apache.org/jira/browse/MCOMPILER-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned MCOMPILER-576: - Assignee: Konrad Windszus > Deprecate parameter "compilerVersion" >

[jira] [Created] (MCOMPILER-576) Deprecate parameter "compilerVersion"

Konrad Windszus created MCOMPILER-576: - Summary: Deprecate parameter "compilerVersion" Key: MCOMPILER-576 URL: https://issues.apache.org/jira/browse/MCOMPILER-576 Project: Maven Compiler Plugin

[jira] [Assigned] (MNG-5726) Update OS Activation To Allow Wildcards In OS Version

[ https://issues.apache.org/jira/browse/MNG-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned MNG-5726: Assignee: Konrad Windszus > Update OS Activation To Allow Wildcards In OS Version >

[jira] [Resolved] (MNG-8019) Streamline update policy of pluginRepository/repository of Maven Central in Super POM

[ https://issues.apache.org/jira/browse/MNG-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MNG-8019. -- Fix Version/s: 3.9.7 (was: 3.9.x-candidate) Resolution: Fixed

[jira] [Comment Edited] (MNG-5726) Update OS Activation To Allow Wildcards In OS Version

[ https://issues.apache.org/jira/browse/MNG-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819226#comment-17819226 ] Konrad Windszus edited comment on MNG-5726 at 2/21/24 12:52 PM: Currently

[jira] [Comment Edited] (MNG-5726) Update OS Activation To Allow Wildcards In OS Version

[ https://issues.apache.org/jira/browse/MNG-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819226#comment-17819226 ] Konrad Windszus edited comment on MNG-5726 at 2/21/24 12:52 PM: Currently

[jira] [Commented] (MNG-5726) Update OS Activation To Allow Wildcards In OS Version

[ https://issues.apache.org/jira/browse/MNG-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819226#comment-17819226 ] Konrad Windszus commented on MNG-5726: -- Currently this is based on a string comparison in

[jira] [Assigned] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount

[ https://issues.apache.org/jira/browse/OAK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned OAK-10655: - Assignee: Konrad Windszus > Improve warning emitted for Unexpected changes performed on

[jira] [Updated] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount

[ https://issues.apache.org/jira/browse/OAK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated OAK-10655: -- Description: Currently the feature provided in OAK-9208 emits WARNs like the following {code}

[jira] [Created] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount

Konrad Windszus created OAK-10655: - Summary: Improve warning emitted for Unexpected changes performed on a non-default mount Key: OAK-10655 URL: https://issues.apache.org/jira/browse/OAK-10655

[jira] [Resolved] (SLING-12252) Remove maven-plugin-annotations from dependencyManagement

[ https://issues.apache.org/jira/browse/SLING-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-12252. - Resolution: Fixed [~sjaranowski] Thanks for the PR. I just applied it. Fixed in

[jira] [Assigned] (SLING-12252) Remove maven-plugin-annotations from dependencyManagement

[ https://issues.apache.org/jira/browse/SLING-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-12252: --- Assignee: Konrad Windszus > Remove maven-plugin-annotations from

[jira] [Commented] (JCRVLT-745) Stashing: naming and folder location

[ https://issues.apache.org/jira/browse/JCRVLT-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817507#comment-17817507 ] Konrad Windszus commented on JCRVLT-745: I can't answer those questions. [~tripod] Do you

[jira] [Commented] (MNG-5585) match server credentials based on server realm

[ https://issues.apache.org/jira/browse/MNG-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817380#comment-17817380 ] Konrad Windszus commented on MNG-5585: -- This requires some changes on resolver side: MRESOLVER-495. >

[jira] [Assigned] (JCRVLT-746) Exclude items are not added to WorkspaceFilter in RCP

[ https://issues.apache.org/jira/browse/JCRVLT-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned JCRVLT-746: -- Assignee: Konrad Windszus > Exclude items are not added to WorkspaceFilter in RCP >

[jira] [Updated] (JCRVLT-746) Exclude items are not added to WorkspaceFilter in RCP

[ https://issues.apache.org/jira/browse/JCRVLT-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCRVLT-746: --- Component/s: RCP (was: vlt) > Exclude items are not added to

[jira] [Resolved] (JCRVLT-746) Exclude items are not added to WorkspaceFilter in RCP

[ https://issues.apache.org/jira/browse/JCRVLT-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved JCRVLT-746. Resolution: Fixed Fixed in

[jira] [Updated] (JCRVLT-746) Exclude items are not added to WorkspaceFilter in RCP

[ https://issues.apache.org/jira/browse/JCRVLT-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCRVLT-746: --- Fix Version/s: 3.7.4 > Exclude items are not added to WorkspaceFilter in RCP >

[jira] [Assigned] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned MNG-8050: Assignee: Konrad Windszus > Same repositories IDs in settings.xml and POM are not detected

[jira] [Comment Edited] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817081#comment-17817081 ] Konrad Windszus edited comment on MNG-8050 at 2/13/24 5:18 PM: --- Overwriting

[jira] [Comment Edited] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817081#comment-17817081 ] Konrad Windszus edited comment on MNG-8050 at 2/13/24 5:18 PM: --- Overwriting

[jira] [Comment Edited] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817081#comment-17817081 ] Konrad Windszus edited comment on MNG-8050 at 2/13/24 5:17 PM: --- Overwriting

[jira] [Comment Edited] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817081#comment-17817081 ] Konrad Windszus edited comment on MNG-8050 at 2/13/24 4:59 PM: --- Overwriting

[jira] [Commented] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817081#comment-17817081 ] Konrad Windszus commented on MNG-8050: -- Overwriting of the POM repository with the repository having

[jira] [Comment Edited] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816933#comment-17816933 ] Konrad Windszus edited comment on MNG-8050 at 2/13/24 11:48 AM: The problem

[jira] [Updated] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MNG-8050: - Description: When the same repository ID is used in repositories defined in  # {{settings.xml}}

[jira] [Commented] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816933#comment-17816933 ] Konrad Windszus commented on MNG-8050: -- The problem is that validation happens separately for settings

[jira] [Updated] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

[ https://issues.apache.org/jira/browse/MNG-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MNG-8050: - Description: When the same repository ID is used in repositories defined in  # {{settings.xml}}

[jira] [Created] (MNG-8050) Same repositories IDs in settings.xml and POM are not detected

Konrad Windszus created MNG-8050: Summary: Same repositories IDs in settings.xml and POM are not detected Key: MNG-8050 URL: https://issues.apache.org/jira/browse/MNG-8050 Project: Maven

[jira] [Comment Edited] (MRESOLVER-495) Provide AuthenticationSelector based on host/realm instead of repository id

[ https://issues.apache.org/jira/browse/MRESOLVER-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816900#comment-17816900 ] Konrad Windszus edited comment on MRESOLVER-495 at 2/13/24 9:09 AM:

[jira] [Comment Edited] (MRESOLVER-495) Provide AuthenticationSelector based on host/realm instead of repository id

[ https://issues.apache.org/jira/browse/MRESOLVER-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816900#comment-17816900 ] Konrad Windszus edited comment on MRESOLVER-495 at 2/13/24 8:42 AM:

[jira] [Commented] (MRESOLVER-495) Provide AuthenticationSelector based on host/realm instead of repository id

[ https://issues.apache.org/jira/browse/MRESOLVER-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816900#comment-17816900 ] Konrad Windszus commented on MRESOLVER-495: --- Currently the {{AuthenticationContext}} being

[jira] [Updated] (MRESOLVER-495) Provide AuthenticationSelector based on host/realm instead of repository id

[ https://issues.apache.org/jira/browse/MRESOLVER-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MRESOLVER-495: -- Summary: Provide AuthenticationSelector based on host/realm instead of repository

[jira] [Updated] (MRESOLVER-495) Provide AuthenticationSelector based on host instead of repository id

[ https://issues.apache.org/jira/browse/MRESOLVER-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MRESOLVER-495: -- Description: Currently the

[jira] [Commented] (MRESOLVER-495) Provide AuthenticationSelector based on host instead of repository id

[ https://issues.apache.org/jira/browse/MRESOLVER-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816891#comment-17816891 ] Konrad Windszus commented on MRESOLVER-495: --- Thanks, I linked some related ticket in Maven

[jira] [Created] (MRESOLVER-495) Provide AuthenticationSelector based on host instead of repository id

Konrad Windszus created MRESOLVER-495: - Summary: Provide AuthenticationSelector based on host instead of repository id Key: MRESOLVER-495 URL: https://issues.apache.org/jira/browse/MRESOLVER-495

[jira] [Updated] (SCM-1015) Clarify difference between ScmManager and ScmProvider

[ https://issues.apache.org/jira/browse/SCM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SCM-1015: - Description: I was assuming that {{ScmProvider}} is the SPI while {{ScmManager}} is the

[jira] [Created] (SCM-1015) Clarify difference between ScmManager and ScmProvider

Konrad Windszus created SCM-1015: Summary: Clarify difference between ScmManager and ScmProvider Key: SCM-1015 URL: https://issues.apache.org/jira/browse/SCM-1015 Project: Maven SCM Issue

[jira] [Resolved] (SLING-12249) Clarify "ADDED" resource changes for ancestor nodes of path

[ https://issues.apache.org/jira/browse/SLING-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-12249. - Fix Version/s: API 2.27.4 Resolution: Fixed Fixed in

[jira] [Commented] (JCRVLT-744) Vaults do not handle multi workspace environments

[ https://issues.apache.org/jira/browse/JCRVLT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816544#comment-17816544 ] Konrad Windszus commented on JCRVLT-744: I think the issue with the session is not only with

[jira] [Commented] (JCRVLT-744) Vaults do not handle multi workspace environments

[ https://issues.apache.org/jira/browse/JCRVLT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816441#comment-17816441 ] Konrad Windszus commented on JCRVLT-744: FileVault API is always bound to a JCR session which is

[jira] [Assigned] (SCM-914) InfoItem.lastChangedDate is leaky abstraction

[ https://issues.apache.org/jira/browse/SCM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SCM-914: --- Assignee: Konrad Windszus > InfoItem.lastChangedDate is leaky abstraction >

[jira] [Comment Edited] (SCM-914) InfoItem.lastChangedDate is leaky abstraction

[ https://issues.apache.org/jira/browse/SCM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816073#comment-17816073 ] Konrad Windszus edited comment on SCM-914 at 2/9/24 2:43 PM: - This would be

[jira] [Comment Edited] (SCM-914) InfoItem.lastChangedDate is leaky abstraction

[ https://issues.apache.org/jira/browse/SCM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816073#comment-17816073 ] Konrad Windszus edited comment on SCM-914 at 2/9/24 2:10 PM: - This would be

[jira] [Commented] (SCM-914) InfoItem.lastChangedDate is leaky abstraction

[ https://issues.apache.org/jira/browse/SCM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816073#comment-17816073 ] Konrad Windszus commented on SCM-914: - This would be interesting in the context of DOXIASITETOOLS-329 as

[jira] [Comment Edited] (DOXIASITETOOLS-329) Expose lastModification date in addition to publishDate in Velocity Context

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814869#comment-17814869 ] Konrad Windszus edited comment on DOXIASITETOOLS-329 at 2/9/24 1:51 PM:

[jira] [Comment Edited] (DOXIASITETOOLS-329) Expose lastModification date in addition to publishDate in Velocity Context

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814869#comment-17814869 ] Konrad Windszus edited comment on DOXIASITETOOLS-329 at 2/9/24 1:48 PM:

[jira] [Comment Edited] (DOXIASITETOOLS-329) Expose lastModification date in addition to publishDate in Velocity Context

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814869#comment-17814869 ] Konrad Windszus edited comment on DOXIASITETOOLS-329 at 2/9/24 1:48 PM:

[jira] [Resolved] (MSCMPUB-63) Rely on DefaultScmRepositoryConfigurator from maven-release for extracting credentials from settings.xml

[ https://issues.apache.org/jira/browse/MSCMPUB-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MSCMPUB-63. Fix Version/s: 3.2.2 Resolution: Fixed Fixed in

[jira] [Commented] (SLING-12249) Clarify "ADDED" resource changes for ancestor nodes of path

[ https://issues.apache.org/jira/browse/SLING-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815995#comment-17815995 ] Konrad Windszus commented on SLING-12249: - [~cziegeler] I would appreciate a review on the

[jira] [Resolved] (DOXIA-728) MarkdownSink: Support blockquotes

[ https://issues.apache.org/jira/browse/DOXIA-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved DOXIA-728. --- Resolution: Fixed Fixed in

[jira] [Updated] (DOXIA-728) MarkdownSink: Support blockquotes

[ https://issues.apache.org/jira/browse/DOXIA-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated DOXIA-728: -- Fix Version/s: 2.0.0-M10 > MarkdownSink: Support blockquotes >

[jira] [Resolved] (MRELEASE-1139) Improve logging for used credentials in DefaultScmRepositoryConfigurator

[ https://issues.apache.org/jira/browse/MRELEASE-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MRELEASE-1139. --- Fix Version/s: 3.0.2 Resolution: Fixed Fixed in

[jira] [Created] (MSCMPUB-63) Rely on DefaultScmRepositoryConfigurator from maven-release for extracting credentials from settings.xml

Konrad Windszus created MSCMPUB-63: -- Summary: Rely on DefaultScmRepositoryConfigurator from maven-release for extracting credentials from settings.xml Key: MSCMPUB-63 URL:

[jira] [Resolved] (MSCMPUB-61) Leverage the distributionManagement.site.id by default for parameter "serverId"

[ https://issues.apache.org/jira/browse/MSCMPUB-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved MSCMPUB-61. Fix Version/s: 3.2.2 Resolution: Fixed Fixed in

<    1   2   3   4   5   6   7   8   9   10   >