Re: nb-javac for building NetBeans itself

[Neil C Smith]

On Sun, 30 Oct 2022, 18:40 Jaroslav Tulach, 
wrote:

> Dne úterý 25. října 2022 11:02:07 CET, Neil C Smith napsal(a):
> > On Tue, 25 Oct 2022 at 08:06, Jaroslav Tulach 
>
> wrote:
> > >  JDK `javac` drops support for old `-target` versions. E.g. version 11
> can
> > >  no>
> > > longer target 1.5 bytecode:
> >
> > Doesn't that take nb-javac beyond ever being just an automated
> > backport of the current javac to run on older JDK?
>
> nb-javac is an automated backport of the latest JDK's javac to run on
> JDK8+.
> No change here.
>
> > I'm confused!
>

Yep, still confused!

How do you plan to backport the latest javac while also including support
for removed older targets? Add all the removed code back in?

Or are we talking different versions of nb-javac for compiling the IDE than
used in editor support?

I don't see much issue with requiring older JDKs to compile older NetBeans
personally - it's probably less likely to break than assuming the old
compiler code runs correctly on JDK 33+ ...

Best wishes,

Neil

Re: Test Netbeans PR on Mavenized NB Platform application

[Jaroslav Tulach]

Long time no see, Mathieu!

There is a staging repository: https://repository.apache.org/content/groups/
staging/org/netbeans/modules/ but it looks a bit outdated.

Eric, is that intended or shall we be producing NetBeans dev bits regularly?
-jt



Dne sobota 8. října 2022 21:22:07 CET, Mathieu Bastian napsal(a):
> Hi folks,
> 
> I was called out in a recent PR
>  to
> test it with my NB Platform application. I'm willing to do so but I need
> some guidance.
> 
> My application is mavenized. What is the simplest way to test this PR
> locally with the dev version of Netbeans? For instance, can I create a
> "RELEASE160-SNAPSHOT" version locally via a command? If I had this, I could
> easily switch my application's NB Platform version to this dev version and
> test the change.
> 
> Much appreciated!
> 
> Mathieu





-
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

Building with proxies causes DoS attack on OSU

[John Neffenger]

As the progress on my pull request has stalled, I'm starting over with a 
proper bug report:


  Building with proxies causes DoS attack on OSU
  https://github.com/apache/netbeans/issues/4890

  "Building NetBeans in an environment that defines both proxy 
variables causes a brief denial-of-service (DoS) attack on one of the 
Web servers hosted by the Oregon State University (OSU) Open Source Lab."


I am grateful to Michael Bien and Matthias Bläsing for providing an 
initial review of my pull request back in June. I hope this bug report 
can let us come to an agreement on the problem without the distractions 
of a proposed fix.


Thank you,
John

-
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

Re: [DISCUSS] Drop separate platform source and binary zip from release artefacts?

[Jaroslav Tulach]

Drop them.

I do care about NetBeans Platform, but people who use it shall use Maven 
artifacts to begin with these days.

If they really want a ZIP distribution, they can download IDE and keep just 
the platform cluster.

-jt

Dne čtvrtek 20. října 2022 12:28:16 CET, Neil C Smith napsal(a):
> Hi All,
> 
> Every release we include source and binary zip artefacts for the
> platform alone.  eg.
> https://dist.apache.org/repos/dist/release/netbeans/netbeans-platform/15/
> 
> Even the source zip is treated as an artefact of the main release.
> It's not voted on separately, and I don't know how many other people
> bother to check them?
> 
> They seem like an added complexity to the release process with minimal
> benefit (and a few issues). I'm not sure we link them in from
> anywhere?  I'm not sure if there's much of a need for them?
> 
> So, does anyone have a good argument or use case for continuing to
> include these?  Otherwise, I plan not to include them as artefacts in
> the next (NB16) release vote.
> 
> Thanks,
> 
> Neil
> 
> -
> 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

Re: parent.relativePath warning on Windows

[Mark Eggers]

Answers in-line. Thanks for any thoughts.

On 10/30/2022 6:53 AM, Eric Bresie wrote:

1. Is the sub-projects within the parent projects folder structure or
external?


The project is nested per Maven recommendations. The project was created 
within NetBeans using the process I outlined in the original message.



2. In the "parent" pom, did the "modules" for the sub-projects get
defined?


  


MyServerModule


MyClientModule


MyPoCModule

  

Note the extra blank lines.


3. In the sub-projects, did the parent pom coordinates get included?


Yes, the parent element looks like the following (again, created by 
NetBeans).



MyModules
org.mdeggers
1.0-SNAPSHOT



4. Which environment is maven running in on Windows (i.e. basic jar on
path based or installed in a Cygwin type environment)?



The Maven that is being run is included with NetBeans 16-rc2. I normally 
run an installed NetBeans by specifying it in Tools->Options->Java->Maven.


Both are mavem 3.8.6.

On the command line maven is in my path (specified by a set of 
environment variables) and unpacked in a Windows sub-directory.


I do not have any Java tools installed in either Cygwin or WSL2.

Again, NetBeans 13  (running on JDK 11) opens this project structure 
with no errors.


. . . . just my two cents.
/mde/



Eric Bresie
ebre...@gmail.com


On Thu, Oct 27, 2022 at 6:07 PM Mark Eggers 
wrote:


It appears that images are stripped from the list.

The following should work:

https://i.postimg.cc/MpmPxK2n/module-error-edited.png

/mde/

On 10/27/2022 3:50 PM, Mark Eggers wrote:

Folks,

I am getting a warning about multi-module project structures and
parent.relativePath, but only on Windows (see screen shot).

To recreate:

1. Create a POM project
2. Right-mouse click on modules, and create a new module (Java

application)

3. Go into that new module and look at the created pom.xml

You'll get the warning (see screen shot) that the parent.relativePath
points to the module, rather than to the parent.

The project structure created by NetBeans (14,15,16-rc2) is correct, but
the warning IMO is not. This warning does not appear on Windows in
NetBeans <= 13.

I created this screen shot in the following environment.

Windows 10 Professional
Java 17.0.3+7
NetBeans 16-rc2 (unpacked from the zip file)

The following items were added to netbeans.conf:

# adding UTF-8 and fontsize at the end
netbeans_default_options=" . . . . -J-Dfile.encoding=UTF-8 --fontsize 14"

# location of JDK 17 - run JDK 11 by default on this machine
netbeans_jdkhome="D:\Programs-x64\Java\jdk-17.0.3+7"

I did not import any settings, and did not pre-activate any modules.

Right now since it's a warning, I just ignore it.

Please also note in the screen shot, pom.xml is created with Unix (LF)
endings instead of Windows (CRLF) endings. However, a Java Web
application created as a module in this project shows Windows (CRLF) for
pom.xml

The warnings do not show up when following the same procedure on Ubuntu
20.04.1.

Could this be due to line ending confusion? I have the following project
structure:

MyModules - pom.xml is in Unix (LF) format (POM project)
 |
 MyServerModule - pom.xml is in Unix (LF) format (Java application)
 |
 MyClientModule - pom.xml is in Windows (CRLF) format (Web

application)

 |
 MyPoCModule - pom.xml is in Windows (CRLF) format (Web application)

If someone can point me in the general direction of where to look, I'd
be happy to try and narrow it down further.

. . . just my two cents
/mde/


-
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









-
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

Jackpot has to run on ancient JDK was: nb-javac for building NetBeans itself

[Jaroslav Tulach]

> This would mean that NB_the_IDE (not the platform) would not be able to
> _run_ on JDK 8 anymore (thunder in the background), it would be locked
> to the current JDK release which is already conveniently synced with
> NB's release cycle.


Michael,
NetBeans Platform needs portability. We have to be able to run on JDK8 
including our Java related tools.

Here is my take on that: https://lists.apache.org/thread/
3pt699bs18g1xp6tw8bdno82bqtrrj8b

Plus there is another reason that has just come to my mind: Jackpot. Jackpot 
is a build tool and as such it also needs portability. If we want to increase 
usage of Jackpot in other project, we need to give them freedom to choose 
their JDK and stop thinking about requiring them to run on the latest JDK!

-jt




-
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

Re: nb-javac for building NetBeans itself

[Jaroslav Tulach]

Dne středa 26. října 2022 22:53:13 CET, Eric Bresie napsal(a):
> Sorry I’m not in the know here from a who developed what but…
> 
> Since the below is forked from
> 
> https://github.com/oracle/nb-javac
> 
> Is that going to be a problem?
> 
> Or is that the beauty of open source development (i.e. fork it, enhance it,
> rebrand it [maybe nb-jc], etc. - license permitting)?

Hello Eric,
it is the beauty of open source development. Original maintainers give up on 
the project and I took over with the help of few friends. The nb-javac 
development is happening at https://github.com/JaroslavTulach/nb-javac/ now.

-jt


> > I take the above back -- nb-javac is developed by Jaroslav Tulach, and
> > whoever contributes, e.g., Dusan Balek.
> > 
> > https://github.com/JaroslavTulach/nb-javac/
> > 
> > Where should it be, Neil? It can't be here at Apache because of its
> > licensing. Isn't it fine where it is and under active development via
> > Jaroslav and others?
> > 
> > Where should it be on Maven Central where it is not versus where it is
> 
> now?
> 
> > Gj





-
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

Re: nb-javac for building NetBeans itself

[Jaroslav Tulach]

Dne úterý 25. října 2022 11:02:07 CET, Neil C Smith napsal(a):
> On Tue, 25 Oct 2022 at 08:06, Jaroslav Tulach  
wrote:
> >  JDK `javac` drops support for old `-target` versions. E.g. version 11 can
> >  no> 
> > longer target 1.5 bytecode:
> 
> Doesn't that take nb-javac beyond ever being just an automated
> backport of the current javac to run on older JDK?

nb-javac is an automated backport of the latest JDK's javac to run on JDK8+. 
No change here.

> I'm confused!  Wasn't the original proposal (and our existing usage of
> it) about using nb-javac to support later source and target while
> running on an older JDK.  This also adds supporting older source and
> target while running on a newer JDK?

By fixing the compiler in the build script (by downloading it from Maven 
central) you will be able to build such version of NetBeans on JDK33+ even if 
it drops support for any `-target` NetBeans currently needs.

If we stick using `javac` from the JDK the NetBeans build runs on, then at one 
moment you will need to download an ancient JDK to built old version of 
NetBeans as JDK33+ would be "too modern".

Let's use the JDK as a runtime only. Let's stop relying on its compiler. The 
build will be more reproducible.
-jt




-
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

NetBeans Platform Needs Portability was: nb-javac for building NetBeans itself

[Jaroslav Tulach]

Dne středa 26. října 2022 5:48:28 CET, Laszlo Kishalmi napsal(a):
> I kind of like the idea let nb-javac go, not depend more on it. 


Guys,
you are looking at the problem from an IDE perspective. However NetBeans is 
also a platform!

When designing frameworks and libraries that shall be widely adopted it is 
important to increase portability as much as possible. If an API can be used 
on different systems, different configurations, the amount of users including 
such API in their applications grows. There are hundreds of applications 
written on top of NetBeans Platform are cannot force them to run on latest JDK 
only.

Supporting the ancient JDK gives the application writers using NetBeans as a 
framework a freedom to choose their JDK. The application writers can then run 
on oldest or newest JDK. That's the kind of freedom they want.

We have all seen what problems happen when an important 3rd party library 
(Lucene) decides to drop support for older JDK. NetBeans Platform was always 
well known for carrying about its users - I certainly value everyone who 
builds its app on top of NetBeans Platform.

Many of such applications are still running on JDK8. Hence I want NetBeans 
Platform to run fine on JDK8.
 
-jt

PS: I am not a guy who wants to live in past, however! That's why I am offering 
you various ways to move forward, without hurting NetBeans Platform 
Portability.




-
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

Re: Startup Dialog and Start Page Size - 16-rc2

[Neil C Smith]

On Sun, 30 Oct 2022 at 15:40, Eric Bresie  wrote:
>
> So it seems my initial run found Java 8 available;  when I set the
> netbeans_jdkhome to java 11 it seems to work.
>
> Are there any dialog changes which may have been impacted by the JDK
> version in use?  Why does it work with JDK 11 but not JDK 8?

I commented on your issue.  But JDK 8 support was dropped in NetBeans 13!

Neil

-
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

Re: Startup Dialog and Start Page Size - 16-rc2

[Eric Bresie]

So it seems my initial run found Java 8 available;  when I set the
netbeans_jdkhome to java 11 it seems to work.

Are there any dialog changes which may have been impacted by the JDK
version in use?  Why does it work with JDK 11 but not JDK 8?

Eric Bresie
ebre...@gmail.com


On Sun, Oct 30, 2022 at 9:51 AM Eric Bresie  wrote:

> I think I raised a similar issue previously during 15 rc builds but I'm
> seeing Startup Dialog and  Start Page size differences.
>
> I've documented with screenshots here
> https://github.com/apache/netbeans/issues/4889
>
> Where in the codebase would this sort of sizing reside?
>
> Eric Bresie
> ebre...@gmail.com
>

Startup Dialog and Start Page Size - 16-rc2

[Eric Bresie]

I think I raised a similar issue previously during 15 rc builds but I'm
seeing Startup Dialog and  Start Page size differences.

I've documented with screenshots here
https://github.com/apache/netbeans/issues/4889

Where in the codebase would this sort of sizing reside?

Eric Bresie
ebre...@gmail.com

Re: UNSTABLE 16-rc2 Build

[Eric Bresie]

Looking further I did find one test failure regarding broken links on
javadocs.  Is this expected as maybe javadocs aren't there yet and are
broken links?

See
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/lastCompletedBuild/testReport/org.netbeans.nbbuild/CheckLinks/Release_preparation___prepare_release___build_for_release___testBrokenLinks/

Do the javadocs need to be generated prior to this or is this by design?

Eric



Eric Bresie
ebre...@gmail.com


On Sun, Oct 30, 2022 at 9:06 AM Eric Bresie  wrote:

> Was about to pull down and noticed the build shows as "UNSTABLE" (see the
> icon and hover over)
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/console
>
> I can see anything specific initially but was curious why this would be
> considered "UNSTABLE"?
>
> Eric Bresie
> ebre...@gmail.com
>
>
> On Thu, Oct 27, 2022 at 8:18 AM Neil C Smith 
> wrote:
>
>> The second release candidate build for Apache NetBeans 16 is available
>> (links below).
>>
>> Changes since 16-rc1 can be found at
>> https://github.com/apache/netbeans/pull/4854
>>
>> Please help with testing, particularly of changes, and file issues in
>> GitHub as necessary -
>>
>> https://github.com/apache/netbeans/issues
>>
>> If you're a committer adding an issue, or helping triage an issue
>> (please do!), add the milestone and/or priority labels as appropriate.
>> Use priority:high for should be fixed before release,
>> priority:critical for must be fixed before we can release.
>>
>> **The following rules are applied to pull requests from now until
>> release:**
>>
>> Please read the full info on how we manage pull requests to delivery
>> at least once! :-) -
>> https://lists.apache.org/thread/hyjbsz55zb9xfcnccghkrsvqsnt83nwf
>>
>> PR's intended to be included in the 16 release :
>>  - Limited to fixes (link an issue if there is one, or provide
>> justification in description)
>>  - Label with priority:high or priority:critical as appropriate.
>>  - Base on the delivery branch.
>>  - Mark with NB16 milestone.
>>  - Will be merged by the release team.
>>
>> PR's with features for a future release :
>>  - Base on the master branch.
>>  - Will be reviewed and merged in the usual way.
>>  - If possible stay away from big refactoring.
>>  - If possible do not overlap with fixes for 16 (delivery will be
>> merged to master weekly).
>>
>>
>> The NetBeans 16-rc2 artifacts, including unsigned installers, are here:
>>
>> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/
>>
>> Alternative trial link to latest release candidate:
>> https://nightlies.apache.org/netbeans/candidate/netbeans/
>>
>> Link to the binary zip:
>>
>> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/netbeans/netbeans-16-rc2-bin.zip
>> SHA512:
>> 6bb5eab966202575bb68c1e5a11b44d6eb4318a6f7d25c23c265013c66f15066dd34b783384d14ef4c737ed2e983d203c5092b09dbd573d1f51050282f0604b7
>>
>> The sources are here:
>>
>> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/netbeans/netbeans-16-rc2-source.zip
>> SHA512:
>> 4db94e8f37bf8508acf4ea934172166efc812e2c9eb840867e916690e4a647222e0e74087e7f32b31038c069df7404131adad6b61a666422260f3cd2fa180fb7
>>
>> Link to the VSCode plugin:
>>
>> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/vsix/
>>
>>
>> The PRs already integrated into NetBeans 16 are :
>> https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16
>>
>> Issues currently tagged for NetBeans 16 are :
>>
>> https://github.com/apache/netbeans/issues?q=is%3Aopen+is%3Aissue+milestone%3ANB16
>>
>> Release schedule :
>> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
>>
>>
>> Thank you for your contributions!
>>
>> Best wishes,
>>
>> Neil
>>
>> PS. Please don't respond to this email directly - start a new thread.
>> Let's keep the [NOTICE] tag for what it says. Thanks! :-)
>>
>> -
>> 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
>>
>>
>>
>>

Re: UNSTABLE 16-rc2 Build

[Neil C Smith]

On Sun, 30 Oct 2022 at 14:06, Eric Bresie  wrote:
>
> Was about to pull down and noticed the build shows as "UNSTABLE" (see the
> icon and hover over)
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/console
>
> I can see anything specific initially but was curious why this would be
> considered "UNSTABLE"?

Same for all branches.  I think it was due to some Javadoc generation
changes / tests that Eric introduced?  It doesn't affect the release
builds.

Neil

-
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

UNSTABLE 16-rc2 Build

[Eric Bresie]

Was about to pull down and noticed the build shows as "UNSTABLE" (see the
icon and hover over)
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/console

I can see anything specific initially but was curious why this would be
considered "UNSTABLE"?

Eric Bresie
ebre...@gmail.com


On Thu, Oct 27, 2022 at 8:18 AM Neil C Smith  wrote:

> The second release candidate build for Apache NetBeans 16 is available
> (links below).
>
> Changes since 16-rc1 can be found at
> https://github.com/apache/netbeans/pull/4854
>
> Please help with testing, particularly of changes, and file issues in
> GitHub as necessary -
>
> https://github.com/apache/netbeans/issues
>
> If you're a committer adding an issue, or helping triage an issue
> (please do!), add the milestone and/or priority labels as appropriate.
> Use priority:high for should be fixed before release,
> priority:critical for must be fixed before we can release.
>
> **The following rules are applied to pull requests from now until
> release:**
>
> Please read the full info on how we manage pull requests to delivery
> at least once! :-) -
> https://lists.apache.org/thread/hyjbsz55zb9xfcnccghkrsvqsnt83nwf
>
> PR's intended to be included in the 16 release :
>  - Limited to fixes (link an issue if there is one, or provide
> justification in description)
>  - Label with priority:high or priority:critical as appropriate.
>  - Base on the delivery branch.
>  - Mark with NB16 milestone.
>  - Will be merged by the release team.
>
> PR's with features for a future release :
>  - Base on the master branch.
>  - Will be reviewed and merged in the usual way.
>  - If possible stay away from big refactoring.
>  - If possible do not overlap with fixes for 16 (delivery will be
> merged to master weekly).
>
>
> The NetBeans 16-rc2 artifacts, including unsigned installers, are here:
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/
>
> Alternative trial link to latest release candidate:
> https://nightlies.apache.org/netbeans/candidate/netbeans/
>
> Link to the binary zip:
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/netbeans/netbeans-16-rc2-bin.zip
> SHA512:
> 6bb5eab966202575bb68c1e5a11b44d6eb4318a6f7d25c23c265013c66f15066dd34b783384d14ef4c737ed2e983d203c5092b09dbd573d1f51050282f0604b7
>
> The sources are here:
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/netbeans/netbeans-16-rc2-source.zip
> SHA512:
> 4db94e8f37bf8508acf4ea934172166efc812e2c9eb840867e916690e4a647222e0e74087e7f32b31038c069df7404131adad6b61a666422260f3cd2fa180fb7
>
> Link to the VSCode plugin:
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/6/artifact/dist/vsix/
>
>
> The PRs already integrated into NetBeans 16 are :
> https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16
>
> Issues currently tagged for NetBeans 16 are :
>
> https://github.com/apache/netbeans/issues?q=is%3Aopen+is%3Aissue+milestone%3ANB16
>
> Release schedule :
> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
>
>
> Thank you for your contributions!
>
> Best wishes,
>
> Neil
>
> PS. Please don't respond to this email directly - start a new thread.
> Let's keep the [NOTICE] tag for what it says. Thanks! :-)
>
> -
> 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
>
>
>
>

Re: parent.relativePath warning on Windows

[Eric Bresie]

   1. Is the sub-projects within the parent projects folder structure or
   external?
   2. In the "parent" pom, did the "modules" for the sub-projects get
   defined?
   3. In the sub-projects, did the parent pom coordinates get included?
   4. Which environment is maven running in on Windows (i.e. basic jar on
   path based or installed in a Cygwin type environment)?


Eric Bresie
ebre...@gmail.com


On Thu, Oct 27, 2022 at 6:07 PM Mark Eggers 
wrote:

> It appears that images are stripped from the list.
>
> The following should work:
>
> https://i.postimg.cc/MpmPxK2n/module-error-edited.png
>
> /mde/
>
> On 10/27/2022 3:50 PM, Mark Eggers wrote:
> > Folks,
> >
> > I am getting a warning about multi-module project structures and
> > parent.relativePath, but only on Windows (see screen shot).
> >
> > To recreate:
> >
> > 1. Create a POM project
> > 2. Right-mouse click on modules, and create a new module (Java
> application)
> > 3. Go into that new module and look at the created pom.xml
> >
> > You'll get the warning (see screen shot) that the parent.relativePath
> > points to the module, rather than to the parent.
> >
> > The project structure created by NetBeans (14,15,16-rc2) is correct, but
> > the warning IMO is not. This warning does not appear on Windows in
> > NetBeans <= 13.
> >
> > I created this screen shot in the following environment.
> >
> > Windows 10 Professional
> > Java 17.0.3+7
> > NetBeans 16-rc2 (unpacked from the zip file)
> >
> > The following items were added to netbeans.conf:
> >
> > # adding UTF-8 and fontsize at the end
> > netbeans_default_options=" . . . . -J-Dfile.encoding=UTF-8 --fontsize 14"
> >
> > # location of JDK 17 - run JDK 11 by default on this machine
> > netbeans_jdkhome="D:\Programs-x64\Java\jdk-17.0.3+7"
> >
> > I did not import any settings, and did not pre-activate any modules.
> >
> > Right now since it's a warning, I just ignore it.
> >
> > Please also note in the screen shot, pom.xml is created with Unix (LF)
> > endings instead of Windows (CRLF) endings. However, a Java Web
> > application created as a module in this project shows Windows (CRLF) for
> > pom.xml
> >
> > The warnings do not show up when following the same procedure on Ubuntu
> > 20.04.1.
> >
> > Could this be due to line ending confusion? I have the following project
> > structure:
> >
> > MyModules - pom.xml is in Unix (LF) format (POM project)
> > |
> > MyServerModule - pom.xml is in Unix (LF) format (Java application)
> > |
> > MyClientModule - pom.xml is in Windows (CRLF) format (Web
> application)
> > |
> > MyPoCModule - pom.xml is in Windows (CRLF) format (Web application)
> >
> > If someone can point me in the general direction of where to look, I'd
> > be happy to try and narrow it down further.
> >
> > . . . just my two cents
> > /mde/
> >
> >
> > -
> > 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
>
>
>
>