On 01.12.23 16:00, Svata Dedic wrote:
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
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.
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
The vote on Apache NetBeans 20 (vc1) is now closed with a result of
11 +1 binding votes,
6 +1 votes from community members.
There were 0 -1 votes.
This means we can proceed with the release of Apache NetBeans 20.
Thanks everyone!
Full results of the vote are as follow -
+1
Hi,
[X] yes / +1
[ ] no / -1 (please justify -1)
[X] binding (member of PMC)
My vote is based on
[X] I have built and tested the source with openjdk "11.0.20" 2023-07-18 on
Ubuntu 22.04 wsl
[X] I have tested the Maven artefacts
I will close the vote.
Best Regards
Eric
-Message
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
