Dne úterý 1. dubna 2025 15:48:55 CEST, Jan Lahoda napsal(a): > As long as NetBeans itself is developed compatibly, then even if the > extension has a slightly newer or older version of the embedded NetBeans > compared to the current released NetBeans shouldn't be a big deal, right? > Your module would simply depend on the older version of the NetBeans > modules, and things should still work? > > I am not quite sure if there's any real difference to how things work now > (given the VSNetBeans releases are faster than the being done in between > main releases as well).
There are various interim releases of VSCode NetBeans extension in the current scheme - like 13.9.999, etc. But every three months there is a release (like 14.0.0) that "synchronizes" with the main repository. Thus we could always hope that once a quarter there is going to be a release of VSCode NetBeans compatible with NetBeans (Swing Edition). I don't see any such promise in the new proposal. -jt > On Sat, Mar 29, 2025 at 2:57 PM Jaroslav Tulach <jaroslav.tul...@gmail.com> > > wrote: > > When I "put my Enso hat on", I have to ask: > > - Will Apache NetBeans VSCode still be compatible with NetBeans IDE? > > - How that's going to be ensured? > > > > A little background: > > - Enso is building its tooling on the NetBeans project > > > > - we build both: > > - VSCode extension: > > https://github.com/enso-org/enso/blob/develop/tools/ > > enso4igv/README.md > > <https://github.com/enso-org/enso/blob/develop/tools/enso4igv/README.md> > > > > - NetBeans module: > > https://github.com/enso-org/enso/blob/develop/tools/ > > enso4igv/IGV.md > > <https://github.com/enso-org/enso/blob/develop/tools/enso4igv/IGV.md> > > - there is a single Maven project in our Enso repository > > - it builds both VSCode extension & NetBeans module > > - single codebase for both systems > > > > - a great value that simplifies our life > > > > - we use Maven dependencies - e.g. the officially released Maven artifacts > > > > How's this "two extensions/modules from a single code" is supposed to work > > when you "include NetBeans main repository" as a (Git) sub-module? How > > much > > different the sub-module is going to be? For the Enso use-case we need as > > little changes in the sub-module as possible. Is that going to be > > guaranteed > > somehow? > > > > Jaroslav Tulach > > Enso compiler & tooling team > > > > Dne středa 26. března 2025 16:00:02 CET, Martin Balin napsal(a): > > > Hello, > > > There was a discussion about how to do releases of VSNetBeans - NetBeans > > > > LSP > > > > > server for VS Code on dev@ and then also on Slack. The reason was > > > overlapping releases with main NetBeans IDE causing some friction etc. > > > > > > As the result of these preliminary talks I’ve wrote a proposal how to > > > decouple VSNetBeans from NetBeans repo and how to release it > > > > independently > > > > > from main IDE release. All still under ASF umbrella. Proposal for > > > discussion > > > > https://cwiki.apache.org/confluence/display/NETBEANS/VSNetBeans+Repository > > +a> > > > nd+Updated+Releases > > > > > > Thank you, > > > Martin > > > > --------------------------------------------------------------------- > > 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
