Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Adding WAR assembly to package Roller as a custom WAR for each of the…

… three "app servers" we support

git-svn-id: https://svn.apache.org/repos/asf/roller/trunk@1052070 13f79535-47bb-0310-9956-ffa450edef68
  • Loading branch information...
commit 8bba57837377627667cc1393e4559b629377f387 1 parent 181cfca
David M. Johnson authored
View
43 README.txt
@@ -31,16 +31,17 @@ which includes OpenJPA buildcode enhancement, OpenJPA and other Java EE jars.
After pulling the source tree and changing directory to its top level, as
indicated above, the following command will build and run all unit tests:
- mvn install
+ mvn clean
+ mvn install
After doing that, you should find the newly built Roller webapp, suitable
for use with Tomcat in weblogger-web/target/roller.
To build Roller release files, you do this:
- cd weblogger-assembly
- mvn install
-
+ cd weblogger-assembly
+ mvn install
+
After that, you'll find Roller distribution files in weblogger-assembly/target.
The Tomcat specific release files will have 'for-tomcat' in their names.
@@ -55,15 +56,43 @@ If you leave those extra things out, Roller can run on most Java EE servers.
If you add a 'javaee' flag to the Roller build invocation, you can create
Roller release files that will work on a Java EE 6 app server.
- mvn -Djavaee=true install
- cd weblogger-assembly
- mvn install
+ mvn clean
+ mvn -Djavaee=true install
+
+ cd weblogger-war-assembly
+ mvn -Djavaee=true install
+
+ cd ../weblogger-assembly
+ mvn -Djavaee=true install
When that finishes, you will find Roller distribution files in
weblogger-assembly/target. The Java EE specific release files will have
'for-javaee' in their names.
+---------------------------
+BUILDING FOR JBOSS 6
+
+JBoss 6 is a Java EE server, but due to differences in JNDI naming, it needs
+a separate build.
+
+If you add a 'jboss' flag to the Roller build invocation, you can create
+Roller release files that will work on a JBoss 6 app server.
+
+ mvn clean
+ mvn -Djboss=true install
+
+ cd weblogger-war-assembly
+ mvn -Djboss=true install
+
+ cd ../weblogger-assembly
+ mvn -Djboss=true install
+
+When that finishes, you will find Roller distribution files in
+weblogger-assembly/target. The Java EE specific release files will have
+'for-jboss' in their names.
+
+
NOTE: If you wish to pull a branch other than the trunk, replace the word
"trunk" in both lines above with the appropriate branch name. Note that
versions of Roller before 5.0 have an ant-based build. In general, you should
View
6 build-javaee-release.sh
@@ -1,6 +1,12 @@
# How to build the Java EE release of Roller (Glassfish)
mvn clean
mvn -Djavaee=true install
+
+pushd weblogger-war-assembly
+mvn clean
+mvn -Djavaee=true install
+popd
+
pushd weblogger-assembly
mvn clean
mvn -Djavaee=true install
View
6 build-jboss-release.sh
@@ -1,6 +1,12 @@
# How to build the JBoss release of Roller
mvn clean
mvn -Djavaee=true -Djboss=true install
+
+pushd weblogger-war-assembly
+mvn clean
+mvn -Djboss=true install
+popd
+
pushd weblogger-assembly
mvn clean
mvn -Djboss=true install
View
6 build-tomcat-release.sh
@@ -1,6 +1,12 @@
# How to build a Tomcat release of Roller
mvn clean
mvn install
+
+pushd weblogger-war-assembly
+mvn clean
+mvn install
+popd
+
pushd weblogger-assembly
mvn clean
mvn install
View
4 pom.xml
@@ -8,7 +8,7 @@
<groupId>org.apache.roller</groupId>
<artifactId>roller-project</artifactId>
- <version>5.0.0-RC2</version>
+ <version>5.0.0-RC3</version>
<packaging>pom</packaging>
<name>Apache Roller Project</name>
@@ -27,7 +27,7 @@
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
- <roller.version>5.0.0-RC2</roller.version>
+ <roller.version>5.0.0-RC3</roller.version>
<!-- avoid CLOB/BLOB error in all later versions of Derby -->
<derby.version>10.1.3.1</derby.version>
</properties>
Please sign in to comment.
Something went wrong with that request. Please try again.