[embjopr-commits] EMBJOPR SVN: r979 - trunk.
embjopr-commits at lists.jboss.org
embjopr-commits at lists.jboss.org
Tue Aug 17 18:18:44 EDT 2010
Author: ips
Date: 2010-08-17 18:18:43 -0400 (Tue, 17 Aug 2010)
New Revision: 979
Modified:
trunk/BUILD.txt
trunk/INSTALL.txt
Log:
update BUILD.txt and INSTALL.txt
Modified: trunk/BUILD.txt
===================================================================
--- trunk/BUILD.txt 2010-08-12 00:03:26 UTC (rev 978)
+++ trunk/BUILD.txt 2010-08-17 22:18:43 UTC (rev 979)
@@ -2,10 +2,10 @@
********************************
Compiling
=========
-1) Make sure you have JDK 5, a Subversion (SVN) client, and Maven 2 setup on
- your system.
+1) Make sure you have JDK 5 or 6, a Subversion (SVN) client, and Maven 2.1
+ or later setup on your system.
-2) Check out the Embedded Jopr source from SVN:
+2) Check out the Embedded Jopr source from JBoss SVN:
svn co http://anonsvn.jboss.org/repos/embjopr/trunk/ embjopr
@@ -20,11 +20,11 @@
This will produce three admin console WARs:
- * jbas4/target/jbas4-console.war
- - for deployment to JBoss AS 4.2.x or JBoss EAP 4.3.x
- * jbas5/target/jbas5-console.war
+ * jbas4/target/admin-console.war
+ - for deployment to JBoss AS 4.2.x or JBoss EAP 4.x
+ * jbas5/target/admin-console.war
- for deployment to JBoss AS 5.1.x or JBoss EAP 5.x
- * jbas6/target/jbas6-console.war
+ * jbas6/target/admin-console.war
- for deployment to JBoss AS 6.x
Installation
@@ -32,9 +32,9 @@
See INSTALL.txt in the embjopr root directory for instructions on installing
the admin console WAR to a JBAS instance and logging in to the admin console.
-NOTE: If you are deploying the admin console to EAP 5.x, you should remove the
- bundled admin-console.war from the deploy dir before installing your
- self-built admin console WAR.
+NOTE: If you are deploying the admin console to EAP 5.x or AS 6.x, you
+ should remove the bundled admin-console.war from the deploy dir before
+ installing your self-built admin console WAR.
NOTE: If you think you may want to activate the dev profile at some point, you
should deploy the admin console WAR in exploded form (i.e. as a
@@ -74,14 +74,20 @@
<profile>
<id>dev</id>
<properties>
- <!-- Set the below prop to the location to your dev JBAS 4.2/4.3
- deploy location for the admin console WAR.
- e.g.: C:/opt/jboss-eap-4.3.0.GA_CP02/jboss-as/server/production -->
+ <!-- Set the below prop to the location to your dev JBAS 4.2 deploy
+ location for the admin console WAR.
+ e.g.: C:/opt/jboss-4.2.2.GA/server/default -->
<jbas4.configDir>SET_ME</jbas4.configDir>
- <!-- Set the below prop to the location to your dev JBAS 5.0 deploy
- location for the embedded console WAR.
+
+ <!-- Set the below prop to the location to your dev JBAS 5.1 deploy
+ location for the admin console WAR.
e.g.: C:/opt/jboss-5.1.0.GA/server/default -->
<jbas5.configDir>SET_ME</jbas5.configDir>
+
+ <!-- Set the below prop to the location to your dev JBAS 6.x deploy
+ location for the admin console WAR.
+ e.g.: C:/opt/jboss-6.0.0.GA/server/default -->
+ <jbas6.configDir>SET_ME</jbas6.configDir>
</properties>
</profile>
@@ -89,3 +95,4 @@
"<activeProfile>dev</activeProfile>" to the "activeProfiles" section. If you
do not do this, you can always activate the dev profile for a particular mvn
run by including "-Pdev" on the mvn command line.
+
Modified: trunk/INSTALL.txt
===================================================================
--- trunk/INSTALL.txt 2010-08-12 00:03:26 UTC (rev 978)
+++ trunk/INSTALL.txt 2010-08-17 22:18:43 UTC (rev 979)
@@ -19,31 +19,37 @@
4) Stop your JBAS instance.
-5) Copy jbas4-console.war (JBAS 4.2.x/4.3.x) *or* jbas5-console.war (JBAS 5.x)
- to your ${JBOSS_CONFIG_DIR}/deploy/ directory.
+5) Copy the admin-console.war intended for the version of JBAS you are running:
+
+ * jbas4/target/admin-console.war
+ - for deployment to JBoss AS 4.2.x
+ * jbas5/target/admin-console.war
+ - for deployment to JBoss AS 5.1.x
+ * jbas6/target/admin-console.war
+ - for deployment to JBoss AS 6.x
+
+ to ${JBOSS_CONFIG_DIR}/deploy/.
-6) (AS5 ONLY) Enable the Profile Service.
- *NOTE* These instructions currently work for AS5 CR1, but not for CR2.
- a) In the ${JBOSS_CONFIG_DIR}/conf directory, delete the bootstrap.xml file and
- rename the bootstrap-repo.xml to bootstrap.xml.
- b) ***CR2 and earlier***: In ${JBOSS_CONFIG_DIR}/deployers directory, rename
- profileservice-beans.xml.bak file to profileservice-beans.xml.
- or
- ***post CR2***: In ${JBOSS_CONFIG_DIR}/deploy directory, rename
- profileservice-jboss-beans.xml.bak to profileservice-jboss-beans.xml.
-
-7) Restart your JBAS instance.
+6) Restart your JBAS instance.
-8) Once JBAS fully starts, go to http://localhost:8080/jbas4-console/ (JBAS 4.2.x/4.3.x)
- *or* http://localhost:8080/jbas5-console/ (JBAS 5.x). Login with the same credentials
- you would use for the JMX console (e.g. admin:admin).
+7) Once JBAS fully starts, go to http://localhost:8080/admin-console/.
+ Login with the same credentials you would use for the JMX console
+ (e.g. admin:admin).
Troubleshooting
***************
-Take a look at the following tips and if they don't help jump over to the forum: http://www.jboss.com/index.html?module=bb&op=viewforum&f=294
+Take a look at the following tips and, if they don't help, jump over to the
+Embedded Jopr discussion forum:
+
+ http://community.jboss.org/en/jbossas/embjopr?view=discussions
-1) Console not deploying
-The console has been designed to run in any configuration of JBAS4.2 which supports dpeloying Seam applications, if you can deploy one of the simple Seam apps described here:
+1) Admin console WAR not deploying
+The admin console webapp has been designed to run in any configuration of
+JBoss AS which supports deploying Seam applications, if you can deploy one
+of the simple Seam apps described here:
+
http://www.seamframework.org/Documentation/RunningSeamExamplesWithJBossApplicationServer42X
-you should be able to deploy the console.
\ No newline at end of file
+
+you should be able to deploy the admin console.
+
More information about the embjopr-commits
mailing list