On 01.12.23 08:19, Svata Dedic wrote:
On 01. 12. 23 3:29, Michael Bien wrote:
And why is it not sufficient to (mvn) install the dependency into the
local repo, and then depend on it the regular way?
The API is just an abstraction implemented by project system. So with
Maven project, it will be implemented as an edit into pom.xml. For
gradle, build.gradle will be changed. Similar to current (private)
Dependency API query, which just extracts project dependencies from
pom/build.gradle and presents it. No parallel build system or
additional metadata.
thanks for clarification Svata - I hoped it would work like that, I just
wanted to be sure.
Sounds like a useful feature in some situations. The impl details will
be interesting though, since I am sure someone will try to add a maven
project to a gradle project or vise versa.
best regards && looking forward to try the feature,
-mbien
-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
---------------------------------------------------------------------
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
