[ 
https://issues.apache.org/jira/browse/CONNECTORS-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052021#comment-15052021
 ] 

Karl Wright commented on CONNECTORS-1263:
-----------------------------------------

Yes, it fails for me now.  Did not fail over the weekend.  It looks like 
there's a path in the test that shouldn't be there:

{code}
    [junit] Caused by: org.h2.jdbc.JdbcSQLException: A file path that is implici
tly relative to the current working directory is not allowed in the database URL
 "jdbc:h2:/Users/mau/w/alf/alfresco-indexer/target/checkout/alf_data_dev/h2_data
/alf_dev;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=10000;MVCC=FALSE;L
OCK_MODE=0". Use an absolute path, ~/name, ./name, or the baseDir setting instea
d. [90011-185]
    [junit]     at org.h2.message.DbException.getJdbcSQLException(DbException.ja
va:345)
    [junit]     at org.h2.message.DbException.get(DbException.java:179)
    [junit]     at org.h2.message.DbException.get(DbException.java:155)
    [junit]     at org.h2.engine.ConnectionInfo.getName(ConnectionInfo.java:398)

    [junit]     at org.h2.engine.Engine.openSession(Engine.java:45)
    [junit]     at org.h2.engine.Engine.openSession(Engine.java:167)
    [junit]     at org.h2.engine.Engine.createSessionAndValidate(Engine.java:145
)
{code}


> Use alfresco-indexer-0.8.0(-SNAPSHOT)
> -------------------------------------
>
>                 Key: CONNECTORS-1263
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1263
>             Project: ManifoldCF
>          Issue Type: Task
>          Components: Alfresco webscript connector
>    Affects Versions: ManifoldCF 2.2
>            Reporter: Maurizio Pillitu
>
> Update alfresco-webscript connector to use alfresco-indexer-0.8.0
> Right now only 0.8.0-SNAPSHOT version is available on Maven Central; as soon 
> as Manifold trunk is tested against it, version 0.8.0 will be released (and 
> Manifold trunk will be updated to use the released version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to