Setup information missing

[gvlx]

Setup information (in README.md) should include the basic information to configure Designer to access and debug the Java code.

[gvlx]

File Installation

• Install Tundra package as described in the README.md.
• Unzip the src and docs of the Tundra.java inside the Tundra package code directory.
• Reload the Tundra package

Designer Configuration

Tundra.Java

You should create a new java project with the location pointing to the src directory of the unzipped file (I the following example called it "permafrost.tundra").

Add the following "Libraries" in the project setup's Java Build Path:

• External JARs from the code/jars/static directory of the Tundra package:
  • commons-csv-1.0.jar
  • javax.json-1.0.4.jar
  • snakeyaml-1.15.jar
  • spring-core-4.1.2.RELEASE.jar
  • spring-web-4.1.2.RELEASE.jar
  • xmlsec-1.5.8.jar
• Variables:
  • IS_CLIENT
  • IS_SERVER
  • IS_MAIL
  • ECLIPSE_OSGI
• Libraries:
  • JUnit4

Tundra

Add the following libraries in the Tundra java project setup's Java Build Path:

• External JARs from the code/jars/static directory of the Tundra package:
  • commons-csv-1.0.jar
  • javax.json-1.0.4.jar
  • snakeyaml-1.15.jar
  • spring-core-4.1.2.RELEASE.jar
  • spring-web-4.1.2.RELEASE.jar
  • xmlsec-1.5.8.jar
• Variables
  • IS_CLIENT
  • IS_SERVER

Add the Tundra.Java project "permafrost.tundra" as a project in the Java Build Path.

NOTE: if you are not using the Tundra.java package, add the external JAR Tundra.jar in the Java Build Path above.

The beauty of open source is this.

Colaboration.

[gvlx]

I found some more missing libraries in the tests of the Package but I have to reset my changes to find what I changed to make them pass. (no git access where I tested).

[lachlan]

@gvlx thanks for that!

I would recommend cloning the Tundra.java git repository in its entirety to a completely different directory than the ./packages/Tundra directory in your Integration Server (keep the two projects separate):

C:\>mkdir Workspace
C:\>cd Workspace
C:\Workspace>git clone https://github.com/Permafrost/Tundra.java.git
C:\Workspace>cd Tundra.java
C:\Workspace\Tundra.java>

Then create a new Java project in Designer/eclipse whose directory is C:\Workspace\Tundra.java (or whatever directory you choose), rather than storing the source code directly in the Tundra package's code directory like you suggest above. This way, you can still use git against both your Tundra and Tundra.java git repository clones for version control.

You can then add this Tundra.java eclipse project as a project dependency to your Tundra Java project (Designer usually creates this automatically in my experience), which should let you debug across projects.

I think the Tundra.java README should be updated to include instructions on how to set it up as a separate project in Designer/eclipse, and also how to set up the dependencies between the projects so you can debug across them.

Thoughts?

By the way, I'm pretty new to Designer myself. I actually prefer using Intellij as my Java IDE, which is what I'm currently using to develop the Tundra.java project.

[gvlx]

Hi, you're right about separating both projects (they are different projects after all), notwithstanding to be able to continue to use git on both.

Probably the best way to add Tundra.java is to make Designer manage it entirely, either from the git URL or from the zip file.

As I had already the Tundra project created, Designer did not find the Tundra.java dependency afterwards, so the order in which we install both projects is important (something I missed as I only realized afterwards that you had created this java project).

I'll test this and a add note here.

I have nothing against using other tools but I must use the vendor provided Designer Eclipse to be able to fully integrate with the platform, so I'll keep posting other relevant information when I find it.