Ok, I had to workaround some things:
1. Missing directories
mkdir framework/dist/example-proprietary
mkdir framework/dist/example
2. Wrong download locations:
connectors/alfresco/build.xml
87c87
< <get
src="https://artifacts.alfresco.com/nexus/service/local/repositories/releases/content/org/alfresco/alfresco-web-service-client/${alfresco-client.version}/alfresco-web-service-client-${alfresco-client.version}.jar";
dest="lib-proprietary"/>
---
> <get
src="https://artifacts.alfresco.com/nexus/service/local/repositories/releases/content/org/alfresco/alfresco-web-service-client/${alfresco-client.version}/alfresco-web-service-client-${alfresco-client.version}.jar";
dest="lib-proprietary/alfresco-web-service-client-${alfresco-client.version}.jar"/>
site/build.xml
266c266
< <get
src="http://downloads.sourceforge.net/project/dejavu/dejavu/2.33/dejavu-fonts-ttf-2.33.zip?r=&ts=1327734867&use_mirror=cdnetworks-us-2";
dest="fonts"/>
---
> <get
src="http://downloads.sourceforge.net/project/dejavu/dejavu/2.33/dejavu-fonts-ttf-2.33.zip?r=&ts=1327734867&use_mirror=cdnetworks-us-2";
dest="fonts/dejavu-fonts-ttf-2.33.zip"/>
279c279
< <get
src="http://jaist.dl.sourceforge.jp/ipafonts/51867/IPAGTTC00303.zip";
dest="fonts"/>
---
> <get
src="http://jaist.dl.sourceforge.jp/ipafonts/51867/IPAGTTC00303.zip";
dest="fonts/IPAGTTC00303.zip"/>
I need little time to configure and test the new version.
Frank
Am 11.03.2015 um 13:05 schrieb Frank Brendel:
Hi Karl,
I am trying to build ManifoldCF from trunk but it doesn't work when I
make 'ant make-deps'.
BUILD FAILED
/eurolog/software/mcf-trunk/build.xml:173: The following error
occurred while executing this line:
/eurolog/software/mcf-trunk/framework/build.xml:1586: Could not create
almost empty JAR archive
(/eurolog/software/mcf-trunk/framework/dist/example/start.jar (No such
file or directory))
Sorry if this is a dumb mistake but I am totally new in building java
applications from source.
Btw. the same error occurs with release-2.0.2.
Frank
Am 11.03.2015 um 12:36 schrieb Karl Wright:
Hi Frank,
See CONNECTORS-1171.
Karl
On Wed, Mar 11, 2015 at 7:29 AM, Frank Brendel
<[email protected] <mailto:[email protected]>> wrote:
Hi Karl,
unfortunately SharePoint doesn't provide a field 'url'.
And the problem persists even if I change the attribute name to,
lets say 'myurl'.
Frank
Am 11.03.2015 um 12:15 schrieb Karl Wright:
Ah, ok, so basically you are saying that the UI is broken. That
should be easy to confirm.
FWIW, there is already a metadata field from SharePoint called
"url". You can manipulate it by adding a Metadata Adjuster to
your job pipeline. So that might be a better way to do this.
Karl
On Wed, Mar 11, 2015 at 6:49 AM, Frank Brendel
<[email protected] <mailto:[email protected]>>
wrote:
Hi Karl,
after clicking on "Add Path Mapping" I'd expect either the
accepted mapping or an error message.
But I see only "No mappings specified".
I've set org.apache.manifoldcf.connectors to DEBUG and I see
lots of "SharePoint: List" but no "SharePoint: Path..."
entries as mentioned below.
Thanks
Frank
Am 11.03.2015 um 11:09 schrieb Karl Wright:
Hi Frank,
I am not sure what you mean by "nothing happens", but if
you turn on connector debugging, you will be able to see
what happens in the ManifoldCF log.
>>>>>>
// Add the path metadata item into the mix, if enabled
String pathAttributeName = sDesc.getPathAttributeName();
if (pathAttributeName != null &&
pathAttributeName.length() > 0)
{
if (Logging.connectors.isDebugEnabled())
Logging.connectors.debug("SharePoint: Path attribute name
is '"+pathAttributeName+"'");
String pathString =
sDesc.getPathAttributeValue(documentIdentifier);
if (Logging.connectors.isDebugEnabled())
Logging.connectors.debug("SharePoint: Path attribute value
is '"+pathString+"'");
data.addField(pathAttributeName,pathString);
}
else
Logging.connectors.debug("SharePoint: Path attribute name
is null");
<<<<<<
Thanks,
Karl
On Wed, Mar 11, 2015 at 5:25 AM, Frank Brendel
<[email protected]
<mailto:[email protected]>> wrote:
Hello,
I cannot add a path mapping to the SharePoint connector.
In the jobs metadata tab I've configured a metadata rule:
Path match: /*
Action: include
All metadata: true
Now I want a new attribute 'url' that contains the
complete URL to the SharePoint source and not only the
path.
Therefore I set the attribute name to 'url' and try to
add a path mapping
Match regexp: (.*)
Replace string: http:\/\/host:port$(1)
<http:%5C/%5C/host:port$%281%29>
But nothing happens. Why?
Thank you
Frank
