- Java Development Kit (Membrane's source is Java 17 compatible.)
- Maven 3
- IntelliJ or Eclipse (3.7, 4.2, ...) with the m2e plugin
- some git client
-
To import the Project into your Eclipse, you have to install the Maven plugin for Eclipse(m2e plugin).
-
To install the plugin start Eclipse and select Help->Install New Software.
-
Select http://download.eclipse.org/releases/juno in the Drop down Menu "Work with:".
-
Then search for "maven" within the listed plugins. Fastest option is to use the Filter.
-
Select the m2e plugin named "m2e - Maven Integration for Eclipse" and hit next.
-
Now you'll have to finish this installation by accepting the terms of agreement. Eclipse should be installing the plugin now.
-
Checkout the source code from https://github.com/membrane/service-proxy .
-
Now go to Files->import and select "Existing Maven projects".
-
In the next section you will have to set the service-proxy\cli directory as root-directory. Hit Finish. Eclipse is now building the Workspace, this might take some time. Some build errors will remain until you have completed the next steps.
-
The project service-proxy-annot should be error-free. Right click it and run as "Maven install".
-
Enable annotation processing on service-proxy-core and service-proxy-war: For both projects, a. Right-click the project. b. Choose "Properties". c. Expand "Java Compiler". d. Select "Annotation Processing". e. Check both [X] Enable project specific settings [X] Enable annotation processing
(Skip to the next section, if you don't need a distribution build.)
-
Right click the service-proxy-core and run as "Maven install".
-
Right click membrane-service-proxy and run as "Maven install".
-
After doing so membrane-service-proxy-x.x.x.zip should be in the \cli\target folder.
- To run cli, navigate src/main/java/com.predic8.membrane.core/ and run IDEStarter as "Java Application".
To run the integration tests in an isolated environment, run
docker build .
if you have a Docker Engine available.
The example tests try to run the service-proxy.sh/bat scripts in the examples folders of a distribution build in the target folder. Remember to build after any change otherwise old code is tested:
Build a distribution in target/ . Then run the example tests.
mvn clean install -DskipTests
On Mac OS the setsid
command is needed. It can be installed with:
brew install util-linux
Run Testclass ExampleTests