forked from geonetwork/core-geonetwork
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
troubleshoot release module order of execution and profile acivation …
…and handling of jetty folder Signed-off-by: Jody Garnett <[email protected]>
- Loading branch information
1 parent
9411ca8
commit 9b05882
Showing
5 changed files
with
106 additions
and
67 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,30 +1,46 @@ | ||
Release | ||
======= | ||
|
||
The release module for GeoNetwork requires jetty to be downloaded before it will package an installer for use. | ||
The release module for GeoNetwork. | ||
|
||
1. Build geonetwork if you have not done so already | ||
|
||
``` | ||
mvn clean install -DskipTests | ||
``` | ||
To generate ``zip`` bundles use the release profile (``release``, ``cmis``, ``jcloud``, ``s3``): | ||
``` | ||
mvn clean install -Drelease | ||
``` | ||
|
||
2. From the release folder, download jetty (you only need to do this once): | ||
To generate only for the ``release`` module: | ||
```bash | ||
cd release | ||
mvn clean install -Drelease | ||
``` | ||
|
||
``` | ||
mvn process-resources -Djetty-download | ||
``` | ||
This module is designed to be used as part of a full build. It copies files from web/target so gn-web-app must be built first. | ||
|
||
3. Once the `jetty` folder is in place the release module will package the `zip` installer: | ||
## Manual release | ||
|
||
``` | ||
mvn package | ||
``` | ||
|
||
4. The installer is created in `target` folder. | ||
Open a terminal window and execute the following steps from within the ``release`` folder. | ||
|
||
1. Once GeoNetwork has been built (run Maven in the repository root), download Jetty: | ||
|
||
3. To clean up the `jetty` folder: | ||
```bash | ||
mvn clean install -Pjetty-download | ||
``` | ||
|
||
This will download the version of jetty indicated in dependency management, and rename to ``jetty`` folder | ||
(adjusting ``jetty-deploy.xml`` configuration to use `web` rather than default ``webapps``). | ||
|
||
2. Next, create the ZIP distributions and copy the WAR: | ||
|
||
``` | ||
mvn clean:clean@reset | ||
ant | ||
``` | ||
|
||
The build.xml file will check everything is available and assemble into a zip. | ||
|
||
## Jetty download | ||
|
||
To clean up the ``jetty`` download, when switching between branches: | ||
|
||
```bash | ||
mvn clean:clean@reset | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters