On 01. 12. 23 15:53, Michael Bien wrote:
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.
The feature should be primarily used to add artifact (e.g.
io-micronaut:micronaut-router:4.1.2) dependencies. But yes, it's
possible to describe a project on local hard disk ... which will most
probably cause an "unsupported" exception.
It is only IMHO safe to add a subproject in the same multiproject in
gradle (not in maven) as a dependency. Maven relies entirely on
artifacts (?).
I could imagine that the implementation would attempt to extract output
artifact's GAV from the identified project and use that.
-S.
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
