On 01. 12. 23 16:22, Michael Bien wrote:
is this about a convenience action which:
Possibly, but it's mainly about a convenience API that allows (other)
modules to do that.
Currently a "technology" module (micronaut, spring, oracle cloud) that
would like to introduce an artifact to the build, must check
- project type (say gradle/maven)
- based on project type:
maven: use Maven API (ModelUtils.checkModelDependency) to add a
<dependency> child
gradle: do textual edit of build.gradle
It's rather peculiar to make such actions from a "technology" module
that does not directly depend on Maven and Gradle internals, and of
course does not want to reimplement it.
In addition, I'd like to conform to refactoring API that computes the
chane first, then allows to apply it, where the Maven API operation will
directly mutate the POM document.
The result should be nothing more (from API perspective) than add/remove
(artifact) dependency, later maybe update (version change, simple excludes).
Help would be appreciated in thinking out how to possibly integrate sets
of maven/gradle artifact references into Library concept of Java project
common API ... it seems the current impl assumes .jars are present.
-S.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
