Here's a newer build: http://download.jboss.org/jbosstools/oxygen/stable/ updates/core/freemarker/ > Is that oxygen snapshot likely to be actually gone any time soon? It's a snapshot, it could be overwritten at any time. We make no guarantees that snapshots will persist for more than a day. > Also, will there be chance to have PR-s merged and trigger a build, or that's barely possible at this point? Anything is possible, but the whole point of deprecating, then removing, was that we don't plan to run any more builds. That's now your job. :) Cheers, Nick On Fri, Mar 9, 2018 at 2:19 AM, Daniel Dekany <ddekany(a)freemail.hu&gt; wrote: > Friday, March 9, 2018, 3:28:45 AM, Nick Boldt wrote: > > > You should point them here: > > > > http://download.jboss.org/jbosstools/neon/stable/updates/ > core/freemarker/ > > But this is a quite outdated version. > > > No guarantees about snapshot sites, but stable ones are forever. > > Is that oxygen snapshot likely to be actually gone any time soon? > > Also, will there be chance to have PR-s merged and trigger a build, or > that's barely possible at this point? > > -- > Thanks, > Daniel Dekany >

Daniel, Any news from the Apache Foundation about their willingness to take the Eclipse Freemaker codebase from org.jboss and port it to org.apache?

If not, here's another option you might like to explore. Angero Zerr (added to cc:) has started a prototype Freemaker Language Server: https://github.com/angelozerr/freemarker-languageserver He also has a feature/plugin for Eclipse which uses the language server to provide Freemaker support in Eclipse: https://github.com/angelozerr/lsp4e-freemarker As the future of Eclipse tooling seems to be around language servers, rather than language-specific plugins, this might be a better, more supported approach to consider. Maybe he'd want to contribute this work to the ASF?

Nick On Fri, Mar 9, 2018 at 8:22 AM, Nick Boldt <nboldt(a)redhat.com&gt; wrote: Here's a newer build: http://download.jboss.org/jbosstools/oxygen/stable/updates/core/freemarker/ > Is that oxygen snapshot likely to be actually gone any time soon? It's a snapshot, it could be overwritten at any time. We make no guarantees that snapshots will persist for more than a day. > Also, will there be chance to have PR-s merged and trigger a build, or that's barely possible at this point? Anything is possible, but the whole point of deprecating, then removing, was that we don't plan to run any more builds. That's now your job. Cheers, Nick On Fri, Mar 9, 2018 at 2:19 AM, Daniel Dekany <ddekany(a)freemail.hu&gt; wrote: Friday, March 9, 2018, 3:28:45 AM, Nick Boldt wrote: > You should point them here: > > http://download.jboss.org/jbosstools/neon/stable/updates/core/freemarker/ But this is a quite outdated version. > No guarantees about snapshot sites, but stable ones are forever. Is that oxygen snapshot likely to be actually gone any time soon? Also, will there be chance to have PR-s merged and trigger a build, or that's barely possible at this point? -- Thanks, Daniel Dekany

Hi, On Tue, Mar 20, 2018 at 7:57 AM, Daniel Dekany <ddekany(a)freemail.hu&gt; wrote: > It can be the future, but it doesn't seem to be a short term solution, > It's nowadays the solution with the better short term ROI. There are big chances that with the same amount of effort on FreeMarker LS and Eclipse IDE integration of the LS, you get better results faster than with trying to migrate code from JBoss Tools to Apache, from legal, releng and technical POV. > especially as my quick impression was that LSP4E is immature LSP4E is already used in production-grade Eclipse based tools, such as Red Hat Developers Studio or Spring Tools Suite and is the root for Eclipse aCute (C#) and Eclipse Corrosion (Rust). If you have any bug with it, feel free to report them to https://bugs.eclipse.org/bugs/ enter_bug.cgi?product=lsp4e so they can be considered and hopefully fixed. If you used BlueSky, you probably got the 0.2.0 release of LSP4E installed. LSP4E is about to ship 0.6.0 so that can explain why you found issues. Please open bugs to BlueSky about the issues so some cycles may be spent to upgrade to newer LSP4E and deliver more value. > and > considering that commit activity seems to be low (same worries with > BlueSky, which brings the most extra value to us). The commit activity of LSP4E is low because the project is actually mature enough for most of its adopters and the project doesn't require continuous daily work to work well. If you're used to GitHub pull request, then the Gerrit process used to develop LSP4E indeed produces less commits but with much higher quality (1 commit with Gerrit ~= 5 commits with GitHub PR, because the typical "fix comment" or "applied suggestion" commits we see with GitHub PR are on the Gerrit review and not in the history)... The commit activity for BlueSky is low because at the moment, the project is not "business-critical" to anyone and not so many users do report bugs, so it's hard to figure out what can be done. Please report bugs if you have any. > I'm also not yet seeing if there will be enough momentum behind LSP4E. There is already momentum behind LSP4E. You should come to EclipseCons or similar tools oriented conferences to see how LSP is perceived by all major players in the Tools domain as *the* solution to many problems, and how LSP4E client is perceived as one of the best client for LSP, after VSCode. To be clear, unless you are very experienced Eclipse developers, maintaining Freemarker plugin as it will be a hard task, that has very big chances of becoming too hard at some point to remain sustainable. By moving it to Apache, you're not giving it a second life, you're mostly trying to keep it alive a bit longer with a lot of efforts and less expertise as its maitenance used to require. Moving to LSP, you're bringing tools for FreeMarker to a new life with less efforts (because most of the code is plain Java and not Eclipse-specific) and you open the door for other tools such as Eclipse Che or VSCode to support Freemarker properly. The LSP and LSP4E are really sustainable and will remain maintained by experts of this domain, for free (from your adopter perspective). This is the only sustainable path, and this is from now on, not in the future. Cheers

Tuesday, March 20, 2018, 8:24:14 AM, Mickael Istria wrote: > Hi, > > On Tue, Mar 20, 2018 at 7:57 AM, Daniel Dekany <ddekany(a)freemail.hu&gt; > wrote: > It can be the future, but it doesn't seem to be a short term > solution, > > It's nowadays the solution with the better short term ROI. There are > big chances that with the same amount of effort on FreeMarker LS and > Eclipse IDE integration of the LS, you get better results faster > than with trying to migrate code from JBoss Tools to Apache, from > legal, releng and technical POV. > >> especially as my quick impression was that LSP4E is immature > > LSP4E is already used in production-grade Eclipse based tools, such > as Red Hat Developers Studio or Spring Tools Suite and is the root > for Eclipse aCute (C#) and Eclipse Corrosion (Rust). If you have any > bug with it, feel free to report them to > https://bugs.eclipse.org/bugs/enter_bug.cgi?product=lsp4e so they > can be considered and hopefully fixed. > If you used BlueSky, you probably got the 0.2.0 release of LSP4E > installed. LSP4E is about to ship 0.6.0 so that can explain why you > found issues. [snip] The FreeMarker plugin uses 0.6.0.201803121253. Otherwise, as far as maturity goes, I was just naively assuming that it's immature officially as well, but didn't meant to interfere with anyone. We will see how the new FreeMarker plugin does anyway. Also, I plan to debug into why is it behaving as it does, then I will know more. As far as the old plugin is concerned, for a while we can get away with a personal Github fork and a repo on Bintray. So maybe we will give the new plugin a few months before deciding. -- Thanks, Daniel Dekany _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On Tue, Mar 20, 2018 at 4:26 PM, Max Rydahl Andersen <manderse(a)redhat.com&gt; wrote: > Michael - have LSP4 project looked into how to add outline support ? LSP4E has had outline support for since November 2016, relying on the document symbol ranges.

for what it is worth I think freemarker is a perfect candidate for LSP

On Tue, Mar 20, 2018 at 4:33 PM, Max Rydahl Andersen <manderse(a)redhat.com&gt; wrote: > nice. does that approach end up being sensible for users or will it add a > lot of details to the outline ? > It would depend on the LS grain for "symbols". My experience with it was positive and I never suffered from a too full outline as far as I remember. Feel free to give it a try with BlueSky for instance and to report your impressions on related bug trackers. -- Mickael Istria Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> developer, at Red Hat Developers <https://developers.redhat.com/> community Elected Committer Representative at the Eclipse Foundation <https://www.eclipse.org/org/> board of directors