[jira] [Commented] (MRESOLVER-244) Deprecate FileTransformer API

2022-12-10 Thread Elliotte Rusty Harold (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645618#comment-17645618
 ] 

Elliotte Rusty Harold commented on MRESOLVER-244:
-

How exactly do these classes OOM? They're just interfaces, and I don't see 
anything fundamentally wrong in the interface design. Where's the 
implementation? 

> Deprecate FileTransformer API
> -
>
> Key: MRESOLVER-244
> URL: https://issues.apache.org/jira/browse/MRESOLVER-244
> Project: Maven Resolver
>  Issue Type: Task
>  Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 1.8.0
>
>
> The FileTransformer API has serious issues about making resolver itself OOM 
> prone. Also, while this API was made part of Resolver public API, it is 
> really unused in resolver (sans that OOM-prone bit).
> For now deprecate without replacement, and for Maven 4 let's see will we end 
> up with Maven API or provide some different, more usable and safe replacement.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (MRESOLVER-244) Deprecate FileTransformer API

2022-04-11 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520342#comment-17520342
 ] 

Hudson commented on MRESOLVER-244:
--

Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #18

See 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/18/

> Deprecate FileTransformer API
> -
>
> Key: MRESOLVER-244
> URL: https://issues.apache.org/jira/browse/MRESOLVER-244
> Project: Maven Resolver
>  Issue Type: Task
>  Components: Resolver
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 1.8.0
>
>
> The FileTransformer API has serious issues about making resolver itself OOM 
> prone. Also, while this API was made part of Resolver public API, it is 
> really unused in resolver (sans that OOM-prone bit).
> For now deprecate without replacement, and for Maven 4 let's see will we end 
> up with Maven API or provide some different, more usable and safe replacement.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (MRESOLVER-244) Deprecate FileTransformer API

2022-03-07 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502483#comment-17502483
 ] 

Hudson commented on MRESOLVER-244:
--

Build unstable in Jenkins: Maven » Maven TLP » maven-resolver » PR-154 #6

See 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/PR-154/6/

> Deprecate FileTransformer API
> -
>
> Key: MRESOLVER-244
> URL: https://issues.apache.org/jira/browse/MRESOLVER-244
> Project: Maven Resolver
>  Issue Type: Task
>  Components: Resolver
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 1.8.0
>
>
> The FileTransformer API has serious issues about making resolver itself OOM 
> prone. Also, while this API was made part of Resolver public API, it is 
> really unused in resolver (sans that OOM-prone bit).
> For now deprecate without replacement, and for Maven 4 let's see will we end 
> up with Maven API or provide some different, more usable and safe replacement.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (MRESOLVER-244) Deprecate FileTransformer API

2022-03-07 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502438#comment-17502438
 ] 

Hudson commented on MRESOLVER-244:
--

Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » PR-157 #3

See 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/PR-157/3/

> Deprecate FileTransformer API
> -
>
> Key: MRESOLVER-244
> URL: https://issues.apache.org/jira/browse/MRESOLVER-244
> Project: Maven Resolver
>  Issue Type: Task
>  Components: Resolver
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 1.8.0
>
>
> The FileTransformer API has serious issues about making resolver itself OOM 
> prone. Also, while this API was made part of Resolver public API, it is 
> really unused in resolver (sans that OOM-prone bit).
> For now deprecate without replacement, and for Maven 4 let's see will we end 
> up with Maven API or provide some different, more usable and safe replacement.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (MRESOLVER-244) Deprecate FileTransformer API

2022-03-05 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501824#comment-17501824
 ] 

Hudson commented on MRESOLVER-244:
--

Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #7

See 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/7/

> Deprecate FileTransformer API
> -
>
> Key: MRESOLVER-244
> URL: https://issues.apache.org/jira/browse/MRESOLVER-244
> Project: Maven Resolver
>  Issue Type: Task
>  Components: Resolver
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 1.8.0
>
>
> The FileTransformer API has serious issues about making resolver itself OOM 
> prone. Also, while this API was made part of Resolver public API, it is 
> really unused in resolver (sans that OOM-prone bit).
> For now deprecate without replacement, and for Maven 4 let's see will we end 
> up with Maven API or provide some different, more usable and safe replacement.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (MRESOLVER-244) Deprecate FileTransformer API

2022-03-05 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501821#comment-17501821
 ] 

Hudson commented on MRESOLVER-244:
--

Build failed in Jenkins: Maven » Ci Reporting Builds Tests » maven-resolver » 
master #2

See 
https://ci-maven.apache.org/job/Maven/job/ci-reporting-test/job/maven-resolver/job/master/2/

> Deprecate FileTransformer API
> -
>
> Key: MRESOLVER-244
> URL: https://issues.apache.org/jira/browse/MRESOLVER-244
> Project: Maven Resolver
>  Issue Type: Task
>  Components: Resolver
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 1.8.0
>
>
> The FileTransformer API has serious issues about making resolver itself OOM 
> prone. Also, while this API was made part of Resolver public API, it is 
> really unused in resolver (sans that OOM-prone bit).
> For now deprecate without replacement, and for Maven 4 let's see will we end 
> up with Maven API or provide some different, more usable and safe replacement.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)