On Mon, 18 Dec 2023 at 12:25, Svata Dedic wrote:
>
> Will check, thanks.
>
> Anything is possible until the API matures and goes public, tentative
> timeframe is NB23. I am willing to adapt 'early adopter' code, we now
> need for Oracle exensions, of course.
Restarting this conversation as reques
Will check, thanks.
Anything is possible until the API matures and goes public, tentative
timeframe is NB23. I am willing to adapt 'early adopter' code, we now
need for Oracle exensions, of course.
-S.
On 18. 12. 23 13:04, Neil C Smith wrote:
On Wed, 29 Nov 2023 at 19:24, Svata Dedic wrote
On Wed, 29 Nov 2023 at 19:24, Svata Dedic wrote:
> I am working (finishing) on an extension of (still private) Project
> Dependency API that would allow to *add* dependency to a project (and
> also remove). This is a change that will span both Maven and Gradle
> modules, so I thought I'll put a no
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 buil
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 prima
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-mic
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
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
Hi Svata,
lets say project A sets a dependency on project B and project
dependencies are an IDE feature. How will project A build outside of the
IDE?
And why is it not sufficient to (mvn) install the dependency into the
local repo, and then depend on it the regular way?
I don't doubt that
Hi,
I am working (finishing) on an extension of (still private) Project
Dependency API that would allow to *add* dependency to a project (and
also remove). This is a change that will span both Maven and Gradle
modules, so I thought I'll put a note in advance, but PR will be landing
shortly in
10 matches
Mail list logo
