dgreen commented on issue #3678: URL: https://github.com/apache/netbeans/issues/3678#issuecomment-1274172514
On 20 Jul 2022, at 10:26, Michael Bien wrote: >>> well i would like to have all new-project wizards use the same >>> new-java-mainclass template. Just like the old ant project did/does. >> >> +1 to that. Is that reasonable to target during NB15 do you think? > > probably not. I am not going to do that anyway since I don't know the > requirements. I pinged everyone in march > https://github.com/apache/netbeans/issues/3678#issuecomment-1080221805 > and got no reply. Sorry. Did not realize I was being included specifically as opposed to just a mailing list message. File URLs: * Click nbfs://nbhost/SystemFileSystem/Templates/Licenses/license-default.txt to change this license * Click nbfs://nbhost/SystemFileSystem/Templates/Project/Maven2JavaApp/src/main/java/uab.edu.ee333.mavenproject1/Mavenproject1.java ${packagePath}/${mainClassName}.java to edit this template What I desire is, in steady state, to have customizable templates with my information being used instead of one or more URLs. I understand new templates may be needed for new situations. In the cited case, there is not a deducible template to create as the second line appears broken — not completely interpolated and clicking (or CMD+clicking on Mac) doesn’t cause any visible action. Tools > Templates does not seem to include any options that suggest the template to create/modify. I generally write small programs so I use the templates across all projects not new templates for each project. My understanding is that the existing templates are across all projects. If a template can be established for this generated main from clicking the second line of the inserted URLs, pre-populated with the default content including the URL, and after editing the edited template is used for future use both inside the current and future projects, I think this would be a win. Certainly one new-java-mainclass seems like a good way to go for command line programs and I was thinking that way went I made the initial post but Javafx (and others) has their own structure (imports, a shell main calling start and a shell launch) and that is helpful. So reuse when appropriate would be great but it most important to have a path to having a template. >>> I also learned that the VSCode nb plugin does not have a template >>> manager window, so it heavily relies on those links. >> >> I'm curious how you edit those the second time! wink > > customer support probably ;) I have not used this before. Firing it up with the extension “Language Server for Java by Apache NetBeans v14.0.301” on my Mac, and then running the only wizard there for a maven Java project with the same template and two URLs that can be run within VSCode. The same URLs are present, and the first one works option-clicking on it while the second one is unresponsive. Dave -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
