Hi Christophe,
I had two properties set to false in my build.properties:
org.apache.portals.graffito.test.jetspeed
org.apache.portals.graffito.production.jetspeed
After changing them to true (as clearly stated on the build instructions
page) I had a successful build and deploy.
Thanks,
Salvio
Christophe Lombart wrote:
I'm also using InnoDB. Before executing the allClean & allBuild goals,
did clean-up the DB used for the Graffito test ?
I made some refactoring that maybe cause the problem.
note: I just commited something but this is a bug fix for deploying
Graffito into Jetspeed.
On 1/30/06, Salvio <[EMAIL PROTECTED]> wrote:
Hi All,
I'm having the same problem seen in this thread:
http://www.mail-archive.com/[email protected]/msg00279.html
What I have done is:
1. upgraded mysql to 4.1.16
2. downloaded and installed jetspeed2 multi db using
3. checked out the trunk of graffito
4. run a maven allClean allBuild using the attached build properties
I get this error message:
db.create:
db.execute:
[echo] Execute SQL script :
./target/src/sql/mysql/security-schema.sql -- ON ERROR = abort
[sql] Executing file:
C:\graffito\x\target\checkout\components\target\src\sql\mysql\security-schema.sql
[sql] [ERROR] Failed to execute: #
-----------------------------------------------------------------------
# SECURITY_PRINCIPAL #
-----------------------------------------------------------------------
drop table if exists SECURITY_PRINCIPAL
BUILD FAILED
File...... C:\graffito\x\target\checkout\maven.xml
Element... maven:reactor
Line...... 88
Column.... 40
Unable to obtain goal [test:test] --
C:\graffito\x\target\checkout\components\maven.xml:286:38: <sql>
java.sql.SQLException: Cannot delete or update a parent row: a foreign
key constraint fails
I have also tried using BDB instead of the default INNODB and in this
case the build and deploy complete successfully.
To complete the installation though I need to re-populate the following
tables with the original data (before deploying graffito) and then run
insert-j2-security.sql again. The tables are: principal_permission,
security_credential, security_permission, security_principal,
security_user_group, security_user_role.
- Salvio
--
Best regards,
Christophe
