Author: solomax Date: Mon Aug 15 03:14:09 2016 New Revision: 1756343 URL: http://svn.apache.org/viewvc?rev=1756343&view=rev Log: Release preparation: publishing to Maven repo works as expected, documentation is updated
Modified:
openmeetings/application/branches/3.1.x/openmeetings-server/pom.xml
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
openmeetings/application/branches/3.1.x/pom.xml
openmeetings/application/branches/3.2.x/openmeetings-server/pom.xml
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
openmeetings/application/branches/3.2.x/pom.xml
openmeetings/application/trunk/openmeetings-server/pom.xml
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
openmeetings/application/trunk/pom.xml
openmeetings/site/trunk/ReleaseGuide.html
Modified: openmeetings/application/branches/3.1.x/openmeetings-server/pom.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.1.x/openmeetings-server/pom.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
--- openmeetings/application/branches/3.1.x/openmeetings-server/pom.xml
(original)
+++ openmeetings/application/branches/3.1.x/openmeetings-server/pom.xml Mon Aug
15 03:14:09 2016
@@ -160,20 +160,19 @@
<build>
<plugins>
<plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>truezip-maven-plugin</artifactId>
+ <artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>unpack-red5-server</id>
+ <phase>prepare-package</phase>
<goals>
- <goal>copy</goal>
+ <goal>run</goal>
</goals>
- <phase>prepare-package</phase>
<configuration>
- <fileset>
-
<directory>${red5-server-file.dir}/red5-server-${red5-server.version}.tar.gz/red5-server</directory>
-
<outputDirectory>${server.dir}</outputDirectory>
- </fileset>
+ <target>
+ <untar
src="${red5-server-file.dir}/red5-server-${red5-server.version}.tar.gz"
dest="${project.build.directory}"
+
compression="gzip" overwrite="true"/>
+ </target>
<skip>${om.quick.build}</skip>
</configuration>
</execution>
@@ -218,6 +217,9 @@
<execution>
<id>make-assembly</id>
<phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
<configuration>
<descriptors>
<descriptor>${project.basedir}/src/main/assembly/${assembly.descriptor}.xml</descriptor>
@@ -226,13 +228,13 @@
<appendAssemblyId>false</appendAssemblyId>
<tarLongFileMode>gnu</tarLongFileMode>
</configuration>
- <goals>
- <goal>single</goal>
- </goals>
</execution>
<execution>
<id>make-src</id>
<phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
<configuration>
<descriptors>
<descriptor>${project.basedir}/src/main/assembly/src.xml</descriptor>
@@ -242,9 +244,6 @@
<tarLongFileMode>gnu</tarLongFileMode>
<skipAssembly>${src.pack.skip}</skipAssembly>
</configuration>
- <goals>
- <goal>single</goal>
- </goals>
</execution>
</executions>
</plugin>
@@ -269,19 +268,6 @@
</goals>
</pluginExecutionFilter>
<action>
-
<ignore></ignore>
-
</action>
-
</pluginExecution>
-
<pluginExecution>
-
<pluginExecutionFilter>
-
<groupId>org.codehaus.mojo</groupId>
-
<artifactId>truezip-maven-plugin</artifactId>
-
<versionRange>[1.2,)</versionRange>
-
<goals>
-
<goal>copy</goal>
-
</goals>
-
</pluginExecutionFilter>
- <action>
<ignore></ignore>
</action>
</pluginExecution>
Modified:
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
---
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
(original)
+++
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
Mon Aug 15 03:14:09 2016
@@ -21,11 +21,8 @@
</properties>
<body>
-
<section name="How to Build a Release of OpenMeetings">
-
<subsection name="Required tools">
-
<div>
<p>To build a binary release of
OpenMeetings you need: </p>
<ul>
@@ -42,96 +39,115 @@
</li>
</ul>
</div>
-
</subsection>
-
<subsection name="Prepare your Apache ID">
-
<div>
- Every release package must be signed
with a PGP/GPG key.
- <br />
- So if you want to release a package
your Apache Id must be
- connected with a PGP key!
- <br />
- <br />
- You might follow:
- <br />
- <a
-
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
-
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
- </a>
- <br />
- <br />
- In short:
- <br />
- Create PGP key pairs (private + public)
(and I recommend creating a
- Revoke Cert)
- <br />
- Upload the public key (either bei using
the PGP Tool that you use
- to create the key) or by using the web
form to:
- <a href="http://pgp.mit.edu/";
target="_blank" rel="nofollow">http://pgp.mit.edu/
- </a>
- <br />
- Add the fingerprint string (something
like "BF13 CF11 F9C9 0CBE
- 4413 09AB 0055 16BF 93A3 0395") to your
profile at
- <a href="https://id.apache.org/";
target="_blank" rel="nofollow">https://id.apache.org/</a>
- <br />
- Wait for 6-8 hours, the server will
search for a public key based
- on your fingerprint, if success it will
create a file with your
- name at:
- <br />
- <a
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
- <br />
- <br />
- If that is "success" then add your key
to:
- <br />
- <a
-
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS
- </a>
- <br />
- and follow the instructions in the file.
- <br />
+ <ul>
+ <li><b>Every release package
must be signed with a PGP/GPG key.</b><br />
+ So if you want to
release a package your Apache Id must be
+ connected with a PGP
key!
+ <br />
+ <br />
+ You might follow:
+ <br />
+ <a
+
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
+
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
+ </a>
+ <br />
+ <br />
+ In short:
+ <ul>
+ <li>Create PGP
key pairs (private + public) (and I recommend creating a Revoke Cert)</li>
+ <li>Upload the
public key (either bei using the PGP Tool that you use
+ to
create the key) or by using the web form to:
+ <a
href="http://pgp.mit.edu/"; target="_blank"
rel="nofollow">http://pgp.mit.edu/</a>
+ </li>
+ <li>Add the
fingerprint string (something like "BF13 CF11 F9C9 0CBE
+ 4413
09AB 0055 16BF 93A3 0395") to your profile at
+ <a
href="https://id.apache.org/"; target="_blank"
rel="nofollow">https://id.apache.org/</a>
+ </li>
+ <li>
+ Wait
for 6-8 hours, the server will search for a public key based
+ on your
fingerprint, if success it will create a file with your
+ name at:
+ <br />
+ <a
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
+ </li>
+ <li>
+ If that
is "success" then add your key to:
+ <br />
+ <a
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS</a>
+ <br />
+ <br />
+ and
follow the instructions in the file.
+ </li>
+ </ul>
+ </li>
+ <li><b>Maven</b><br/>
+ <ul>
+ <li>Ensure you
able to login to <a
href="https://repository.apache.org/";>https://repository.apache.org</a></li>
+ <li>
+ Set up
development environment as described here: <a
href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>Setup
development environment</a><br/>
+ Don't
forget to secure passwords as described here: <a
href="http://maven.apache.org/guides/mini/guide-encryption.html#How_to_create_a_master_password";>Password
Encryption</a>
+ </li>
+
+ </ul>
+ </li>
+ </ul>
</div>
-
</subsection>
-
<subsection name="Step1 - Prepare files">
- <p>
- Check that all files:
- <br />
- LICENSE, NOTICE, DISCLAIMER, CHANGELOG,
README
- <br />
- are up to date and refer to the right
version.
- </p>
-
- <p>
- Create a TAG of the SVN tree that you
would like to release<br/>
- Example:
- </p>
+ <ul>
+ <li>
+ Check that all files:<br />
+ LICENSE, NOTICE, DISCLAIMER,
CHANGELOG, README<br />
+ are up to date and refer to the
right version.
+ </li>
+ <li>
+ Create a TAG of the SVN tree
that you would like to release<br/>
+ Example:
- <source>
+ <source>
svn copy -r1453158
https://svn.apache.org/repos/asf/openmeetings/application/trunk \
https://svn.apache.org/repos/asf/openmeetings/application/tags/3.1.0RC1
\
-m "3.1.0 Release candidate 1"
- </source>
-
-
- <p>Get the source from your TAG: </p>
- <source>svn checkout
https://svn.apache.org/repos/asf/openmeetings/application/tags/$BRANCHORTAG/</source>
- <p>$BRANCHORTAG should be replaced with your
new TAG</p>
-
- <p>Update versions of all modules</p>
- <source>mvn versions:set
-DgenerateBackupPoms=false -DnewVersion=3.1.0</source>
- <p>Run the command: </p>
- <source>mvn clean install -Prc</source>
- <p>Test building the source on windows and OSx
or Linux</p>
- <p>Test running the binary's</p>
- <p>
- Commit artifacts you have created with
KEYS file to the
-
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
- Proposed file structure for "Release
Candidate 1" of 3.1.0 will be:
- </p>
- <source>
+ </source>
+ </li>
+ <li>
+ <p>Get the source from your
TAG: </p>
+ <source>svn checkout
https://svn.apache.org/repos/asf/openmeetings/application/tags/$BRANCHORTAG/</source>
+ <p>$BRANCHORTAG should be
replaced with your new TAG</p>
+ </li>
+ <li>
+ <p>Update versions of all
modules</p>
+ <source>mvn versions:set
-DgenerateBackupPoms=false -DnewVersion=3.1.0</source>
+ </li>
+ <li>Deploy release artifacts to Maven
+ <ul>
+ <li>
+ <source>
+mvn clean
+mvn deploy -Pdeploy,rc
+ </source>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Run the command: </p>
+ <source>mvn clean install
-Prc</source>
+ </li>
+ <li>
+ <p>Test building the source on
windows and OSx or Linux</p>
+ <p>Test running the binary's</p>
+ </li>
+ <li>
+ <p>
+ Commit artifacts you
have created with KEYS file to the
+
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
+ Proposed file structure
for "Release Candidate 1" of 3.1.0 will be:
+ </p>
+ <source>
3.1.0
3.1.0/rc1
3.1.0/rc1/src
@@ -150,7 +166,12 @@ svn copy -r1453158 https://svn.apache.or
3.1.0/rc1/bin/apache-openmeetings-3.1.0.tar.gz.asc
3.1.0/rc1/CHANGELOG
3.1.0/rc1/KEYS
- </source>
+ </source>
+ </li>
+ <li>Upload Artifacts with signatures
created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+ </ul>
</subsection>
<subsection name="Step2 - VOTE and RESULT emails">
@@ -245,31 +266,45 @@ for f in `ls -1 *.tar.gz *.zip`; do gpg
<subsection name="Step4 - Distribute and announce">
<p>If VOTEs positive: Upload the release </p>
- <p>Upload Artifacts with signatures created on
the previous steps to
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION</p>
- <p>
- Wait 24 hours (until all Apache mirrors
have synced the packages)
- and send an announcement to the mailing
list + blog and any other
- channel.
- </p>
- <p>
- Email announcements should have the
subject line:
- <br />
- [ANNOUNCE] Apache OpenMeetings x.xx
released
- </p>
- <p>
- Update release section of DOAP file
<tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
- </p>
- <p>
- Add a section to <a
href="downloads.html">downloads</a> website.<br />
- Make sure that the binary packages are
linked using the mirror URL as base path (
- <b>not</b>
http://www.apache.org/dist):<br />
- Mirror URL:
- <a
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
- </p>
- <p>
- Release candidates should be deleted
from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br/>
- Old releases should be deleted from
<tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
- </p>
+ <ul>
+ <li>Upload Artifacts with signatures
created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+ <li>Close staging repo:
+ <ul>
+ <li>Go to: <a
href="https://repository.apache.org/#stagingRepositories";>Staging
Repositories</a></li>
+ <li>Select openmeetings
staging repo and Close it with valid message:<br/>
+ for ex. "The
VOTE about 3.1.2 release was successful"
+ </li>
+ <li>Select openmeetings
staging repo and Release it with valid message:<br/>
+ for ex. "The
VOTE about 3.1.2 release was successful"
+ </li>
+ </ul>
+ </li>
+ <li>
+ Wait 24 hours (until all Apache
mirrors have synced the packages)
+ and send an announcement to the
mailing list + blog and any other
+ channel.
+ </li>
+ <li>
+ Email announcements should have
the subject line:<br />
+ [ANNOUNCE] Apache OpenMeetings
x.xx released
+ </li>
+ <li>
+ Update release section of DOAP
file <tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
+ </li>
+ <li>
+ Add a section to <a
href="downloads.html">downloads</a> website.<br />
+ Make sure that the binary
packages are linked using the mirror URL as base path (
+ <b>not</b>
http://www.apache.org/dist):<br />
+ Mirror URL:
+ <a
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
+ </li>
+ <li>
+ Release candidates should be
deleted from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br/>
+ Old releases should be deleted
from <tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
+ </li>
+ </ul>
</subsection>
</section>
</body>
Modified: openmeetings/application/branches/3.1.x/pom.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.1.x/pom.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
--- openmeetings/application/branches/3.1.x/pom.xml (original)
+++ openmeetings/application/branches/3.1.x/pom.xml Mon Aug 15 03:14:09 2016
@@ -58,20 +58,26 @@
<tomcat.version>8.0.36</tomcat.version>
<derby.version>10.12.1.1</derby.version>
</properties>
- <modules>
- <module>openmeetings-util</module>
- <module>openmeetings-db</module>
- <module>openmeetings-core</module>
- <module>openmeetings-install</module>
- <module>openmeetings-service</module>
- <module>openmeetings-webservice</module>
- <module>openmeetings-web</module>
- <module>openmeetings-flash</module>
- <module>openmeetings-screenshare</module>
- <module>openmeetings-server</module>
- </modules>
<profiles>
<profile>
+ <id>AllModules</id>
+ <activation>
+ <activeByDefault>true</activeByDefault>
+ </activation>
+ <modules>
+ <module>openmeetings-util</module>
+ <module>openmeetings-db</module>
+ <module>openmeetings-core</module>
+ <module>openmeetings-install</module>
+ <module>openmeetings-service</module>
+ <module>openmeetings-webservice</module>
+ <module>openmeetings-web</module>
+ <module>openmeetings-flash</module>
+ <module>openmeetings-screenshare</module>
+ <module>openmeetings-server</module>
+ </modules>
+ </profile>
+ <profile>
<id>Quick</id>
<activation>
<property>
@@ -197,6 +203,13 @@
<jarsigner.skip>true</jarsigner.skip>
</properties>
</profile>
+ <profile>
+ <id>deploy</id>
+ <modules>
+ <module>openmeetings-util</module>
+ <module>openmeetings-db</module>
+ </modules>
+ </profile>
</profiles>
<url>http://openmeetings.apache.org</url>
<inceptionYear>2012</inceptionYear>
@@ -848,11 +861,6 @@
<version>1.8</version>
</plugin>
<plugin>
- <groupId>org.codehaus.mojo</groupId>
-
<artifactId>truezip-maven-plugin</artifactId>
- <version>1.2</version>
- </plugin>
- <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.6</version>
Modified: openmeetings/application/branches/3.2.x/openmeetings-server/pom.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.2.x/openmeetings-server/pom.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
--- openmeetings/application/branches/3.2.x/openmeetings-server/pom.xml
(original)
+++ openmeetings/application/branches/3.2.x/openmeetings-server/pom.xml Mon Aug
15 03:14:09 2016
@@ -160,20 +160,19 @@
<build>
<plugins>
<plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>truezip-maven-plugin</artifactId>
+ <artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>unpack-red5-server</id>
+ <phase>prepare-package</phase>
<goals>
- <goal>copy</goal>
+ <goal>run</goal>
</goals>
- <phase>prepare-package</phase>
<configuration>
- <fileset>
-
<directory>${red5-server-file.dir}/red5-server-${red5-server.version}.tar.gz/red5-server</directory>
-
<outputDirectory>${server.dir}</outputDirectory>
- </fileset>
+ <target>
+ <untar
src="${red5-server-file.dir}/red5-server-${red5-server.version}.tar.gz"
dest="${project.build.directory}"
+
compression="gzip" overwrite="true"/>
+ </target>
<skip>${om.quick.build}</skip>
</configuration>
</execution>
@@ -218,6 +217,9 @@
<execution>
<id>make-assembly</id>
<phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
<configuration>
<descriptors>
<descriptor>${project.basedir}/src/main/assembly/${assembly.descriptor}.xml</descriptor>
@@ -226,13 +228,13 @@
<appendAssemblyId>false</appendAssemblyId>
<tarLongFileMode>gnu</tarLongFileMode>
</configuration>
- <goals>
- <goal>single</goal>
- </goals>
</execution>
<execution>
<id>make-src</id>
<phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
<configuration>
<descriptors>
<descriptor>${project.basedir}/src/main/assembly/src.xml</descriptor>
@@ -242,9 +244,6 @@
<tarLongFileMode>gnu</tarLongFileMode>
<skipAssembly>${src.pack.skip}</skipAssembly>
</configuration>
- <goals>
- <goal>single</goal>
- </goals>
</execution>
</executions>
</plugin>
@@ -269,19 +268,6 @@
</goals>
</pluginExecutionFilter>
<action>
-
<ignore></ignore>
-
</action>
-
</pluginExecution>
-
<pluginExecution>
-
<pluginExecutionFilter>
-
<groupId>org.codehaus.mojo</groupId>
-
<artifactId>truezip-maven-plugin</artifactId>
-
<versionRange>[1.2,)</versionRange>
-
<goals>
-
<goal>copy</goal>
-
</goals>
-
</pluginExecutionFilter>
- <action>
<ignore></ignore>
</action>
</pluginExecution>
Modified:
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
---
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
(original)
+++
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
Mon Aug 15 03:14:09 2016
@@ -21,11 +21,8 @@
</properties>
<body>
-
<section name="How to Build a Release of OpenMeetings">
-
<subsection name="Required tools">
-
<div>
<p>To build a binary release of
OpenMeetings you need: </p>
<ul>
@@ -42,96 +39,115 @@
</li>
</ul>
</div>
-
</subsection>
-
<subsection name="Prepare your Apache ID">
-
<div>
- Every release package must be signed
with a PGP/GPG key.
- <br />
- So if you want to release a package
your Apache Id must be
- connected with a PGP key!
- <br />
- <br />
- You might follow:
- <br />
- <a
-
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
-
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
- </a>
- <br />
- <br />
- In short:
- <br />
- Create PGP key pairs (private + public)
(and I recommend creating a
- Revoke Cert)
- <br />
- Upload the public key (either bei using
the PGP Tool that you use
- to create the key) or by using the web
form to:
- <a href="http://pgp.mit.edu/";
target="_blank" rel="nofollow">http://pgp.mit.edu/
- </a>
- <br />
- Add the fingerprint string (something
like "BF13 CF11 F9C9 0CBE
- 4413 09AB 0055 16BF 93A3 0395") to your
profile at
- <a href="https://id.apache.org/";
target="_blank" rel="nofollow">https://id.apache.org/</a>
- <br />
- Wait for 6-8 hours, the server will
search for a public key based
- on your fingerprint, if success it will
create a file with your
- name at:
- <br />
- <a
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
- <br />
- <br />
- If that is "success" then add your key
to:
- <br />
- <a
-
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS
- </a>
- <br />
- and follow the instructions in the file.
- <br />
+ <ul>
+ <li><b>Every release package
must be signed with a PGP/GPG key.</b><br />
+ So if you want to
release a package your Apache Id must be
+ connected with a PGP
key!
+ <br />
+ <br />
+ You might follow:
+ <br />
+ <a
+
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
+
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
+ </a>
+ <br />
+ <br />
+ In short:
+ <ul>
+ <li>Create PGP
key pairs (private + public) (and I recommend creating a Revoke Cert)</li>
+ <li>Upload the
public key (either bei using the PGP Tool that you use
+ to
create the key) or by using the web form to:
+ <a
href="http://pgp.mit.edu/"; target="_blank"
rel="nofollow">http://pgp.mit.edu/</a>
+ </li>
+ <li>Add the
fingerprint string (something like "BF13 CF11 F9C9 0CBE
+ 4413
09AB 0055 16BF 93A3 0395") to your profile at
+ <a
href="https://id.apache.org/"; target="_blank"
rel="nofollow">https://id.apache.org/</a>
+ </li>
+ <li>
+ Wait
for 6-8 hours, the server will search for a public key based
+ on your
fingerprint, if success it will create a file with your
+ name at:
+ <br />
+ <a
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
+ </li>
+ <li>
+ If that
is "success" then add your key to:
+ <br />
+ <a
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS</a>
+ <br />
+ <br />
+ and
follow the instructions in the file.
+ </li>
+ </ul>
+ </li>
+ <li><b>Maven</b><br/>
+ <ul>
+ <li>Ensure you
able to login to <a
href="https://repository.apache.org/";>https://repository.apache.org</a></li>
+ <li>
+ Set up
development environment as described here: <a
href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>Setup
development environment</a><br/>
+ Don't
forget to secure passwords as described here: <a
href="http://maven.apache.org/guides/mini/guide-encryption.html#How_to_create_a_master_password";>Password
Encryption</a>
+ </li>
+
+ </ul>
+ </li>
+ </ul>
</div>
-
</subsection>
-
<subsection name="Step1 - Prepare files">
- <p>
- Check that all files:
- <br />
- LICENSE, NOTICE, DISCLAIMER, CHANGELOG,
README
- <br />
- are up to date and refer to the right
version.
- </p>
-
- <p>
- Create a TAG of the SVN tree that you
would like to release<br/>
- Example:
- </p>
+ <ul>
+ <li>
+ Check that all files:<br />
+ LICENSE, NOTICE, DISCLAIMER,
CHANGELOG, README<br />
+ are up to date and refer to the
right version.
+ </li>
+ <li>
+ Create a TAG of the SVN tree
that you would like to release<br/>
+ Example:
- <source>
+ <source>
svn copy -r1453158
https://svn.apache.org/repos/asf/openmeetings/application/trunk \
https://svn.apache.org/repos/asf/openmeetings/application/tags/3.1.0RC1
\
-m "3.1.0 Release candidate 1"
- </source>
-
-
- <p>Get the source from your TAG: </p>
- <source>svn checkout
https://svn.apache.org/repos/asf/openmeetings/application/tags/$BRANCHORTAG/</source>
- <p>$BRANCHORTAG should be replaced with your
new TAG</p>
-
- <p>Update versions of all modules</p>
- <source>mvn versions:set
-DgenerateBackupPoms=false -DnewVersion=3.1.0</source>
- <p>Run the command: </p>
- <source>mvn clean install -Prc</source>
- <p>Test building the source on windows and OSx
or Linux</p>
- <p>Test running the binary's</p>
- <p>
- Commit artifacts you have created with
KEYS file to the
-
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
- Proposed file structure for "Release
Candidate 1" of 3.1.0 will be:
- </p>
- <source>
+ </source>
+ </li>
+ <li>
+ <p>Get the source from your
TAG: </p>
+ <source>svn checkout
https://svn.apache.org/repos/asf/openmeetings/application/tags/$BRANCHORTAG/</source>
+ <p>$BRANCHORTAG should be
replaced with your new TAG</p>
+ </li>
+ <li>
+ <p>Update versions of all
modules</p>
+ <source>mvn versions:set
-DgenerateBackupPoms=false -DnewVersion=3.1.0</source>
+ </li>
+ <li>Deploy release artifacts to Maven
+ <ul>
+ <li>
+ <source>
+mvn clean
+mvn deploy -Pdeploy,rc
+ </source>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Run the command: </p>
+ <source>mvn clean install
-Prc</source>
+ </li>
+ <li>
+ <p>Test building the source on
windows and OSx or Linux</p>
+ <p>Test running the binary's</p>
+ </li>
+ <li>
+ <p>
+ Commit artifacts you
have created with KEYS file to the
+
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
+ Proposed file structure
for "Release Candidate 1" of 3.1.0 will be:
+ </p>
+ <source>
3.1.0
3.1.0/rc1
3.1.0/rc1/src
@@ -150,7 +166,12 @@ svn copy -r1453158 https://svn.apache.or
3.1.0/rc1/bin/apache-openmeetings-3.1.0.tar.gz.asc
3.1.0/rc1/CHANGELOG
3.1.0/rc1/KEYS
- </source>
+ </source>
+ </li>
+ <li>Upload Artifacts with signatures
created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+ </ul>
</subsection>
<subsection name="Step2 - VOTE and RESULT emails">
@@ -245,31 +266,45 @@ for f in `ls -1 *.tar.gz *.zip`; do gpg
<subsection name="Step4 - Distribute and announce">
<p>If VOTEs positive: Upload the release </p>
- <p>Upload Artifacts with signatures created on
the previous steps to
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION</p>
- <p>
- Wait 24 hours (until all Apache mirrors
have synced the packages)
- and send an announcement to the mailing
list + blog and any other
- channel.
- </p>
- <p>
- Email announcements should have the
subject line:
- <br />
- [ANNOUNCE] Apache OpenMeetings x.xx
released
- </p>
- <p>
- Update release section of DOAP file
<tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
- </p>
- <p>
- Add a section to <a
href="downloads.html">downloads</a> website.<br />
- Make sure that the binary packages are
linked using the mirror URL as base path (
- <b>not</b>
http://www.apache.org/dist):<br />
- Mirror URL:
- <a
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
- </p>
- <p>
- Release candidates should be deleted
from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br/>
- Old releases should be deleted from
<tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
- </p>
+ <ul>
+ <li>Upload Artifacts with signatures
created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+ <li>Close staging repo:
+ <ul>
+ <li>Go to: <a
href="https://repository.apache.org/#stagingRepositories";>Staging
Repositories</a></li>
+ <li>Select openmeetings
staging repo and Close it with valid message:<br/>
+ for ex. "The
VOTE about 3.1.2 release was successful"
+ </li>
+ <li>Select openmeetings
staging repo and Release it with valid message:<br/>
+ for ex. "The
VOTE about 3.1.2 release was successful"
+ </li>
+ </ul>
+ </li>
+ <li>
+ Wait 24 hours (until all Apache
mirrors have synced the packages)
+ and send an announcement to the
mailing list + blog and any other
+ channel.
+ </li>
+ <li>
+ Email announcements should have
the subject line:<br />
+ [ANNOUNCE] Apache OpenMeetings
x.xx released
+ </li>
+ <li>
+ Update release section of DOAP
file <tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
+ </li>
+ <li>
+ Add a section to <a
href="downloads.html">downloads</a> website.<br />
+ Make sure that the binary
packages are linked using the mirror URL as base path (
+ <b>not</b>
http://www.apache.org/dist):<br />
+ Mirror URL:
+ <a
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
+ </li>
+ <li>
+ Release candidates should be
deleted from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br/>
+ Old releases should be deleted
from <tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
+ </li>
+ </ul>
</subsection>
</section>
</body>
Modified: openmeetings/application/branches/3.2.x/pom.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.2.x/pom.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
--- openmeetings/application/branches/3.2.x/pom.xml (original)
+++ openmeetings/application/branches/3.2.x/pom.xml Mon Aug 15 03:14:09 2016
@@ -58,20 +58,26 @@
<tomcat.version>8.0.36</tomcat.version>
<derby.version>10.12.1.1</derby.version>
</properties>
- <modules>
- <module>openmeetings-util</module>
- <module>openmeetings-db</module>
- <module>openmeetings-core</module>
- <module>openmeetings-install</module>
- <module>openmeetings-service</module>
- <module>openmeetings-webservice</module>
- <module>openmeetings-web</module>
- <module>openmeetings-flash</module>
- <module>openmeetings-screenshare</module>
- <module>openmeetings-server</module>
- </modules>
<profiles>
<profile>
+ <id>AllModules</id>
+ <activation>
+ <activeByDefault>true</activeByDefault>
+ </activation>
+ <modules>
+ <module>openmeetings-util</module>
+ <module>openmeetings-db</module>
+ <module>openmeetings-core</module>
+ <module>openmeetings-install</module>
+ <module>openmeetings-service</module>
+ <module>openmeetings-webservice</module>
+ <module>openmeetings-web</module>
+ <module>openmeetings-flash</module>
+ <module>openmeetings-screenshare</module>
+ <module>openmeetings-server</module>
+ </modules>
+ </profile>
+ <profile>
<id>Quick</id>
<activation>
<property>
@@ -197,6 +203,13 @@
<jarsigner.skip>true</jarsigner.skip>
</properties>
</profile>
+ <profile>
+ <id>deploy</id>
+ <modules>
+ <module>openmeetings-util</module>
+ <module>openmeetings-db</module>
+ </modules>
+ </profile>
</profiles>
<url>http://openmeetings.apache.org</url>
<inceptionYear>2012</inceptionYear>
@@ -848,11 +861,6 @@
<version>1.8</version>
</plugin>
<plugin>
- <groupId>org.codehaus.mojo</groupId>
-
<artifactId>truezip-maven-plugin</artifactId>
- <version>1.2</version>
- </plugin>
- <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.6</version>
Modified: openmeetings/application/trunk/openmeetings-server/pom.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/trunk/openmeetings-server/pom.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
--- openmeetings/application/trunk/openmeetings-server/pom.xml (original)
+++ openmeetings/application/trunk/openmeetings-server/pom.xml Mon Aug 15
03:14:09 2016
@@ -160,20 +160,19 @@
<build>
<plugins>
<plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>truezip-maven-plugin</artifactId>
+ <artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>unpack-red5-server</id>
+ <phase>prepare-package</phase>
<goals>
- <goal>copy</goal>
+ <goal>run</goal>
</goals>
- <phase>prepare-package</phase>
<configuration>
- <fileset>
-
<directory>${red5-server-file.dir}/red5-server-${red5-server.version}.tar.gz/red5-server</directory>
-
<outputDirectory>${server.dir}</outputDirectory>
- </fileset>
+ <target>
+ <untar
src="${red5-server-file.dir}/red5-server-${red5-server.version}.tar.gz"
dest="${project.build.directory}"
+
compression="gzip" overwrite="true"/>
+ </target>
<skip>${om.quick.build}</skip>
</configuration>
</execution>
@@ -218,6 +217,9 @@
<execution>
<id>make-assembly</id>
<phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
<configuration>
<descriptors>
<descriptor>${project.basedir}/src/main/assembly/${assembly.descriptor}.xml</descriptor>
@@ -226,13 +228,13 @@
<appendAssemblyId>false</appendAssemblyId>
<tarLongFileMode>gnu</tarLongFileMode>
</configuration>
- <goals>
- <goal>single</goal>
- </goals>
</execution>
<execution>
<id>make-src</id>
<phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
<configuration>
<descriptors>
<descriptor>${project.basedir}/src/main/assembly/src.xml</descriptor>
@@ -242,9 +244,6 @@
<tarLongFileMode>gnu</tarLongFileMode>
<skipAssembly>${src.pack.skip}</skipAssembly>
</configuration>
- <goals>
- <goal>single</goal>
- </goals>
</execution>
</executions>
</plugin>
@@ -269,19 +268,6 @@
</goals>
</pluginExecutionFilter>
<action>
-
<ignore></ignore>
-
</action>
-
</pluginExecution>
-
<pluginExecution>
-
<pluginExecutionFilter>
-
<groupId>org.codehaus.mojo</groupId>
-
<artifactId>truezip-maven-plugin</artifactId>
-
<versionRange>[1.2,)</versionRange>
-
<goals>
-
<goal>copy</goal>
-
</goals>
-
</pluginExecutionFilter>
- <action>
<ignore></ignore>
</action>
</pluginExecution>
Modified:
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/trunk/openmeetings-server/src/site/xdoc/ReleaseGuide.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
---
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
(original)
+++
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/ReleaseGuide.xml
Mon Aug 15 03:14:09 2016
@@ -21,11 +21,8 @@
</properties>
<body>
-
<section name="How to Build a Release of OpenMeetings">
-
<subsection name="Required tools">
-
<div>
<p>To build a binary release of
OpenMeetings you need: </p>
<ul>
@@ -42,96 +39,115 @@
</li>
</ul>
</div>
-
</subsection>
-
<subsection name="Prepare your Apache ID">
-
<div>
- Every release package must be signed
with a PGP/GPG key.
- <br />
- So if you want to release a package
your Apache Id must be
- connected with a PGP key!
- <br />
- <br />
- You might follow:
- <br />
- <a
-
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
-
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
- </a>
- <br />
- <br />
- In short:
- <br />
- Create PGP key pairs (private + public)
(and I recommend creating a
- Revoke Cert)
- <br />
- Upload the public key (either bei using
the PGP Tool that you use
- to create the key) or by using the web
form to:
- <a href="http://pgp.mit.edu/";
target="_blank" rel="nofollow">http://pgp.mit.edu/
- </a>
- <br />
- Add the fingerprint string (something
like "BF13 CF11 F9C9 0CBE
- 4413 09AB 0055 16BF 93A3 0395") to your
profile at
- <a href="https://id.apache.org/";
target="_blank" rel="nofollow">https://id.apache.org/</a>
- <br />
- Wait for 6-8 hours, the server will
search for a public key based
- on your fingerprint, if success it will
create a file with your
- name at:
- <br />
- <a
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
- <br />
- <br />
- If that is "success" then add your key
to:
- <br />
- <a
-
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS
- </a>
- <br />
- and follow the instructions in the file.
- <br />
+ <ul>
+ <li><b>Every release package
must be signed with a PGP/GPG key.</b><br />
+ So if you want to
release a package your Apache Id must be
+ connected with a PGP
key!
+ <br />
+ <br />
+ You might follow:
+ <br />
+ <a
+
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
+
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
+ </a>
+ <br />
+ <br />
+ In short:
+ <ul>
+ <li>Create PGP
key pairs (private + public) (and I recommend creating a Revoke Cert)</li>
+ <li>Upload the
public key (either bei using the PGP Tool that you use
+ to
create the key) or by using the web form to:
+ <a
href="http://pgp.mit.edu/"; target="_blank"
rel="nofollow">http://pgp.mit.edu/</a>
+ </li>
+ <li>Add the
fingerprint string (something like "BF13 CF11 F9C9 0CBE
+ 4413
09AB 0055 16BF 93A3 0395") to your profile at
+ <a
href="https://id.apache.org/"; target="_blank"
rel="nofollow">https://id.apache.org/</a>
+ </li>
+ <li>
+ Wait
for 6-8 hours, the server will search for a public key based
+ on your
fingerprint, if success it will create a file with your
+ name at:
+ <br />
+ <a
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
+ </li>
+ <li>
+ If that
is "success" then add your key to:
+ <br />
+ <a
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS</a>
+ <br />
+ <br />
+ and
follow the instructions in the file.
+ </li>
+ </ul>
+ </li>
+ <li><b>Maven</b><br/>
+ <ul>
+ <li>Ensure you
able to login to <a
href="https://repository.apache.org/";>https://repository.apache.org</a></li>
+ <li>
+ Set up
development environment as described here: <a
href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>Setup
development environment</a><br/>
+ Don't
forget to secure passwords as described here: <a
href="http://maven.apache.org/guides/mini/guide-encryption.html#How_to_create_a_master_password";>Password
Encryption</a>
+ </li>
+
+ </ul>
+ </li>
+ </ul>
</div>
-
</subsection>
-
<subsection name="Step1 - Prepare files">
- <p>
- Check that all files:
- <br />
- LICENSE, NOTICE, DISCLAIMER, CHANGELOG,
README
- <br />
- are up to date and refer to the right
version.
- </p>
-
- <p>
- Create a TAG of the SVN tree that you
would like to release<br/>
- Example:
- </p>
+ <ul>
+ <li>
+ Check that all files:<br />
+ LICENSE, NOTICE, DISCLAIMER,
CHANGELOG, README<br />
+ are up to date and refer to the
right version.
+ </li>
+ <li>
+ Create a TAG of the SVN tree
that you would like to release<br/>
+ Example:
- <source>
+ <source>
svn copy -r1453158
https://svn.apache.org/repos/asf/openmeetings/application/trunk \
https://svn.apache.org/repos/asf/openmeetings/application/tags/3.1.0RC1
\
-m "3.1.0 Release candidate 1"
- </source>
-
-
- <p>Get the source from your TAG: </p>
- <source>svn checkout
https://svn.apache.org/repos/asf/openmeetings/application/tags/$BRANCHORTAG/</source>
- <p>$BRANCHORTAG should be replaced with your
new TAG</p>
-
- <p>Update versions of all modules</p>
- <source>mvn versions:set
-DgenerateBackupPoms=false -DnewVersion=3.1.0</source>
- <p>Run the command: </p>
- <source>mvn clean install -Prc</source>
- <p>Test building the source on windows and OSx
or Linux</p>
- <p>Test running the binary's</p>
- <p>
- Commit artifacts you have created with
KEYS file to the
-
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
- Proposed file structure for "Release
Candidate 1" of 3.1.0 will be:
- </p>
- <source>
+ </source>
+ </li>
+ <li>
+ <p>Get the source from your
TAG: </p>
+ <source>svn checkout
https://svn.apache.org/repos/asf/openmeetings/application/tags/$BRANCHORTAG/</source>
+ <p>$BRANCHORTAG should be
replaced with your new TAG</p>
+ </li>
+ <li>
+ <p>Update versions of all
modules</p>
+ <source>mvn versions:set
-DgenerateBackupPoms=false -DnewVersion=3.1.0</source>
+ </li>
+ <li>Deploy release artifacts to Maven
+ <ul>
+ <li>
+ <source>
+mvn clean
+mvn deploy -Pdeploy,rc
+ </source>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Run the command: </p>
+ <source>mvn clean install
-Prc</source>
+ </li>
+ <li>
+ <p>Test building the source on
windows and OSx or Linux</p>
+ <p>Test running the binary's</p>
+ </li>
+ <li>
+ <p>
+ Commit artifacts you
have created with KEYS file to the
+
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
+ Proposed file structure
for "Release Candidate 1" of 3.1.0 will be:
+ </p>
+ <source>
3.1.0
3.1.0/rc1
3.1.0/rc1/src
@@ -150,7 +166,12 @@ svn copy -r1453158 https://svn.apache.or
3.1.0/rc1/bin/apache-openmeetings-3.1.0.tar.gz.asc
3.1.0/rc1/CHANGELOG
3.1.0/rc1/KEYS
- </source>
+ </source>
+ </li>
+ <li>Upload Artifacts with signatures
created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+ </ul>
</subsection>
<subsection name="Step2 - VOTE and RESULT emails">
@@ -245,31 +266,45 @@ for f in `ls -1 *.tar.gz *.zip`; do gpg
<subsection name="Step4 - Distribute and announce">
<p>If VOTEs positive: Upload the release </p>
- <p>Upload Artifacts with signatures created on
the previous steps to
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION</p>
- <p>
- Wait 24 hours (until all Apache mirrors
have synced the packages)
- and send an announcement to the mailing
list + blog and any other
- channel.
- </p>
- <p>
- Email announcements should have the
subject line:
- <br />
- [ANNOUNCE] Apache OpenMeetings x.xx
released
- </p>
- <p>
- Update release section of DOAP file
<tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
- </p>
- <p>
- Add a section to <a
href="downloads.html">downloads</a> website.<br />
- Make sure that the binary packages are
linked using the mirror URL as base path (
- <b>not</b>
http://www.apache.org/dist):<br />
- Mirror URL:
- <a
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
- </p>
- <p>
- Release candidates should be deleted
from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br/>
- Old releases should be deleted from
<tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
- </p>
+ <ul>
+ <li>Upload Artifacts with signatures
created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+ <li>Close staging repo:
+ <ul>
+ <li>Go to: <a
href="https://repository.apache.org/#stagingRepositories";>Staging
Repositories</a></li>
+ <li>Select openmeetings
staging repo and Close it with valid message:<br/>
+ for ex. "The
VOTE about 3.1.2 release was successful"
+ </li>
+ <li>Select openmeetings
staging repo and Release it with valid message:<br/>
+ for ex. "The
VOTE about 3.1.2 release was successful"
+ </li>
+ </ul>
+ </li>
+ <li>
+ Wait 24 hours (until all Apache
mirrors have synced the packages)
+ and send an announcement to the
mailing list + blog and any other
+ channel.
+ </li>
+ <li>
+ Email announcements should have
the subject line:<br />
+ [ANNOUNCE] Apache OpenMeetings
x.xx released
+ </li>
+ <li>
+ Update release section of DOAP
file <tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
+ </li>
+ <li>
+ Add a section to <a
href="downloads.html">downloads</a> website.<br />
+ Make sure that the binary
packages are linked using the mirror URL as base path (
+ <b>not</b>
http://www.apache.org/dist):<br />
+ Mirror URL:
+ <a
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
+ </li>
+ <li>
+ Release candidates should be
deleted from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br/>
+ Old releases should be deleted
from <tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
+ </li>
+ </ul>
</subsection>
</section>
</body>
Modified: openmeetings/application/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/trunk/pom.xml?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
--- openmeetings/application/trunk/pom.xml (original)
+++ openmeetings/application/trunk/pom.xml Mon Aug 15 03:14:09 2016
@@ -58,20 +58,26 @@
<tomcat.version>8.0.36</tomcat.version>
<derby.version>10.12.1.1</derby.version>
</properties>
- <modules>
- <module>openmeetings-util</module>
- <module>openmeetings-db</module>
- <module>openmeetings-core</module>
- <module>openmeetings-install</module>
- <module>openmeetings-service</module>
- <module>openmeetings-webservice</module>
- <module>openmeetings-web</module>
- <module>openmeetings-flash</module>
- <module>openmeetings-screenshare</module>
- <module>openmeetings-server</module>
- </modules>
<profiles>
<profile>
+ <id>AllModules</id>
+ <activation>
+ <activeByDefault>true</activeByDefault>
+ </activation>
+ <modules>
+ <module>openmeetings-util</module>
+ <module>openmeetings-db</module>
+ <module>openmeetings-core</module>
+ <module>openmeetings-install</module>
+ <module>openmeetings-service</module>
+ <module>openmeetings-webservice</module>
+ <module>openmeetings-web</module>
+ <module>openmeetings-flash</module>
+ <module>openmeetings-screenshare</module>
+ <module>openmeetings-server</module>
+ </modules>
+ </profile>
+ <profile>
<id>Quick</id>
<activation>
<property>
@@ -197,6 +203,13 @@
<jarsigner.skip>true</jarsigner.skip>
</properties>
</profile>
+ <profile>
+ <id>deploy</id>
+ <modules>
+ <module>openmeetings-util</module>
+ <module>openmeetings-db</module>
+ </modules>
+ </profile>
</profiles>
<url>http://openmeetings.apache.org</url>
<inceptionYear>2012</inceptionYear>
@@ -848,11 +861,6 @@
<version>1.8</version>
</plugin>
<plugin>
- <groupId>org.codehaus.mojo</groupId>
-
<artifactId>truezip-maven-plugin</artifactId>
- <version>1.2</version>
- </plugin>
- <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.6</version>
Modified: openmeetings/site/trunk/ReleaseGuide.html
URL:
http://svn.apache.org/viewvc/openmeetings/site/trunk/ReleaseGuide.html?rev=1756343&r1=1756342&r2=1756343&view=diff
==============================================================================
--- openmeetings/site/trunk/ReleaseGuide.html (original)
+++ openmeetings/site/trunk/ReleaseGuide.html Mon Aug 15 03:14:09 2016
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.7.1 at 2016-08-12
+ | Generated by Apache Maven Doxia Site Renderer 1.7.1 at 2016-08-15
| Rendered using Apache Maven Fluido Skin 1.5
-->
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
@@ -8,7 +8,7 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Apache OpenMeetings Team" />
- <meta name="Date-Revision-yyyymmdd" content="20160812" />
+ <meta name="Date-Revision-yyyymmdd" content="20160815" />
<meta http-equiv="Content-Language" content="en" />
<title>Apache OpenMeetings Project – Release Guide</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.5.min.css" />
@@ -42,7 +42,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2016-08-12
+ <li id="publishDate">Last Published: 2016-08-15
</li>
@@ -760,14 +760,11 @@
-
<div class="section">
<h2><a name="How_to_Build_a_Release_of_OpenMeetings"></a>How to Build a
Release of OpenMeetings</h2>
-
<div class="section">
<h3><a name="Required_tools"></a>Required tools</h3>
-
<div>
@@ -793,111 +790,153 @@
</li>
</ul>
</div>
-
</div>
-
<div class="section">
<h3><a name="Prepare_your_Apache_ID"></a>Prepare your Apache ID</h3>
-
<div>
- Every release package must be signed
with a PGP/GPG key.
- <br />
- So if you want to release a package
your Apache Id must be
- connected with a PGP key!
- <br />
- <br />
- You might follow:
- <br />
- <a class="externalLink"
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
- </a>
- <br />
- <br />
- In short:
- <br />
- Create PGP key pairs (private + public)
(and I recommend creating a
- Revoke Cert)
- <br />
- Upload the public key (either bei using
the PGP Tool that you use
- to create the key) or by using the web
form to:
- <a class="externalLink"
href="http://pgp.mit.edu/"; target="_blank" rel="nofollow">http://pgp.mit.edu/
- </a>
- <br />
- Add the fingerprint string (something
like "BF13 CF11 F9C9 0CBE
- 4413 09AB 0055 16BF 93A3 0395") to
your profile at
- <a class="externalLink"
href="https://id.apache.org/"; target="_blank"
rel="nofollow">https://id.apache.org/</a>
- <br />
- Wait for 6-8 hours, the server will
search for a public key based
- on your fingerprint, if success it will
create a file with your
- name at:
- <br />
- <a class="externalLink"
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
- <br />
- <br />
- If that is "success" then add
your key to:
- <br />
- <a class="externalLink"
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS
- </a>
- <br />
- and follow the instructions in the file.
- <br />
+
+<ul>
+
+<li><b>Every release package must be signed with a PGP/GPG key.</b><br />
+ So if you want to
release a package your Apache Id must be
+ connected with a PGP
key!
+ <br />
+ <br />
+ You might follow:
+ <br />
+ <a class="externalLink"
href="http://www.apache.org/dev/new-committers-guide.html#security-and-pgp";
target="_blank">http://www.apache.org/dev/new-committers-guide.html#security-and-pgp
+ </a>
+ <br />
+ <br />
+ In short:
+
+<ul>
+
+<li>Create PGP key pairs (private + public) (and I recommend creating a Revoke
Cert)</li>
+
+<li>Upload the public key (either bei using the PGP Tool that you use
+ to
create the key) or by using the web form to:
+ <a
class="externalLink" href="http://pgp.mit.edu/"; target="_blank"
rel="nofollow">http://pgp.mit.edu/</a>
+ </li>
+
+<li>Add the fingerprint string (something like "BF13 CF11 F9C9 0CBE
+ 4413
09AB 0055 16BF 93A3 0395") to your profile at
+ <a
class="externalLink" href="https://id.apache.org/"; target="_blank"
rel="nofollow">https://id.apache.org/</a>
+ </li>
+
+<li>
+ Wait
for 6-8 hours, the server will search for a public key based
+ on your
fingerprint, if success it will create a file with your
+ name at:
+ <br />
+ <a
class="externalLink"
href="https://people.apache.org/keys/committer/";>https://people.apache.org/keys/committer/</a>
+ </li>
+
+<li>
+ If that
is "success" then add your key to:
+ <br />
+ <a
class="externalLink"
href="https://svn.apache.org/repos/asf/openmeetings/project/KEYS";>https://svn.apache.org/repos/asf/openmeetings/project/KEYS</a>
+ <br />
+ <br />
+ and
follow the instructions in the file.
+ </li>
+ </ul>
+ </li>
+
+<li><b>Maven</b><br />
+
+<ul>
+
+<li>Ensure you able to login to <a class="externalLink"
href="https://repository.apache.org/";>https://repository.apache.org</a></li>
+
+<li>
+ Set up
development environment as described here: <a class="externalLink"
href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env";>Setup
development environment</a><br />
+ Don't
forget to secure passwords as described here: <a class="externalLink"
href="http://maven.apache.org/guides/mini/guide-encryption.html#How_to_create_a_master_password";>Password
Encryption</a>
+ </li>
+
+ </ul>
+ </li>
+ </ul>
</div>
-
</div>
-
<div class="section">
<h3><a name="Step1_-_Prepare_files"></a>Step1 - Prepare files</h3>
-<p>
- Check that all files:
- <br />
- LICENSE, NOTICE, DISCLAIMER, CHANGELOG,
README
- <br />
- are up to date and refer to the right
version.
- </p>
-
-
-<p>
- Create a TAG of the SVN tree that you
would like to release<br />
- Example:
- </p>
-
+<ul>
+
+<li>
+ Check that all files:<br />
+ LICENSE, NOTICE, DISCLAIMER,
CHANGELOG, README<br />
+ are up to date and refer to the
right version.
+ </li>
+
+<li>
+ Create a TAG of the SVN tree
that you would like to release<br />
+ Example:
+
<div class="source"><pre class="prettyprint">
svn copy -r1453158
https://svn.apache.org/repos/asf/openmeetings/application/trunk \
https://svn.apache.org/repos/asf/openmeetings/application/tags/3.1.0RC1
\
-m "3.1.0 Release candidate 1"
- </pre></div>
-
-
-
+ </pre></div>
+ </li>
+
+<li>
+
<p>Get the source from your TAG: </p>
-
+
<div class="source"><pre class="prettyprint">svn checkout
https://svn.apache.org/repos/asf/openmeetings/application/tags/$BRANCHORTAG/</pre></div>
-
+
<p>$BRANCHORTAG should be replaced with your new TAG</p>
-
-
+ </li>
+
+<li>
+
<p>Update versions of all modules</p>
-
+
<div class="source"><pre class="prettyprint">mvn versions:set
-DgenerateBackupPoms=false -DnewVersion=3.1.0</pre></div>
-
+ </li>
+
+<li>Deploy release artifacts to Maven
+
+<ul>
+
+<li>
+
+<div class="source"><pre class="prettyprint">
+mvn clean
+mvn deploy -Pdeploy,rc
+ </pre></div>
+ </li>
+ </ul>
+ </li>
+
+<li>
+
<p>Run the command: </p>
-
+
<div class="source"><pre class="prettyprint">mvn clean install -Prc</pre></div>
-
+ </li>
+
+<li>
+
<p>Test building the source on windows and OSx or Linux</p>
-
+
<p>Test running the binary's</p>
-
+ </li>
+
+<li>
+
<p>
- Commit artifacts you have created with
KEYS file to the
-
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
- Proposed file structure for
"Release Candidate 1" of 3.1.0 will be:
- </p>
-
+ Commit artifacts you
have created with KEYS file to the
+
<tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt>
+ Proposed file structure
for "Release Candidate 1" of 3.1.0 will be:
+ </p>
+
<div class="source"><pre class="prettyprint">
3.1.0
3.1.0/rc1
@@ -917,7 +956,13 @@ svn copy -r1453158 https://svn.apache.or
3.1.0/rc1/bin/apache-openmeetings-3.1.0.tar.gz.asc
3.1.0/rc1/CHANGELOG
3.1.0/rc1/KEYS
- </pre></div>
+ </pre></div>
+ </li>
+
+<li>Upload Artifacts with signatures created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+ </ul>
</div>
@@ -1046,36 +1091,56 @@ for f in `ls -1 *.tar.gz *.zip`; do gpg
<p>If VOTEs positive: Upload the release </p>
-<p>Upload Artifacts with signatures created on the previous steps to
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION</p>
-
-<p>
- Wait 24 hours (until all Apache mirrors
have synced the packages)
- and send an announcement to the mailing
list + blog and any other
- channel.
- </p>
-
-<p>
- Email announcements should have the
subject line:
- <br />
- [ANNOUNCE] Apache OpenMeetings x.xx
released
- </p>
-
-<p>
- Update release section of DOAP file
<tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
- </p>
-
-<p>
- Add a section to <a
href="downloads.html">downloads</a> website.<br />
- Make sure that the binary packages are
linked using the mirror URL as base path (
- <b>not</b>
http://www.apache.org/dist):<br />
- Mirror URL:
- <a class="externalLink"
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
- </p>
-
-<p>
- Release candidates should be deleted
from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br />
- Old releases should be deleted from
<tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
- </p>
+<ul>
+
+<li>Upload Artifacts with signatures created on the previous steps to
+
https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION
+ </li>
+
+<li>Close staging repo:
+
+<ul>
+
+<li>Go to: <a class="externalLink"
href="https://repository.apache.org/#stagingRepositories";>Staging
Repositories</a></li>
+
+<li>Select openmeetings staging repo and Close it with valid message:<br />
+ for ex.
"The VOTE about 3.1.2 release was successful"
+ </li>
+
+<li>Select openmeetings staging repo and Release it with valid message:<br />
+ for ex.
"The VOTE about 3.1.2 release was successful"
+ </li>
+ </ul>
+ </li>
+
+<li>
+ Wait 24 hours (until all Apache
mirrors have synced the packages)
+ and send an announcement to the
mailing list + blog and any other
+ channel.
+ </li>
+
+<li>
+ Email announcements should have
the subject line:<br />
+ [ANNOUNCE] Apache OpenMeetings
x.xx released
+ </li>
+
+<li>
+ Update release section of DOAP
file <tt>site/trunk/doap.rdf
(https://svn.apache.org/repos/asf/openmeetings/site/trunk/doap.rdf)</tt>
+ </li>
+
+<li>
+ Add a section to <a
href="downloads.html">downloads</a> website.<br />
+ Make sure that the binary
packages are linked using the mirror URL as base path (
+ <b>not</b>
http://www.apache.org/dist):<br />
+ Mirror URL:
+ <a class="externalLink"
href="http://www.apache.org/dyn/closer.lua/openmeetings/";>http://www.apache.org/dyn/closer.lua/openmeetings/</a>
+ </li>
+
+<li>
+ Release candidates should be
deleted from <tt>https://dist.apache.org/repos/dist/dev/openmeetings/</tt><br />
+ Old releases should be deleted
from <tt>https://dist.apache.org/repos/dist/release/openmeetings/</tt>
+ </li>
+ </ul>
</div>
</div>
