Well, if I see well, you try to bring the jvi-cmd:run task down to the
project level by defining a task that depends on that.
The defined run task would be a DefaultTask, so it is not taking the
--debug-jvm argument.
Here instead of defining a new run task, I'd configure the ide's run and
de
On 9/22/22 9:15 AM, László Kishalmi wrote:
You may find reading this one useful:
https://docs.gradle.org/current/userguide/composite_builds.html
Thanks, this looks promising. I started, only for one project, with
settings.gradle
rootProject.name = 'jvi-ide'
includeBuild '/src/jvi-dev/j
You may find reading this one useful:
https://docs.gradle.org/current/userguide/composite_builds.html
On Thu, Sep 22, 2022 at 7:43 AM Ernie Rael wrote:
> Thanks László,
>
> Since I got thing back in sync, have not seen the problem. I tried what
> I think were similar steps, it /did not reproduce
Hi,
Private and friend module will still be there.
But the javadoc is limited to public signature and package.
If there is a private field/method in a class from a published javadoc it twill
not be accessible. I guess this like that since a long time.
Best Regards,
Eric
-Message d'origine-
Hello,
You have a very good example here:
https://github.com/junichi11/netbeans-color-codes-preview
BTW, it is a very useful plugin that I would expect be part of core NB
eventually.
Hope it helps.
Cheers,
JM
On Sun, Sep 11, 2022 at 3:20 PM Christian Lenz
wrote:
> Hey Peter,
>
> you can ha
Hi Eric,
Thank you for the job.
There is one thing that I am unsure to have properly understood. As a NBP
advanced user, I often refer and use the Javadoc of private and friend
modules.
Will the new site still provide it for the DEV version (currently on
bits.netbeans.org it is broken)?
This i
