[jira] [Commented] (MRELEASE-1106) Target perform failed for non standard pom location

[ https://issues.apache.org/jira/browse/MRELEASE-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854936#comment-17854936 ] Stanislav Spiridonov commented on MRELEASE-1106: No, bisect form what

[jira] [Commented] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737660#comment-17737660 ] Stanislav Spiridonov commented on MNG-6877: --- Anyway, it solves my mine issue (2 p

[jira] [Commented] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737657#comment-17737657 ] Stanislav Spiridonov commented on MNG-6877: --- No, it isn't on project CP.  IMHO I

[jira] [Commented] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737284#comment-17737284 ] Stanislav Spiridonov commented on MNG-6877: --- I think not if it isn't on the proje

[jira] [Comment Edited] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737280#comment-17737280 ] Stanislav Spiridonov edited comment on MNG-6877 at 6/26/23 5:25 PM: -

[jira] [Comment Edited] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737280#comment-17737280 ] Stanislav Spiridonov edited comment on MNG-6877 at 6/26/23 5:22 PM: -

[jira] [Commented] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737280#comment-17737280 ] Stanislav Spiridonov commented on MNG-6877: --- But if I have the apt-processor as d

[jira] [Commented] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737279#comment-17737279 ] Stanislav Spiridonov commented on MNG-6877: --- Your changes work but apt-processor

[jira] [Commented] (MDEP-557) In dependency analysis, support Spring Boot style intentional transitive compile-time dependencies

[ https://issues.apache.org/jira/browse/MDEP-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692064#comment-17692064 ] Stanislav Spiridonov commented on MDEP-557: --- Maybe use some custom analyzer? The

[jira] [Commented] (MRELEASE-1106) Target perform failed for non standard pom location

[ https://issues.apache.org/jira/browse/MRELEASE-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609124#comment-17609124 ] Stanislav Spiridonov commented on MRELEASE-1106: Yes, with M5 it works

[jira] [Updated] (MRELEASE-1106) Target perform failed for non standard pom location

[ https://issues.apache.org/jira/browse/MRELEASE-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Spiridonov updated MRELEASE-1106: --- Description: My project uses the nonstandard location of pom.xml: inside

[jira] [Created] (MRELEASE-1106) Target perform failed for non standard pom location

Stanislav Spiridonov created MRELEASE-1106: -- Summary: Target perform failed for non standard pom location Key: MRELEASE-1106 URL: https://issues.apache.org/jira/browse/MRELEASE-1106 Project:

[jira] [Commented] (MDEP-791) Non-test scoped and transitive dependencies in compile scope

[ https://issues.apache.org/jira/browse/MDEP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494974#comment-17494974 ] Stanislav Spiridonov commented on MDEP-791: --- I agree that it is not a problem of

[jira] [Commented] (MDEP-791) Non-test scoped and transitive dependencies in compile scope

[ https://issues.apache.org/jira/browse/MDEP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494973#comment-17494973 ] Stanislav Spiridonov commented on MDEP-791: --- Hmm... I can reproduce it  MDEP lat

[jira] [Commented] (MDEP-791) Non-test scoped and transitive dependencies in compile scope

[ https://issues.apache.org/jira/browse/MDEP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494954#comment-17494954 ] Stanislav Spiridonov commented on MDEP-791: --- Ok, you understand all correctly but

[jira] [Commented] (MDEP-791) Non-test scoped and transitive dependencies in compile scope

[ https://issues.apache.org/jira/browse/MDEP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494951#comment-17494951 ] Stanislav Spiridonov commented on MDEP-791: --- [~cstamas] - "All the other changes

[jira] [Commented] (MDEP-791) Non-test scoped and transitive dependencies in compile scope

[ https://issues.apache.org/jira/browse/MDEP-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494819#comment-17494819 ] Stanislav Spiridonov commented on MDEP-791: --- I agree with [~elharo] - simple use

[jira] [Comment Edited] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869425#comment-16869425 ] Stanislav Spiridonov edited comment on MCOMPILER-391 at 9/6/21, 12:30 PM: --

[jira] [Updated] (MCOMPILER-418) NPE when --patch-module is used in non-modular Project

[ https://issues.apache.org/jira/browse/MCOMPILER-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Spiridonov updated MCOMPILER-418: --- Description: When "--patch-module" argument with reference to jar is added

[jira] [Created] (MCOMPILER-418) NPE when --patch-module is used in non-modular Project

Stanislav Spiridonov created MCOMPILER-418: -- Summary: NPE when --patch-module is used in non-modular Project Key: MCOMPILER-418 URL: https://issues.apache.org/jira/browse/MCOMPILER-418 Project

[jira] [Commented] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075252#comment-17075252 ] Stanislav Spiridonov commented on MNG-6877: --- Test project: [https://github.com/fo

[jira] [Commented] (MNG-6877) Separate scope for annotation processing

[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070452#comment-17070452 ] Stanislav Spiridonov commented on MNG-6877: --- Ok, I will try. It will take some ti

[jira] [Created] (MNG-6877) Separate scope for annotation processing

Stanislav Spiridonov created MNG-6877: - Summary: Separate scope for annotation processing Key: MNG-6877 URL: https://issues.apache.org/jira/browse/MNG-6877 Project: Maven Issue Type: New

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869426#comment-16869426 ] Stanislav Spiridonov commented on MCOMPILER-391: And I can't find any

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869425#comment-16869425 ] Stanislav Spiridonov commented on MCOMPILER-391: mvn install dependan

[jira] [Updated] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Spiridonov updated MCOMPILER-391: --- Attachment: MCOMPILER-391.zip > annotationProcessorPaths have to follow de

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869420#comment-16869420 ] Stanislav Spiridonov commented on MCOMPILER-391: [INFO] Scanning for p

[jira] [Created] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

Stanislav Spiridonov created MCOMPILER-391: -- Summary: annotationProcessorPaths have to follow dependencyManagement rules Key: MCOMPILER-391 URL: https://issues.apache.org/jira/browse/MCOMPILER-391

[jira] [Created] (MNG-6158) Duplicate transitive dependency with provided and runtime scopes

Stanislav Spiridonov created MNG-6158: - Summary: Duplicate transitive dependency with provided and runtime scopes Key: MNG-6158 URL: https://issues.apache.org/jira/browse/MNG-6158 Project: Maven

[jira] [Created] (MDEP-546) Update project information on plugin site

Stanislav Spiridonov created MDEP-546: - Summary: Update project information on plugin site Key: MDEP-546 URL: https://issues.apache.org/jira/browse/MDEP-546 Project: Maven Dependency Plugin

[jira] [Updated] (MNG-5913) Allows to define the aliases for existing server configuration in settings.xml

[ https://issues.apache.org/jira/browse/MNG-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Spiridonov updated MNG-5913: -- Description: Now the repository (and other server related tags!!!) linked with correspondi

[jira] [Updated] (MNG-5913) Allows to define the aliases for existing server configuration in settings.xml

[ https://issues.apache.org/jira/browse/MNG-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Spiridonov updated MNG-5913: -- Summary: Allows to define the aliases for existing server configuration in settings.xml (

[jira] [Commented] (MNG-5913) Add to repository reference to server configuration

[ https://issues.apache.org/jira/browse/MNG-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962325#comment-14962325 ] Stanislav Spiridonov commented on MNG-5913: --- The SO is just illustrate the issue.

[jira] [Created] (MNG-5913) Add to repository reference to server configuration

Stanislav Spiridonov created MNG-5913: - Summary: Add to repository reference to server configuration Key: MNG-5913 URL: https://issues.apache.org/jira/browse/MNG-5913 Project: Maven Issue

[jira] Commented: (MWAR-35) War packaging fails with long file names

[ http://jira.codehaus.org/browse/MWAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99399 ] Stanislav Spiridonov commented on MWAR-35: -- It is a bug of JDK (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6481

[jira] Commented: (WAGON-73) MirroredWagon infinite loop

[ http://jira.codehaus.org/browse/WAGON-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88626 ] Stanislav Spiridonov commented on WAGON-73: --- I have the same behavior with a mirror of central:

[jira] Commented: (MWAR-35) War packaging fails with long file names

[ http://jira.codehaus.org/browse/MWAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86146 ] Stanislav Spiridonov commented on MWAR-35: -- The bug is reproduced on versions 2.0.2 and 2.0.3-SNAPSHOT. It seems that no