Re: plugins.netbeans.org / netbeans.org
Suggestion: - no need for plugin registry and hashes in plugin registry - use the maven/gradle resolver lib for plugin dependencies : reuse repo libs from mvn, gradle or Arquillian - publish the plugin in standard mvn central - if there is need of extra "plugin specific" metadata : store in a META file (like WAR's have web.xml) : maybe go with JSON not XML based on current trends - maybe a file extension of netbeans.plugin.jar ?? On 4/7/19 3:35 PM, Neil C Smith wrote: On Sat, 6 Apr 2019, 01:53 Tushar Joshi, wrote: This means maintaining the list of plugins as files in a github repository. This repository will be considered as the plugin registry. So the plugin developers will just have to submit a PR to get their plugins included or updated. We can still create the moderation process to verify and validate the plugins before we approve the PR for addition or update of the plugins. +1 from me. I've suggested this a few times in conversations on web infrastructure in the past. Seems the ideal way to do this IMO, but... The plugins can be uploaded to the maven registry just as mentioned in the email thread and only the metadata, and registration, SHA hashes can be placed in the plugin registry github repository. IIRC when I looked into it the IDE doesn't check the plugin file against a hash currently? That would need to be done for this approach. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Release Apache NetBeans parent pom 1.0
Maybe consider A="netbeans-parent" In the absence of OSGI, "parent" is common and ambiguous across multiple projects. Example: I have been on projects that ended up with transitive dependencies of multiple "utility.jar" from different groups. While less likely with a parent, IMHO still a collision risk and [projectName]-parent does give context in debugging. On 2/18/19 2:04 PM, Jaroslav Tulach wrote: Dne pondělí 18. února 2019 16:55:52 CET, Ate Douma napsal(a): This *new* maven artifact is using Maven groupId: org.netbeans.maven. Which IMO can and should at least use the org.apache.netbeans prefix. There is no existing usage, yet, so *not* using the org.apache. prefix as expected seems weird and wrong to me. As a strong proponent of compatibility, I am ready to defend existing co- ordinates for existing artifacts. However in this case I agree with Ate. Let's use org.apache.netbeans:parent:1 My voice isn't a vote. I just want to support Ate's argumentation in this case: When in ASF behave like Apache! -jt - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Netbeans future platform and IDE packaging and design - brainstorming
May I also suggest the following pattern for future release consideration? Maven'like / semver.org : using X.Y.Z * The netbeans "product" would be X.Y with any value for Z being 100% compatible with X.Y * Thus an executable netbeans jar of netbeans-x.y.z.jar and maybe netbeans-x.y.jar which wraps and executes the newest x.y.z.jar available (maybe downloading it from the netbeans site for auto-upgrade * the executable JAR would be the slim netbeans application framework with the following unremovable plugins: - plugin manager - plugin for 'distributions' like : ee : base : php : the different setups as the old netbeans.org * Each distribution specifies a set of plugins - each plugin has an x.y.z If needed, netbeans...jar and each plugin...jar may be basically a BOM (bill of materials) that contains required JAR files (think of a FAT JAR, shade, or SpringBoot executable JAR) Thank you, Frederick Bloom hanasaki - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: JUnit 5
Happy to. Also put together a quickie helloworld. https://github.com/hanasaki/helloworld-gradle On 8/8/18 4:06 AM, Geertjan Wielenga wrote: Hi all, Now that the dust around the first Apache NetBeans release is settling and we're converging around a tentative release cycle, maybe we could look at one of the big missing features, i.e., JUnit 5: https://issues.apache.org/jira/browse/NETBEANS-6 John McDonnell, as mentioned in the issue above, has put this together: https://cwiki.apache.org/confluence/display/NETBEANS/Feature+Request+-+JUnit+5+Outline Are there any takers for working on this? A significant starting point would be to see how support for earlier versions of JUnit are implemented in https://github.com/apache/incubator-netbeans and then to start doing something as similar and as integrated into that way of doing things as possible. Especially for those of us who have years of NetBeans plugin development experience, this seems like a reasonable challenge for which you'll get maximum gratitude from the community. :-) Gj - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
status of plugin migration for netbeans 9 @ apache?
Is there a status page for migration of plugins from netbeans.org to netbeans@apache? Specifically looking for the gradle plugin. Thank you so much! - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
