[jira] [Commented] (MASSEMBLY-942) Make "single" goal m2e-friendly by using BuildContext

["Tamás Cservenák (Jira)" <ji...@apache.org>]

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

Tamás Cservenák commented on MASSEMBLY-942:
-------------------------------------------

This will be revisited once in future, but not now. Not only that is not trivial work, but I personally would not invest energy into adding some API that is not Apache, is abandoned and clearly dead (not updated for 12 years)... and seems phased out by other emerging projects like [Takari Incremental build|https://github.com/takari/io.takari.incrementalbuild/blob/master/DOCUMENTATION.md#migrating-existing-maven-plugins] is. Obviously Maven needs to do something about this, but jumping on 1st gen of "incremental" API is not gonna happen IMHO (especially as Takari one claims it has Eclipse IDE integration as well).

Considering all these were written by one same person (Igor F), we may need also some cross-board consultations as well... as this is not a trivial task IMHO.

> Make "single" goal m2e-friendly by using BuildContext
> -----------------------------------------------------
>
>                 Key: MASSEMBLY-942
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-942
>             Project: Maven Assembly Plugin
>          Issue Type: Improvement
>          Components: maven-archiver
>            Reporter: Mickael Istria
>            Priority: Major
>
> When using the maven-assembly-plugin "single" goal in Eclipse m2e, it shows the usual errors regarding unsupported goals.
> For best results in m2e (and all consumers, and for non-CLI builds in general), the maven-assembly-plugin should leverage BuildContext and declare m2e capabilities, as described in https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html



--
This message was sent by Atlassian Jira
(v8.20.7#820007)