Re: [DISCUSS] tweak some defaults for NB17?
On 11/2/22 11:16 AM, Michael Bien wrote: I have a list of options I usually change when setting up NetBeans. One more I would add: change the default keyboard shortcuts for shifting editor tabs from their current values of: Shift Window Tab Left - Ctrl+Alt+Shift+LEFT Shift Window Tab Right - Ctrl+Alt+Shift+RIGHT to the Web browser (Chromium, Firefox) defaults of: Shift Window Tab Left - Ctrl+Shift+PAGE UP Shift Window Tab Right - Ctrl+Shift+PAGE DOWN I use those shortcuts all the time, as I find the NetBeans drag-and-drop to be a little squirrelly. The current defaults do nothing on Ubuntu. I think they would normally move the current application window to the workspace to the right, but on Ubuntu 20.04 LTS the workspaces are vertical, so nothing happens. By the way, I remember being able to add those shortcuts as alternatives, and the old values would remain. Now when I add the new ones as alternatives, the old ones are gone. 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] tweak some defaults for NB17?
On Thu, 3 Nov 2022 at 16:11, Michael Bien wrote: > > On 03.11.22 10:11, Neil C Smith wrote: > > +1 to most of the changes, but ... > > > > On Thu, 3 Nov 2022 at 01:53, John Neffenger wrote: > >>> small toolbar icons: > >> Those are very tiny on my 109-dpi (non-HiDPI) 27-inch monitor. > > Agreed! -1 to changing the icon default size. Have to say I keep > > them larger on all displays, from 27-inch main display, down to old HD > > laptop. Find them unusable at smaller size. > > lets disqualify that idea early :) Although I have to wonder.. wouldn't > those small toolbar icons be the exact same size as all other icons too? > > If they are hard to see, how do you distinguish between file type icons? Seeing them isn't the problem (yet). Accurately clicking the right thing with my clumsy old hands might be! :-) Mind you, I rarely use the toolbar anyway, so I can live with any change. But for people starting out who are more likely to, I do think the current size works. > any news from the svg icon front btw? Good question. > > Actually, I don't entirely think that, although I think there's some > > improvement to make in the UI for them judging from recent comments. > > A lesson in there on changing defaults ... > > yeah, there is probably more granularity needed than just on and off. > Esp once more kinds of inline-hints appear. Well, one lesson is making clear where the settings are when we change defaults, so that those who preferred the way things were know how to revert. Best wishes, 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: [DISCUSS] tweak some defaults for NB17?
On 03.11.22 10:11, Neil C Smith wrote: +1 to most of the changes, but ... On Thu, 3 Nov 2022 at 01:53, John Neffenger wrote: small toolbar icons: Those are very tiny on my 109-dpi (non-HiDPI) 27-inch monitor. Agreed! -1 to changing the icon default size. Have to say I keep them larger on all displays, from 27-inch main display, down to old HD laptop. Find them unusable at smaller size. lets disqualify that idea early :) Although I have to wonder.. wouldn't those small toolbar icons be the exact same size as all other icons too? If they are hard to see, how do you distinguish between file type icons? any news from the svg icon front btw? view -> show versioning label: That adds clutter, in my opinion, but I do most Git operations in an external terminal window. I find the labels useful even in that case. Except occasionally when things don't align with CLI git! I used to use them as last check to see if i was about to push the correct branch. Although I am starting to use the long form now: git push repo_url from_branch:to_branch so that nothing is implied anymore - everything is in that line. While we're at it, let's add '--strict-checksums' too! That one should have been the Maven default years ago, but Maven isn't enabling it until version 4.0: Switch the default checksum policy from "warn" to "fail" https://issues.apache.org/jira/browse/MNG-5728 Possibly a good idea. There's a wider discussion about default Maven options, pom, project template, etc. there. I think we should follow best practices from upstream Maven, even if that means at times no longer following the defaults. In all this tweaking, possibly switching inline hints back off?! :-) yes please :) Although I intentionally didn't mention this one, since this is going to be controversial. Actually, I don't entirely think that, although I think there's some improvement to make in the UI for them judging from recent comments. A lesson in there on changing defaults ... yeah, there is probably more granularity needed than just on and off. Esp once more kinds of inline-hints appear. -mbien Best wishes, 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: Issue reporting maybe confusing
Got it. Thx On Thu, Nov 3, 2022 at 2:23 PM Neil C Smith wrote: > On Thu, 3 Nov 2022 at 14:13, Jean-Marc Borer wrote: > > > > Hi folks, > > > > People get a bit confused when reporting issue AFAIU, all issue shall be > > reported here https://github.com/apache/netbeans/issues > > > > However the Jira site https://issues.apache.org/jira/projects/NETBEANS/ > > still exists. > > > > Having to places to report issues is confusing. People used to Apache > > projects go naturally to Apache Jira. > > > > If the latter should ne no longer be used, couldn't it be stated properly > > or event better tansfer all issues if not already done and block any new > > inputs? > > > > So what is the status today? > > There are not two places for users to report issues. Users cannot > open Jira tickets. All user reported issues should be via GitHub. > See https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-6470 > > Jira issues can still be created by NetBeans committers, as some > expressed an interest in still using it for project management tasks. > > Users can still comment on old issues. > > We're not transferring any issues automatically. Anything still valid > should be opened on GitHub. > > I have a feeling we'll see more and more Apache projects using GitHub > issues due to current concerns around Apache Jira infrastructure (spam > issues, etc.). > > Best wishes, > > 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: Issue reporting maybe confusing
On Thu, 3 Nov 2022 at 14:13, Jean-Marc Borer wrote: > > Hi folks, > > People get a bit confused when reporting issue AFAIU, all issue shall be > reported here https://github.com/apache/netbeans/issues > > However the Jira site https://issues.apache.org/jira/projects/NETBEANS/ > still exists. > > Having to places to report issues is confusing. People used to Apache > projects go naturally to Apache Jira. > > If the latter should ne no longer be used, couldn't it be stated properly > or event better tansfer all issues if not already done and block any new > inputs? > > So what is the status today? There are not two places for users to report issues. Users cannot open Jira tickets. All user reported issues should be via GitHub. See https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-6470 Jira issues can still be created by NetBeans committers, as some expressed an interest in still using it for project management tasks. Users can still comment on old issues. We're not transferring any issues automatically. Anything still valid should be opened on GitHub. I have a feeling we'll see more and more Apache projects using GitHub issues due to current concerns around Apache Jira infrastructure (spam issues, etc.). Best wishes, 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
Issue reporting maybe confusing
Hi folks, People get a bit confused when reporting issue AFAIU, all issue shall be reported here https://github.com/apache/netbeans/issues However the Jira site https://issues.apache.org/jira/projects/NETBEANS/ still exists. Having to places to report issues is confusing. People used to Apache projects go naturally to Apache Jira. If the latter should ne no longer be used, couldn't it be stated properly or event better tansfer all issues if not already done and block any new inputs? So what is the status today? best rgrads
Re: parent.relativePath warning on Windows
Sorry. Now we to report issues here:
https://github.com/apache/netbeans/issues
On Thu, Nov 3, 2022 at 12:42 PM Jean-Marc Borer wrote:
> Hi There,
>
> Spotted the same issue with NB 15. Glad to see it fixed.
>
> @herkrath please file the bug first in
> https://issues.apache.org/jira/projects/NETBEANS/ (simply copy the steps
> above) before creating the PR. It will help to track improvements and
> release notes.
>
> Cheers
>
> On Thu, Nov 3, 2022 at 9:35 AM Mark Herkrath
> wrote:
>
>> Hi all,
>>
>> I ran into the same issue. At least for me, it is happening every time a
>> parent pom is being used. That is for stand-alone/root poms referring to
>> parent poms not being part of the project's file structure, as well as for
>> multi-module poms where the parent pom is usually one level up in the file
>> structure. For stand-alone/root poms, it helps to define
>> though, which is anyway recommended.
>>
>> So I checked the source code, and found this in
>> org.netbeans.modules.maven.hints.pom.PomModelUtils:
>>
>> public ModelSource2 getRelatedSource(String relative) {
>> return new M2S(new File(pomFile, relative), null);
>> }
>>
>> This is clearly incorrect as pomFile is a file, not a directory. It has to
>> be instead:
>> return new M2S(new File(pomFile.getParentFile(), relative), null);
>>
>> I have already tested and the issue is resolved thereafter.
>> Actual incorrect project file structures are correctly reported still. I
>> don't know when getRelatedSource(...) is being called elsewise. But like
>> it
>> is now, no related source will be resolved correctly. So probably there
>> are
>> other issues caused by it as well.
>>
>> Now, I am not very keen to create a merge request. It is quite
>> time-consuming and not getting the credits is ok. So if possible, could a
>> NetBeans maintainer push this simple change, as it is just obvious? If
>> that
>> is not feasible, alright, I will create the corresponding merge request.
>>
>> Thanks,
>> Mark
>>
>> On Sun, Oct 30, 2022 at 7:56 PM Mark Eggers > >
>> wrote:
>>
>> > 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
[NOTICE] Apache NetBeans 16 release candidate 3 available for testing
The third release candidate build for Apache NetBeans 16 is available (links below). This will be our final release candidate unless high/critical priority issues or pull requests are flagged. Please kick the tyres well over the coming week or so! This includes testing building from source and other release checks. Changes since 16-rc2 can be found at https://github.com/apache/netbeans/pull/4870 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-rc3 artifacts, including unsigned installers, are here: https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/8/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/8/artifact/dist/netbeans/netbeans-16-rc3-bin.zip SHA512: a41460a9afed9047f9272dc9c03628add860fce5f9c2912a4f570b4c49e3bba8b35afb6d5d52495ba39b8ddcb3d8ee3a7b3e6b00eb525ab9a6a07e77965509ad The sources are here: https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/8/artifact/dist/netbeans/netbeans-16-rc3-source.zip SHA512: e3ebce04dc42cbc342fe393534124c665200034e30c32a21348d466907bc766860a8fc5690bfa9513061e2321fd9d5b8117f2eabc3fb157b015da4f5c2e31fa6 Link to the VSCode plugin: https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/8/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: [DISCUSS] Drop separate platform source and binary zip from release artefacts?
I do as well use the platform zip for the same reasons as Joerg (even if we use Maven most of the time other envrionments), but I can certainly go with the whole bundle, but please it needs to be properly documented. Not sure I will be able to remember in a few month the exact command-line you suggest above. Cheers, JM On Thu, Nov 3, 2022 at 11:23 AM Joerg Michelberger wrote: > Hi Neil, > > Thanks for that build info creating the platform source zip from IDE source > zip. > As it does the job, we go that way. > > Thanks. > > Regards, > Joerg > > Neil C Smith schrieb am Do., 3. Nov. 2022, 10:30: > > > On Thu, 3 Nov 2022 at 09:12, Joerg Michelberger > > wrote: > > > We use the platform zip as a starting point for our platform based > > > applications. > > > We are building by source in a separate network, not connected to the > > > internet. > > > It is convenient have the platform as separate clear isolated zip, so > we > > > have not extract it from the IDE zip. > > > > > > It would be nice to keep the separated platform zip form. > > > > Extraction is quite easy. If you download the source zip of the IDE and > > run .. > > > > ant build-source-config -Dcluster.config=platform > > > > .. you'll end up with a zip like we've been distributing. It's a > > quick process, unlike all required to release it. Would that extra > > step cause problems for you? > > > > Best wishes, > > > > 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: parent.relativePath warning on Windows
Hi There,
Spotted the same issue with NB 15. Glad to see it fixed.
@herkrath please file the bug first in
https://issues.apache.org/jira/projects/NETBEANS/ (simply copy the steps
above) before creating the PR. It will help to track improvements and
release notes.
Cheers
On Thu, Nov 3, 2022 at 9:35 AM Mark Herkrath
wrote:
> Hi all,
>
> I ran into the same issue. At least for me, it is happening every time a
> parent pom is being used. That is for stand-alone/root poms referring to
> parent poms not being part of the project's file structure, as well as for
> multi-module poms where the parent pom is usually one level up in the file
> structure. For stand-alone/root poms, it helps to define
> though, which is anyway recommended.
>
> So I checked the source code, and found this in
> org.netbeans.modules.maven.hints.pom.PomModelUtils:
>
> public ModelSource2 getRelatedSource(String relative) {
> return new M2S(new File(pomFile, relative), null);
> }
>
> This is clearly incorrect as pomFile is a file, not a directory. It has to
> be instead:
> return new M2S(new File(pomFile.getParentFile(), relative), null);
>
> I have already tested and the issue is resolved thereafter.
> Actual incorrect project file structures are correctly reported still. I
> don't know when getRelatedSource(...) is being called elsewise. But like it
> is now, no related source will be resolved correctly. So probably there are
> other issues caused by it as well.
>
> Now, I am not very keen to create a merge request. It is quite
> time-consuming and not getting the credits is ok. So if possible, could a
> NetBeans maintainer push this simple change, as it is just obvious? If that
> is not feasible, alright, I will create the corresponding merge request.
>
> Thanks,
> Mark
>
> On Sun, Oct 30, 2022 at 7:56 PM Mark Eggers >
> wrote:
>
> > 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
> > >>>
Re: [DISCUSS] Drop separate platform source and binary zip from release artefacts?
Hi Neil, Thanks for that build info creating the platform source zip from IDE source zip. As it does the job, we go that way. Thanks. Regards, Joerg Neil C Smith schrieb am Do., 3. Nov. 2022, 10:30: > On Thu, 3 Nov 2022 at 09:12, Joerg Michelberger > wrote: > > We use the platform zip as a starting point for our platform based > > applications. > > We are building by source in a separate network, not connected to the > > internet. > > It is convenient have the platform as separate clear isolated zip, so we > > have not extract it from the IDE zip. > > > > It would be nice to keep the separated platform zip form. > > Extraction is quite easy. If you download the source zip of the IDE and > run .. > > ant build-source-config -Dcluster.config=platform > > .. you'll end up with a zip like we've been distributing. It's a > quick process, unlike all required to release it. Would that extra > step cause problems for you? > > Best wishes, > > 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 > > > >
Old problem with non-ASCII characters in path
Hello! NB15. Its the old problem as i remember. How to fix this? [image: image.png]
Re: parent.relativePath warning on Windows
Hi all,
I ran into the same issue. At least for me, it is happening every time a
parent pom is being used. That is for stand-alone/root poms referring to
parent poms not being part of the project's file structure, as well as for
multi-module poms where the parent pom is usually one level up in the file
structure. For stand-alone/root poms, it helps to define
though, which is anyway recommended.
So I checked the source code, and found this in
org.netbeans.modules.maven.hints.pom.PomModelUtils:
public ModelSource2 getRelatedSource(String relative) {
return new M2S(new File(pomFile, relative), null);
}
This is clearly incorrect as pomFile is a file, not a directory. It has to
be instead:
return new M2S(new File(pomFile.getParentFile(), relative), null);
I have already tested and the issue is resolved thereafter.
Actual incorrect project file structures are correctly reported still. I
don't know when getRelatedSource(...) is being called elsewise. But like it
is now, no related source will be resolved correctly. So probably there are
other issues caused by it as well.
Now, I am not very keen to create a merge request. It is quite
time-consuming and not getting the credits is ok. So if possible, could a
NetBeans maintainer push this simple change, as it is just obvious? If that
is not feasible, alright, I will create the corresponding merge request.
Thanks,
Mark
On Sun, Oct 30, 2022 at 7:56 PM Mark Eggers
wrote:
> 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
>
Re: [DISCUSS] Drop separate platform source and binary zip from release artefacts?
On Thu, 3 Nov 2022 at 09:12, Joerg Michelberger wrote: > We use the platform zip as a starting point for our platform based > applications. > We are building by source in a separate network, not connected to the > internet. > It is convenient have the platform as separate clear isolated zip, so we > have not extract it from the IDE zip. > > It would be nice to keep the separated platform zip form. Extraction is quite easy. If you download the source zip of the IDE and run .. ant build-source-config -Dcluster.config=platform .. you'll end up with a zip like we've been distributing. It's a quick process, unlike all required to release it. Would that extra step cause problems for you? Best wishes, 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: [DISCUSS] Drop separate platform source and binary zip from release artefacts?
Hi Neil, sorry for late jump in the conversation. We use the platform zip as a starting point for our platform based applications. We are building by source in a separate network, not connected to the internet. It is convenient have the platform as separate clear isolated zip, so we have not extract it from the IDE zip. It would be nice to keep the separated platform zip form. Regards, Joerg Jaroslav Tulach schrieb am So., 30. Okt. 2022, 20:40: > 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: [DISCUSS] tweak some defaults for NB17?
+1 to most of the changes, but ... On Thu, 3 Nov 2022 at 01:53, John Neffenger wrote: > > small toolbar icons: > > Those are very tiny on my 109-dpi (non-HiDPI) 27-inch monitor. Agreed! -1 to changing the icon default size. Have to say I keep them larger on all displays, from 27-inch main display, down to old HD laptop. Find them unusable at smaller size. > > view -> show versioning label: > > That adds clutter, in my opinion, but I do most Git operations in an > external terminal window. I find the labels useful even in that case. Except occasionally when things don't align with CLI git! > While we're at it, let's add '--strict-checksums' too! That one should > have been the Maven default years ago, but Maven isn't enabling it until > version 4.0: > >Switch the default checksum policy from "warn" to "fail" >https://issues.apache.org/jira/browse/MNG-5728 Possibly a good idea. There's a wider discussion about default Maven options, pom, project template, etc. there. I think we should follow best practices from upstream Maven, even if that means at times no longer following the defaults. In all this tweaking, possibly switching inline hints back off?! :-) Actually, I don't entirely think that, although I think there's some improvement to make in the UI for them judging from recent comments. A lesson in there on changing defaults ... Best wishes, 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
