manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (Commented) (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
Date Wed, 07 Dec 2011 14:48:40 GMT


Karl Wright commented on CONNECTORS-308:

Some research on the alfresco.war 3.4.d community edition:  It is not downloadable without
considerable work.  It's embedded in a zip file that can only be downloaded from a server
protected by basic auth, whose credentials are supplied in Javascript in encoded form.  It's
under web-server/webapps in this zip.

I'd therefore recommend that we put the onus on the user to supply this war file in order
for the integration tests to run.  Any objection to this approach?

I'm not really sure what the Maven implications would be either, but clearly the current approach
of building the war ourselves using Alfresco materials is certainly a concern.
> "ant test" fails due to Alfresco test problem
> ---------------------------------------------
>                 Key: CONNECTORS-308
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Alfresco connector
>    Affects Versions: ManifoldCF 0.4
>         Environment: Windows (although this shouldn't matter)
>            Reporter: Karl Wright
>            Assignee: Piergiorgio Lucidi
>             Fix For: ManifoldCF 0.4
> I get this error when I do "ant test":
> {code}
> ...
> setup-alfresco-connector-tests:
>      [copy] Copying 6 files to C:\wip\mcf\trunk\connectors\alfresco\lib
> C:\wip\mcf\trunk\build.xml:316: The following error occurred while executing this line:
> C:\wip\mcf\trunk\tests\alfresco-war\build.xml:25: The following error occurred while
executing this line:
> C:\wip\mcf\trunk\tests\alfresco-war\tools\ant\tasks\tomcat-tasks.xml:30: C:\wip\mcf\trunk\${appserver.dir}\server\lib
does not exist.
> Total time: 18 seconds
> C:\wip\mcf\trunk>
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message