Author: dabbous
Date: 2006-12-16 01:15:44-0800
New Revision: 10390
Modified:
branches/release/b21/INSTALL
branches/release/b21/LICENSE
branches/release/b21/MIGRATION
branches/release/b21/README
Log:
some minor corrections to upgrade/installation descriptions
Modified: branches/release/b21/INSTALL
Url: http://scarab.tigris.org/source/browse/scarab/branches/release/b21/INSTALL?view=diff&rev=10390&p1=branches/release/b21/INSTALL&p2=branches/release/b21/INSTALL&r1=10389&r2=10390
==============================================================================
--- branches/release/b21/INSTALL (original)
+++ branches/release/b21/INSTALL 2006-12-16 01:15:44-0800
@@ -23,10 +23,15 @@
| MySQL | Full support for 4.0 and 4.1
| PostgreSQL | Full support (*)
| MS SQL Server | partial support [FIXME] what is partial support ?
- | Oracle | partial support [FIXME] what is partial support ?
+ | Oracle | broken
| Hypersonic | partial support [FIXME] what is partial support ?
+----------------+--------------------------------------------------
+Please check your security setting. you get some hint from the properties files
+project.properties, search the section "SETUP WIZARD" on that file!
+e.g. for MySQL the default settings assume database user root has no password
+set (which is highly insecure, but convenient for quick installation)
+
(*) See step 5a for more details.
,-----------------------------------------------------------------------.
@@ -63,21 +68,22 @@
2.) copy (not rename!) one of the following two files to build.properties:
- project.properties (full customization property set)
- minimal.properties (minimal customization property set)
+ 2a) minimal.properties (minimal customization property set)
+
+ minimal.properties is your best choice (believe us!). You will
+ be doing this in your command line shell (or dos-box):
+
+ cd $SCARAB_HOME
+ cp minimal.properties build.properties
- You will choose project.properties as your starting point, if you
- are a developer who is deeply involved into the Scarab development.
- In all other cases minimal.properties is your best choice (believe us!).
- So most of you will be doing this:
+ 2b) project.properties (full customization property set)
- cd $SCARAB_HOME
- cp minimal.properties build.properties
+ You will choose project.properties as your starting point, if you
+ are a developer who is deeply involved into the Scarab development.
3.) Scroll through your build.properties and be sure to follow the notes.
If you really miss a property which is not yet available in your
build.properties just add it to your build.properties!
-
,-----------------------------------------------------------------------.
| Step 4: Build Scarab
@@ -85,7 +91,7 @@
You have two choices to build Scarab:
-Maven build:
+4.1 Maven build:
1.) Enter the $SCARAB_ROOT directory
2.) call maven as follows:
@@ -100,7 +106,7 @@
it's possible that you see them fail in this step if your
database is not already configured. Look at the
-Ant build:
+4.2 Ant build:
1.) Enter the $SCARAB_ROOT/build directory
2.) call ant as follows:
@@ -161,8 +167,9 @@
*** End ***
-JIRA templates
---------------
+,-----------------------------------------------------------------------.
+| Step 5.b [OPTIONAL] JIRA templates |
+'-----------------------------------------------------------------------'
By default, a module is created with issue-types that match the
structure of JIRA, enabling transfer of issues from JIRA to Scarab.
@@ -178,16 +185,16 @@
This option is independent of 'skip.seed.data', so either or both may
be specified.
-
-
+
,-----------------------------------------------------------------------.
-| Step 5b: Migrate your current data |
+| Step 5c: Migrate your current data |
'-----------------------------------------------------------------------'
*** ONLY IF YOU ARE MIGRATING AN EXISTING INSTANCE OF SCARAB !! ***
Go to MIGRATION file for instructions on migrating your existing data.
+
,-----------------------------------------------------------------------.
| Step 6: [OPTIONAL] Run the tests |
'-----------------------------------------------------------------------'
@@ -206,10 +213,12 @@
1. maven clean (you better start from scratch if you gonna test)
2. Configure your build.properties to contain at least the correct
- scarab.database.type value.
+ scarab.database.type value.
3. maven war
- 4. maven scarab:create-db (make sure you choose the same database than
- before!!)
+ 4. maven scarab:create-db
+ Be sure, you do not unintentionally overwrite any production data
+ by double checking yur build.properties. Per default the database "scarab"
+ will be generated and a previous version of the datbase will be scratched!
5. maven test
,-----------------------------------------------------------------------.
@@ -222,7 +231,7 @@
On Unix/Linux, run the following shell script:
- $SCARAB_HOME/tomcat/bin/startup.sh'
+ $SCARAB_HOME/tomcat/bin/startup.sh
The webapplication will be available as reflected by the settings of the
Modified: branches/release/b21/LICENSE
Url: http://scarab.tigris.org/source/browse/scarab/branches/release/b21/LICENSE?view=diff&rev=10390&p1=branches/release/b21/LICENSE&p2=branches/release/b21/LICENSE&r1=10389&r2=10390
==============================================================================
--- branches/release/b21/LICENSE (original)
+++ branches/release/b21/LICENSE 2006-12-16 01:15:44-0800
@@ -1,6 +1,6 @@
The Scarab license can be found at
- htpp://scarab.tigris.org/LICENSE
+ http://scarab.tigris.org/LICENSE
A copy of the license can be found in the subfolder
Modified: branches/release/b21/MIGRATION
Url: http://scarab.tigris.org/source/browse/scarab/branches/release/b21/MIGRATION?view=diff&rev=10390&p1=branches/release/b21/MIGRATION&p2=branches/release/b21/MIGRATION&r1=10389&r2=10390
==============================================================================
--- branches/release/b21/MIGRATION (original)
+++ branches/release/b21/MIGRATION 2006-12-16 01:15:44-0800
@@ -4,7 +4,7 @@
This document outlines data migration between versions of Scarab.
It aplies only for already existing installations, which are upgrading
-to b21. If you are building a fresh repository, you don't need to
+to 0.21. If you are building a fresh repository, you don't need to
follow this document.
This document is organized from most recent version to old version.
@@ -19,28 +19,28 @@
CONTENTS OF THIS FILE
-1. Upgrading the database from b20 to b21
- 1.1 The quick step migration procedure
- 1.2 Details of the migration tasks
+1. Upgrading the database from b20 to 0.21
+ 1.1 The quick step migration procedure
+ 1.2 Details of the migration tasks
2. Migrating from older releases
- 2.1 Upgrading the database from b19 (and a20) to b20
- 2.1.1 The quick step migration procedure
- 2.1.2 Details of the migration tasks
- 2.1.3 Upgrading from a20-dev or b20-dev (with Conditions) to released a20
- 2.2 Upgrading from b18 and older versions
- 2.3 Upgrading from b15 to b16
- 2.4 Upgrading from b13 to b14
- 2.5 Upgrading from b13 -> cvs head -> b14
+ 2.1 Upgrading the database from b19 (and a20) to b20
+ 2.1.1 The quick step migration procedure
+ 2.1.2 Details of the migration tasks
+ 2.1.3 Upgrading from a20-dev or b20-dev (with Conditions) to released a20
+ 2.2 Upgrading from b18 and older versions
+ 2.3 Upgrading from b15 to b16
+ 2.4 Upgrading from b13 to b14
+ 2.5 Upgrading from b13 -> cvs head -> b14
,-----------------------------------------------------------------------.
-| 1. Upgrading the database from b20 to b21 |
+| 1. Upgrading the database from b20 to 0.21 |
'-----------------------------------------------------------------------'
,-----------------------------------------------------------------------.
| 1.1 The quick step migration procedure |
'-----------------------------------------------------------------------'
-0. We assume, you have already built the b21 web application
+0. We assume, you have already built the 0.21 web application
either with Ant or with Maven.
1. Change to the build/ directory of your generated web application.
@@ -51,7 +51,7 @@
2. REMEMBER: Not all the information is inside the database!
If you're migrating a running Scarab, you'll want to check
- that your attachments' directory and your search indexes are in their
+ that your attachments directory and your search indexes are in their
supposed place after migration.
You can use the "scarab.attachments.repository" property to get you files
@@ -59,6 +59,9 @@
It's also a good idea to recreate the search indexes after migrating
the system. Use 'Admin - Update search index' option in Scarab.
+ If you have intentionally or unintentionally scratched your index data
+ during migration, it will automatically rebuild upon forst start of
+ the webapp.
,-----------------------------------------------------------------------.
| 1.2 Details of the migration tasks |
Modified: branches/release/b21/README
Url: http://scarab.tigris.org/source/browse/scarab/branches/release/b21/README?view=diff&rev=10390&p1=branches/release/b21/README&p2=branches/release/b21/README&r1=10389&r2=10390
==============================================================================
--- branches/release/b21/README (original)
+++ branches/release/b21/README 2006-12-16 01:15:44-0800
@@ -8,18 +8,19 @@
For a quick installation guide use the file INSTALL in this
directory. Note, many relevant informations are only found in
-the installation guide (see next section).
+the installation guide in the documents section:
,-----------------------------------------------------------------------.
|Getting the installation guide |
'-----------------------------------------------------------------------'
-We highly recommend, that you read the online installation guide at
+We highly recommend, that you first read the installation guide in the
+documents section. You can find a ready made version at
http://scarab-gen.tigris.org/nonav/HEAD/howto/build-howto.html
-If you have Maven installed, you can alternatively generate the
-documentation set locally as follows:
+Alternatively you can generate the documentation set locally as follows.
+Note: you will need Maven installed on your box:
1.) Unpack the installation (you probably already did this)
2.) go to the installation root
@@ -27,7 +28,7 @@
maven xdoc:transform
-The documentation set will be generated to
+The full documentation set will be generated to
$SCARAB_ROOT/target/docs
@@ -41,21 +42,18 @@
It is best to always consult the issue tracking system at
- <http://scarab.tigris.org/issues.html>
+ http://www.solitone.org/scarab/issues
However, here are a couple of known issues that you should expect
things to not work or be difficult...
-#1. Oracle database creation to a fresh schema fails when ant tries
- to delete non-existent tables prior to creating them.
-
-#2. Oracle 8i support is broken. Oracle 9i should work fine.
-
-#3. You may still have some problems working with Oracle. Please let
- us know if you encounter anything, however, we don't promise to fix
- it right away unless you send real patches that conform to our
- desire to have transparent cross database support (ie: don't send us
- Oracle specific changes).
+#1. Oracle support is broken in this release.
+ You may try it out and help us fixing the problems related to the
+ oracle integration. Please let us know of any progress. Your help
+ will add significant value to Scarab. if you encounter anything,
+ however, we don't promise to fix it right away unless you send real
+ patches that conform to our desire to have transparent cross database
+ support (ie: don't send us Oracle specific changes).
#4. Microsoft SQL Server requires you to edit the SQL scripts after
generating them in the /target directory.
@@ -75,5 +73,5 @@
If you have problems or questions, please join the Scarab user mailing
list and post a detailed message describing your issue.
-Homepage: <http://scarab.tigris.org/>
-Mailing lists: <http://scarab.tigris.org/servlets/ProjectMailingListList>
+Homepage: http://scarab.tigris.org/
+Mailing lists: http://scarab.tigris.org/servlets/ProjectMailingListList
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.