Playground: Difference between revisions
Jump to navigation
Jump to search
Line 54: | Line 54: | ||
=Operations= | =Operations= | ||
==Run Locally== | |||
Use: | |||
<pre> | |||
./bin/run | |||
</pre> | |||
The script will assemble the classpath automatically and will attempt to guess the main class. | |||
==Deployment/Undeployment== | |||
<pre> | <pre> |
Revision as of 01:26, 28 November 2016
Reference Assets
Reference operations script: playground/project-template/bin/operations. Works with local and remote servers.
New Project
Use the playground project template:
This template contains a basic structure and artifacts to be used when starting new playground project. In order to create a new project:
1. Recursively copy the template under a new name, and customize it
cp -r .../project-template .../<your-project-name> cd .../<your-project-name> rm -r .idea
2. Edit pom.xml
name
groupId
The Maven group should follow the playground directory structure:
<groupId>io.novaordis.playground.wildfly.hornetq</groupId>
artifactId
Example:
<artifactId>simple-hornetq-client</artifactId>
This will become the IntelliJ project name.
finalName
3. Create the IntelliJ project
Import Project from Maven.
Keep project files in .../.idea.
4. Edit README.md
Operations
Run Locally
Use:
./bin/run
The script will assemble the classpath automatically and will attempt to guess the main class.
Deployment/Undeployment
deploy --help
undeploy --help