incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Lombart (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GRFT-29) Build failure with HSQLDB
Date Tue, 14 Jun 2005 19:17:50 GMT
     [ http://issues.apache.org/jira/browse/GRFT-29?page=all ]
     
Christophe Lombart closed GRFT-29:
----------------------------------

    Resolution: Fixed

Linked to issues GRFT-16. 

* All HSQL specific scripts has been added.
* Running Graffito with HSQL required HSQL version 1.8


> Build failure with HSQLDB
> -------------------------
>
>          Key: GRFT-29
>          URL: http://issues.apache.org/jira/browse/GRFT-29
>      Project: Graffito
>         Type: Bug
>   Components: Project Build
>     Versions: 1.0-a1-dev
>  Environment: HSQLDB, JDK 1.4.2, Maven 1.0.2
>     Reporter: Martin Maisey
>     Assignee: Christophe Lombart

>
> I attempted to build Maven as per http://incubator.apache.org/graffito/getting-started.html,
and used HSQLDB as a quick and easy option that the getting started instructions say is supported.
So I have  
> org.apache.portals.graffito.test.database.default.name=hsql
> in my build.properties.
> However, the build fails with
> BUILD FAILED
> File...... C:\cygwin\home\martin.maisey\graffito\maven.xml
> Element... maven:reactor
> Line...... 77
> Column.... 40
> Unable to obtain goal [test:test] -- C:\cygwin\home\martin.maisey\graffito\components\maven.xml:97:33:
<sql> Source file does not exist!
> The problem appears to be that the file referenced in the database.arg.script parameter
set at line 267 in the maven.xml file mentioned does not exist. This is defined as
> ./src/sql/GraffitoServer/${org.apache.portals.graffito.database.default.name}/drop-db.sql
> Looking at Subversion, this appears to be a manually created file, and there is no file
src/sql/GraffitoServer/hsql/drop-db.sql in Subversion hence the error. In fact, the only database
these files are present for is MySQL. I'm moving to MySQL now as a workaround, but raising
the issue as it might be a good idea to  either 
> * Update the 'Getting Started' page to indicate that the other databases aren't currently
supported, or 
> * Check in the relevant SQL files
> This may be related to GRFT-4 but really is related to the Getting Started page, which
seems to be a bit misleading at the moment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message