Hello Andrew,
Thank you for the directions. I looked up issue
#880; "Split toolbox into a separate repo," and I would like address it having had spent some time on the build. I shall follow up with some notes/questions in the issue's comments section and see if I can find a starting point.
If I am able to clear the clutter around the Toolbox IDE Eclipse-build, I could spend some time with the Eclipse-based IDE's source, assuming that there is interest in keeping the standalone IDE in working condition, in addition to the vscode extension.
I want to add that learning TLA+ and contributing to open source software were my motivation behind touching the "tlaplus" repository. May I discuss a proposal submission for the grant program?
I have very little knowledge of TLA+, or its usage, so I was hoping to take up some engineering tasks about improvements to the development environment/workflow, like issues
#306,
#1165, and
#880, initially, and then, over time, read the tools' source and make some contributions there.
-
Sauparna
On Tuesday, May 13, 2025 at 10:54:53 AM UTC-4 Andrew Helwer wrote:
With regard to your second question about how to set up development for the toolbox IDE in a minimal way, I share your desire to do that. However, the Eclipse Oomph process is currently the only documented method. So, you're working on an unknown - if you figure out how to do it, please document your findings for others!
Not much work is done on the Eclipse-based toolbox IDE these days, and it will likely be
split into a separate repo from the command-line tools. Much more development effort is going into
the VS Code Extension. However, if you are interested in contributing development work to the Eclipse-based IDE that would certainly be appreciated, it could use some love!
If you only want to develop the TLA+ Java command-line tools instead of the toolbox, that is easily done by opening
this directory as an Eclipse project.
Andrew Helwer
On Tuesday, May 13, 2025 at 10:46:29 AM UTC-4 Andrew Helwer wrote:
Hi Sauparna,
Andrew Helwer
On Tuesday, May 13, 2025 at 9:51:15 AM UTC-4 Sauparna Palchowdhury wrote:
"mvn verify" fails.
Setup
OS: macOS, aarch64.
I installed the Adoptium JDK, and I am using Ant and Maven from the command-line. The JAVA_HOME variable is set in .zshenv, the latest And and Maven binaries were downloaded, contents of Ant's bin and lib directories were copied to /usr/local/, and, Maven's bin was added to the PATH environment variable in .zshenv.
JDK; "java --version'' prints
openjdk 21.0.7 2025-04-15 LTS
OpenJDK Runtime Environment Temurin-21.0.7+6 (build 21.0.7+6-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.7+6 (build 21.0.7+6-LTS, mixed mode, sharing)
Ant; 1.10.15
Maven; "mvn -v'' prints
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /Users/rup/Documents/work/lamport/apache-maven-3.9.9
Java version: 11.0.27, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.4.1", arch: "aarch64", family: "mac"
Eclipse;
Eclipse IDE for RCP and RAP Developers (includes Incubating components)
Version: 2024-06 (4.32.0)
Build id: 20240606-1231
The "tlatools'' build runs smoothly from the command line, as described in documentation (DEVELOPING.md).
The Toolbox IDE build runs to completion from command line (I set JAVA_HOME temporarily to point to a JDK version 11), but "mvn verify'' fails with numerous errors, with messages complaining about missing org.eclipse.* libraries. The following pattern of error messages repeat numerous times.
!ENTRY org.eclipse.ui.views 2 0 2025-05-12 10:36:32.269
!MESSAGE Could not resolve module: org.eclipse.ui.views [26]
Here is the full error log file from "tlaplus/toolbox/org.lamport.tla.toolbox.test/target/work/configuration/1747060591331.log''
It's my assumption that I need to point the build to certain Eclipse libraries.
I have the Eclipse IDE installed on macOS. How do I set up a Eclipse project for the Toolbox IDE? The page "Developing with the Eclipse IDE'' (linked from DEVELOPING.md) describes installing Eclipse using a tool called "Oomph" but I am looking for a simpler alternative. I want to avoid using Git from inside Eclipse, I would like to work at the command-line, use my own editor, and, if and when necessary, run the tests (the purpose of ``mvn verify'') in Eclipse. Is there a way to set up the Eclipse project by pointing Eclipse to a particular directory, analogus to opening the "tlatools/org.lamport.tlatools'' project directory for "tlatools''?