Creating an OJ release version - Revision history

Edso: /* The release step by step list */

2023-03-21T13:32:53Z

The release step by step list

Edso at 13:21, 27 November 2022

2022-11-27T13:21:51Z

Edso at 13:20, 27 November 2022

2022-11-27T13:20:45Z

Edso at 10:26, 21 October 2022

2022-10-21T10:26:58Z

Edso: /* The release step by step list */

2022-08-01T14:16:50Z

The release step by step list

Edso: /* The release step by step list */

2022-08-01T14:14:42Z

The release step by step list

Michaudm: /* Build a release example */

2018-04-29T07:59:24Z

Build a release example

Edso: /* The release step by step list */

2017-04-13T14:36:26Z

The release step by step list

Edso: /* The release step by step list */

2017-04-13T14:35:46Z

The release step by step list

Edso: /* New Build/Release Procedure */

2013-07-24T09:00:17Z

New Build/Release Procedure

@@ Line 68: / Line 68: @@
 ## copy/sort out, commit
 # change version in '''pom.xml'''
-# add tag to repository
+# add tag to repository e.g. '2.2.0'
 # build e.g. <pre>mvn package -P release,portable,installer,srczip,javadoc</pre> will build release type portable distros, installer, src-zip and javadoc-zip
 # test startup on all supported platform (if possible)
-# if you all went to plan, '''push changes''' to online repo, if not simply delete the tag and change what is needed, tag again, rebuild, test (repeat as needed)
+# update online git repo
 # create '''release notes''' readme.txt (a modified readme.txt to be placed on sf.net files)
 ## append all changes in this minor version to the end (e.g. 2.1.0 - 2.1.2) as the folder holds them all

@@ Line 72: / Line 72: @@
 # test startup on all supported platform (if possible)
 # if you all went to plan, '''push changes''' to online repo, if not simply delete the tag and change what is needed, tag again, rebuild, test (repeat as needed)
-# create *release notes* readme.txt (a modified readme.txt to be placed on sf.net files)
+# create '''release notes''' readme.txt (a modified readme.txt to be placed on sf.net files)
 ## append all changes in this minor version to the end (e.g. 2.1.0 - 2.1.2) as the folder holds them all
 ## add a table of contents point for changes at the beginning
@@ Line 82: / Line 82: @@
 ### source zip
 ### javadoc zip (apidoc)
-## *release notes* readme.txt (sf.net files version)
+## '''release notes''' readme.txt (sf.net files version)
 # assign default download button per platform under file info (i)
 # update Download links

@@ Line 72: / Line 72: @@
 # test startup on all supported platform (if possible)
 # if you all went to plan, '''push changes''' to online repo, if not simply delete the tag and change what is needed, tag again, rebuild, test (repeat as needed)
-# update release notes (sf.net files readme.txt)
+# create *release notes* readme.txt (a modified readme.txt to be placed on sf.net files)
 # upload files to sourceforge's file release system (sf.net files)
 ## release files
@@ Line 79: / Line 82: @@
 ### source zip
 ### javadoc zip (apidoc)
-## readme.txt (sf.net files version)
+## *release notes* readme.txt (sf.net files version)
 # assign default download button per platform under file info (i)
 # update Download links

@@ Line 4: / Line 4: @@
 ; <span style="color: red;">ATTENTION:
-: <span style="color: red;">Always run maven from the root of your checked out svn folder. Meaning chdir into it first and make sure it is your current working dir.
+: <span style="color: red;">Always run maven in the '''root of the local repo folder'''. Meaning chdir into it first and make sure it is your current working dir.
 === '''Maven profiles''' ===
@@ Line 55: / Line 55: @@
 example
-  cd <svn-checkout-folder>/
+  cd <git-clone-folder>/
   mvn package -P release -D version.number=1.5.1
 === '''The release ''step by step'' list''' ===
-# Check etc/readme.txt (new components, licenses, contributors ...?)
+# Check '''etc/readme.txt''' (new components, licenses, contributors ...?)
 ## update and commit.
-# summarize the changes to the previous version in Changes.txt, based on the [https://github.com/openjump-gis/openjump/commits git commit log] (copy/sorting out), commit to trunk
+# summarize the changes since the previous version in '''Changes.txt''',
-# add svn tag
+## either
-# build release files with maven as outlined above
+### run <pre>mvn generate-sources</pre> and use the 'Unreleased commits' in generated file 'target/res/Git-log.txt' or
 # test startup on all supported platform (if possible)
 # update release notes (sf.net files readme.txt)
-# upload the files to sourceforge's FRS
+# upload files to sourceforge's file release system (sf.net files)
 ## release files
 ## readme.txt (sf.net files version)
 # assign default download button per platform under file info (i)

@@ Line 62: / Line 62: @@
 # Check etc/readme.txt (new components, licenses, contributors ...?)
 ## update and commit.
-# summarize the changes to the previous version in Changes.txt, based on the git commit log (copy/sorting out), commit to trunk
+# summarize the changes to the previous version in Changes.txt, based on the [https://github.com/openjump-gis/openjump/commits git commit log] (copy/sorting out), commit to trunk
 # add svn tag
 # build release files with maven as outlined above

← Older revision		Revision as of 07:59, 29 April 2018
Line 52:		Line 52:

	* for releases you might want to give a version.number (default=unknown) and a version.release (default=release)		* for releases you might want to give a version.number (default=unknown) and a version.release (default=release)
		+	* version.release should have one of two values : release or snapshot

	example		example

@@ Line 71: / Line 71: @@
 # assign default download button per platform under file info (i)
 # update Download links
-## on [[Wiki front page|Main_Page]]
+## on [[Main_Page|Wiki front page]]
 ## on [[Downloading OpenJUMP|Download wiki page]]
 ## on http://openjump.org website

← Older revision		Revision as of 09:00, 24 July 2013
Line 2:		Line 2:

	The new build and release procedure uses maven.		The new build and release procedure uses maven.
		+
		+	; <span style="color: red;">ATTENTION:
		+	: <span style="color: red;">Always run maven from the root of your checked out svn folder. Meaning chdir into it first and make sure it is your current working dir.

	=== '''Maven profiles''' ===		=== '''Maven profiles''' ===