Hi Scott,

I could not reproduce your issue with the included build. MainApp looks all right, though I noticed something odd in the reported dependencies, that actually could cause things like that.

I'm still investigating...

On 1/26/23 16:01, Scott Palmer wrote:
Interestingly, while making this test case the issue only appeared after I made the included library modular, and even then I had to restart NB for the issue to show up. So I can't be certain if this wasn't also an issue with 17-rc1, as I may not have restarted NB 17-rc1 after making my actual library modular.  Perhaps I only noticed it in NB 17-rc2 because of course NB was restarted.

Zip File attached with an application project and a library project that it uses includeBuild to reference.  If the list drops it due to no attachment rules, I've BCC'd you László.

Open just the "MainApp" project in NB and it will show errors, but the build will work fine.

Regards,

Scott

On Thu, Jan 26, 2023 at 4:22 PM László Kishalmi <laszlo.kisha...@gmail.com> wrote:

    Is this a regression between NB17-rc1 and NB17-rc2 ?

    If I may ask, could you provide a sample project?

    On Thu, Jan 26, 2023 at 12:29 PM Scott Palmer <swpal...@gmail.com>
    wrote:

    > No, all those details are in the libs.versions.toml file.
    >
    > [versions]
    > fxsvg = "1.0.0"
    >
    > [libraries]
    > fxsvg = { module = "com.analogideas.fxsvg:fxsvg", version.ref =
    "fxsvg" }
    >
    > On Thu, Jan 26, 2023 at 3:19 PM László Kishalmi
    <laszlo.kisha...@gmail.com
    > >
    > wrote:
    >
    > > Shoudn't you use the <org>:<module>[:<version>] reference there?
    > >
    > > On Thu, Jan 26, 2023 at 10:46 AM Scott Palmer <swpal...@gmail.com>
    > wrote:
    > >
    > > > I have a project that uses another library I am working on.  The
    > library
    > > is
    > > > not deployed to any artifact repository (i.e. not even the
    maven local
    > > > cache), but it does define a group and name.  I included it
    in the
    > > project
    > > > that uses it as an "included build"
    > > >
    > > > In NB 17-rc1 this project was recognized and the imports
    that referred
    > to
    > > > it didn't show any problems.
    > > > In NB 17-rc2 the import line is marked with an error that
    the package
    > > does
    > > > not exist.
    > > > The project still builds and runs fine, but the IDE thinks
    there are
    > > errors
    > > > because of this.
    > > >
    > > > settings.gradle contains:
    > > >
    > > >     includeBuild '../fxsvg'
    > > >
    > > > and the build.gradle file refers to it as an implementation
    dependency
    > > via
    > > > a reference defined in gradle/libs.versions.toml
    > > >
    > > >     implementation libs.fxsvg
    > > >
    > > >
    > > > Regards,
    > > >
    > > > Scott
    > > >
    > >
    >

Reply via email to