Re: Delivery of source of integration packages for 0.4-incubating
I haven't heard back from Mr. Malcolm on this issue as yet, so I think it's time to consider how to move it out of Apache's svn to some other place. Initially I thought I'd just svn export it (complete with LICENSE and NOTICE and README), but then I realized there may be copyright issues since it is currently called "Apache ManifoldCF Meridio Plugin". Questions: (1) Is it a problem to move it to Google Code with no name changes? (2) If I have to change the name, I could use either: "Meridio Plugin For Apache ManifoldCF" or "ManifoldCF Meridio Plugin" Which is better in your opinion? Karl On Fri, Dec 9, 2011 at 10:44 AM, Jukka Zitting wrote: > Hi, > > On Fri, Dec 9, 2011 at 3:14 PM, Karl Wright wrote: >> Essentially, this is a relatively minor piece of the whole Meridio >> connector puzzle. In my view it would be unfortunate to discard the >> rest of the puzzle because we did not have source for that one piece. >> If Apache found that problematic, it could easily be checked in under >> googlecode or some such, with a reference. What is Apache's position >> regarding that kind of solution? > > IIUC we're talking about an extra service that needs to be installed > along with the Meridio server being accessed. > > We could treat that as a system dependency just like we treat Meridio > itself. The only problem then would be for end users who want to use > the connector to figure out the licensing terms under which they can > use this extra component. > > Since we can't distribute it from Apache, it needs to be made > available from somewhere else preferably with good enough licensing > documentation. ManifoldCF can then point to that location from the > connector documentation. > > BR, > > Jukka Zitting
Re: Is ManifoldCF OSI certified?
Glassfish is OK to redistribute; we already have two such jars under redistribution: Directory of C:\wip\mcf\trunk\lib 02/27/2011 08:49 AM 1,026,818 jsp-2.1-glassfish-2.1.v20091210.jar 02/27/2011 08:49 AM 135,424 jsp-api-2.1-glassfish-2.1.v20091210.jar This is what was recorded in the license file for those: This product includes JSP API jars. License: Common Development and Distribution License (CDDL) v1.0 (https://glassfish.dev.java.net/public/CDDLv1.0.html) Karl On Mon, Dec 12, 2011 at 11:19 PM, Karl Wright wrote: > Hi, > > ManifoldCF is Apache licensed. Apache projects cannot redistribute > GPL jars, but that is not a problem, because we probably do not need > to. What we usually do in such cases is download the dependencies at > build time, either automatically through the maven build, or by using > the "ant download-dependencies" target. For JDBC drivers that are > used by the core database layers, luckily they are loaded via > reflection so that lack of a driver will not prevent the build from > completing, although the user will need to download the driver and > build if they intend to use that driver. > > The standard tag library stuff is more problematic it that does not > have redistribution license acceptable for Apache, but I believe the > glassfish stuff is acceptable. I will verify and get back to you. > > The i18n issues, as I said before, are not trivial, and may well > require several iterations to get right. Tab names are just one > aspect of it. This is one reason I wanted to separate any i18n > contribution from the database contribution. > > Thanks, > Karl > > > 2011/12/12 Hitoshi Ozawa : >> Hi, >> I'm checking on the MySQL licenses and it seems MySQL Connector/J is GPL >> v2 license with >> exception clause for FOSS. >> http://www.mysql.com/about/legal/licensing/foss-exception/ >> >> To be classified as FOSS, however, it seems the software has to be OSI >> certified. >> Is Apache ManifoldCF OSI Certified? >> >> "This software is OSI Certified Open Source Software. >> OSI Certified is a certification mark of the Open Source Initiative." >> >> Does somebody know the license to JSTL libraries? I can't find any >> license in the jstl-api-1.2.jar >> and jstl-impl-1.2.jar files. The files are download-able from Oracle's >> GlassFish project page but >> there's not license page. >> >> BTW, I just created a Java message class to read String from properties >> file. Seems you've >> hard-coded tab names into the Java source files, which means I have to >> I18N all references to tab >> names or it won't work. >> >> Regards, >> H.Ozawa >>
Re: Is ManifoldCF OSI certified?
Hi, ManifoldCF is Apache licensed. Apache projects cannot redistribute GPL jars, but that is not a problem, because we probably do not need to. What we usually do in such cases is download the dependencies at build time, either automatically through the maven build, or by using the "ant download-dependencies" target. For JDBC drivers that are used by the core database layers, luckily they are loaded via reflection so that lack of a driver will not prevent the build from completing, although the user will need to download the driver and build if they intend to use that driver. The standard tag library stuff is more problematic it that does not have redistribution license acceptable for Apache, but I believe the glassfish stuff is acceptable. I will verify and get back to you. The i18n issues, as I said before, are not trivial, and may well require several iterations to get right. Tab names are just one aspect of it. This is one reason I wanted to separate any i18n contribution from the database contribution. Thanks, Karl 2011/12/12 Hitoshi Ozawa : > Hi, > I'm checking on the MySQL licenses and it seems MySQL Connector/J is GPL > v2 license with > exception clause for FOSS. > http://www.mysql.com/about/legal/licensing/foss-exception/ > > To be classified as FOSS, however, it seems the software has to be OSI > certified. > Is Apache ManifoldCF OSI Certified? > > "This software is OSI Certified Open Source Software. > OSI Certified is a certification mark of the Open Source Initiative." > > Does somebody know the license to JSTL libraries? I can't find any > license in the jstl-api-1.2.jar > and jstl-impl-1.2.jar files. The files are download-able from Oracle's > GlassFish project page but > there's not license page. > > BTW, I just created a Java message class to read String from properties > file. Seems you've > hard-coded tab names into the Java source files, which means I have to > I18N all references to tab > names or it won't work. > > Regards, > H.Ozawa >
Is ManifoldCF OSI certified?
Hi, I'm checking on the MySQL licenses and it seems MySQL Connector/J is GPL v2 license with exception clause for FOSS. http://www.mysql.com/about/legal/licensing/foss-exception/ To be classified as FOSS, however, it seems the software has to be OSI certified. Is Apache ManifoldCF OSI Certified? "This software is OSI Certified Open Source Software. OSI Certified is a certification mark of the Open Source Initiative." Does somebody know the license to JSTL libraries? I can't find any license in the jstl-api-1.2.jar and jstl-impl-1.2.jar files. The files are download-able from Oracle's GlassFish project page but there's not license page. BTW, I just created a Java message class to read String from properties file. Seems you've hard-coded tab names into the Java source files, which means I have to I18N all references to tab names or it won't work. Regards, H.Ozawa
[jira] [Assigned] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright reassigned CONNECTORS-308:
--
Assignee: Piergiorgio Lucidi (was: Karl Wright)
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> 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
>Priority: Blocker
> 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
> BUILD FAILED
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167849#comment-13167849
]
Karl Wright commented on CONNECTORS-308:
There seems to be no online reference for the error "11120001 Bootstrap
failed". I'm going to assign this back to Piergiorgio to figure out, at this
point.
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
> Environment: Windows (although this shouldn't matter)
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Blocker
> 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
> BUILD FAILED
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167842#comment-13167842
]
Karl Wright commented on CONNECTORS-308:
I'm still left with the following problem running the tests under ant:
{code}
[junit] 2011-12-12 16:51:05.690:INFO::Extract
../../connectors/alfresco/build/alfresco-war/alfresco.war to
C:\Users\Karl\AppData\Local\Temp\Jetty_0_0_0_0_9090_alfresco.war__alfresco__.rv4lqp\webapp
[junit] 2011-12-12 16:51:31.297:INFO:/alfresco:Initializing Spring root
WebApplicationContext
[junit] 2011-12-12 16:52:28.342:WARN::Failed startup of context
org.mortbay.jetty.webapp.WebAppContext@48c46b{/alfresco,../../connectors/alfresco/build/alfresco-war/alfresco.war}
[junit] org.alfresco.error.AlfrescoRuntimeException: 11120001 Bootstrap
failed
[junit] at
org.alfresco.repo.importer.ImporterBootstrap.bootstrap(ImporterBootstrap.java:361)
[junit] at
org.alfresco.repo.importer.ImporterBootstrap.onBootstrap(ImporterBootstrap.java:718)
[junit] at
org.springframework.extensions.surf.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:56)
[junit] at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
[junit] at
org.alfresco.repo.management.SafeApplicationEventMulticaster.multicastEvent(SafeApplicationEventMulticaster.java:78)
[junit] at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:294)
[junit] at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:858)
[junit] at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:419)
[junit] at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
[junit] at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:192)
[junit] at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
[junit] at org.alfresco.web.app.ContextLoaderListener.contextInitialized
{code}
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
> Environment: Windows (although this shouldn't matter)
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Blocker
> 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
> BUILD FAILED
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167840#comment-13167840
]
Karl Wright commented on CONNECTORS-308:
r1213456 to fix more issues.
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
> Environment: Windows (although this shouldn't matter)
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Blocker
> 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
> BUILD FAILED
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Incubator PMC/Board report for Dec 2011 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/December2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[jira] [Commented] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167456#comment-13167456
]
Karl Wright commented on CONNECTORS-308:
r1213193 to fix the latest problem.
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
> Environment: Windows (although this shouldn't matter)
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Blocker
> 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
> BUILD FAILED
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167453#comment-13167453
]
Karl Wright commented on CONNECTORS-308:
I got past the broken maven build and managed to get an alfresco.war. However,
the ant tests fail still, apparently because there is a missing dependency in
the ant test run:
{code}
compile-alfresco-tests:
[mkdir] Created dir: C:\wip\mcf\trunk\build\alfresco-tests\classes
[javac] C:\wip\mcf\trunk\build.xml:2298: warning: 'includeantruntime' was no
t set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 2 source files to C:\wip\mcf\trunk\build\alfresco-tests\cl
asses
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:25: package org.alfresco.webservice.content does
not exist
[javac] import org.alfresco.webservice.content.ContentServiceSoapBindingStub
;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:26: package org.alfresco.webservice.repository d
oes not exist
[javac] import org.alfresco.webservice.repository.QueryResult;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:27: package org.alfresco.webservice.repository d
oes not exist
[javac] import org.alfresco.webservice.repository.RepositoryFault;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:28: package org.alfresco.webservice.repository d
oes not exist
[javac] import org.alfresco.webservice.repository.RepositoryServiceSoapBindi
ngStub;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:29: package org.alfresco.webservice.repository d
oes not exist
[javac] import org.alfresco.webservice.repository.UpdateResult;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:30: package org.alfresco.webservice.types does n
ot exist
[javac] import org.alfresco.webservice.types.CML;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:31: package org.alfresco.webservice.types does n
ot exist
[javac] import org.alfresco.webservice.types.CMLCreate;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:32: package org.alfresco.webservice.types does n
ot exist
[javac] import org.alfresco.webservice.types.CMLDelete;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:33: package org.alfresco.webservice.types does n
ot exist
[javac] import org.alfresco.webservice.types.ContentFormat;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:34: package org.alfresco.webservice.types does n
ot exist
[javac] import org.alfresco.webservice.types.NamedValue;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
alfresco_tests\APISanityIT.java:35: package org.alfresco.webservice.types does n
ot exist
[javac] import org.alfresco.webservice.types.ParentReference;
[javac] ^
[javac] C:\wip\mcf\trunk\tests\alfresco\src\test\java\org\apache\manifoldcf\
...
{code}
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
> Environment: Windows (although this shouldn't matter)
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Blocker
> 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
> BUILD FAILED
> C:\wip\mcf\trunk\build.xml:316: The following error occurred while executing
> this line:
> C:\wip\mcf\trunk\tests\alfresco-war\build.xm
[jira] [Commented] (CONNECTORS-310) Maven build of Alfresco connector fails
[
https://issues.apache.org/jira/browse/CONNECTORS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167449#comment-13167449
]
Karl Wright commented on CONNECTORS-310:
r1213187 to disable maven build of alfresco connector
> Maven build of Alfresco connector fails
> ---
>
> Key: CONNECTORS-310
> URL: https://issues.apache.org/jira/browse/CONNECTORS-310
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector, Build
>Affects Versions: ManifoldCF 0.4
>Reporter: Karl Wright
>Assignee: Piergiorgio Lucidi
>Priority: Blocker
> Fix For: ManifoldCF 0.4
>
>
> When I try "mvn clean install" on trunk, I get the following error:
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ManifoldCF SUCCESS [0.752s]
> [INFO] ManifoldCF - Framework SUCCESS [0.099s]
> [INFO] ManifoldCF - Framework - Core . SUCCESS [3.788s]
> [INFO] ManifoldCF - Framework - UI Core .. SUCCESS [1.327s]
> [INFO] ManifoldCF - Framework - Agents ... SUCCESS [12.891s]
> [INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [19.641s]
> [INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.089s]
> [INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.209s]
> [INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.296s]
> [INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.148s]
> [INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [5.093s]
> [INFO] ManifoldCF - Framework - Script Engine SUCCESS [6.514s]
> [INFO] ManifoldCF - Connectors ... SUCCESS [0.075s]
> [INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.702s]
> [INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [12.696s]
> [INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.450s]
> [INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [1.638s]
> [INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.560s]
> [INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.332s]
> [INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.027s]
> [INFO] ManifoldCF - Connectors - RSS . SUCCESS [2.727s]
> [INFO] ManifoldCF - Connectors - Solr SUCCESS [1.474s]
> [INFO] ManifoldCF - Connectors - Web . SUCCESS [3.440s]
> [INFO] ManifoldCF - Connectors - CMIS SUCCESS [16.662s]
> [INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [2.050s]
> [INFO] ManifoldCF - Connectors - Wiki SUCCESS [12.567s]
> [INFO] ManifoldCF - Connectors - Alfresco FAILURE [2:15.432s]
> [INFO] ManifoldCF - Test materials ... SKIPPED
> [INFO] ManifoldCF - Test Materials - Alfresco WAR SKIPPED
> [INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
> [INFO] ManifoldCF - Tests SKIPPED
> [INFO] ManifoldCF - Test - Alfresco .. SKIPPED
> [INFO] ManifoldCF - Test - Wiki .. SKIPPED
> [INFO] ManifoldCF - Test - CMIS .. SKIPPED
> [INFO] ManifoldCF - Test - Filesystem SKIPPED
> [INFO] ManifoldCF - Test - Sharepoint SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4:15.090s
> [INFO] Finished at: Thu Dec 08 03:43:10 EST 2011
> [INFO] Final Memory: 72M/181M
> [INFO]
>
> [ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
> reso
> lve dependencies for project
> org.apache.manifoldcf:mcf-alfresco-connector:jar:0.
> 4.0-SNAPSHOT: The following artifacts could not be resolved:
> org.opensaml:opensa
> ml:jar:1.0.1, bouncycastle:bcprov-jdk15:jar:137,
> xml-security:xmlsec:jar:1.4.1:
> Could not find artifact org.opensaml:opensaml:jar:1.0.1 in alfresco-public
> (http
> ://maven.alfresco.com/nexus/content/groups/public) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> swit
> ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> rea
> d the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/co
[jira] [Commented] (CONNECTORS-310) Maven build of Alfresco connector fails
[
https://issues.apache.org/jira/browse/CONNECTORS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167445#comment-13167445
]
Karl Wright commented on CONNECTORS-310:
Since this is blocking the ability of people to build with Maven, until this is
worked out I'm going to disable the alfresco part of the maven build and tests.
We can re-enable them when we've got a solution.
> Maven build of Alfresco connector fails
> ---
>
> Key: CONNECTORS-310
> URL: https://issues.apache.org/jira/browse/CONNECTORS-310
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector, Build
>Affects Versions: ManifoldCF 0.4
>Reporter: Karl Wright
>Assignee: Piergiorgio Lucidi
>Priority: Blocker
> Fix For: ManifoldCF 0.4
>
>
> When I try "mvn clean install" on trunk, I get the following error:
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ManifoldCF SUCCESS [0.752s]
> [INFO] ManifoldCF - Framework SUCCESS [0.099s]
> [INFO] ManifoldCF - Framework - Core . SUCCESS [3.788s]
> [INFO] ManifoldCF - Framework - UI Core .. SUCCESS [1.327s]
> [INFO] ManifoldCF - Framework - Agents ... SUCCESS [12.891s]
> [INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [19.641s]
> [INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.089s]
> [INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.209s]
> [INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.296s]
> [INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.148s]
> [INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [5.093s]
> [INFO] ManifoldCF - Framework - Script Engine SUCCESS [6.514s]
> [INFO] ManifoldCF - Connectors ... SUCCESS [0.075s]
> [INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.702s]
> [INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [12.696s]
> [INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.450s]
> [INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [1.638s]
> [INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.560s]
> [INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.332s]
> [INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.027s]
> [INFO] ManifoldCF - Connectors - RSS . SUCCESS [2.727s]
> [INFO] ManifoldCF - Connectors - Solr SUCCESS [1.474s]
> [INFO] ManifoldCF - Connectors - Web . SUCCESS [3.440s]
> [INFO] ManifoldCF - Connectors - CMIS SUCCESS [16.662s]
> [INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [2.050s]
> [INFO] ManifoldCF - Connectors - Wiki SUCCESS [12.567s]
> [INFO] ManifoldCF - Connectors - Alfresco FAILURE [2:15.432s]
> [INFO] ManifoldCF - Test materials ... SKIPPED
> [INFO] ManifoldCF - Test Materials - Alfresco WAR SKIPPED
> [INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
> [INFO] ManifoldCF - Tests SKIPPED
> [INFO] ManifoldCF - Test - Alfresco .. SKIPPED
> [INFO] ManifoldCF - Test - Wiki .. SKIPPED
> [INFO] ManifoldCF - Test - CMIS .. SKIPPED
> [INFO] ManifoldCF - Test - Filesystem SKIPPED
> [INFO] ManifoldCF - Test - Sharepoint SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4:15.090s
> [INFO] Finished at: Thu Dec 08 03:43:10 EST 2011
> [INFO] Final Memory: 72M/181M
> [INFO]
>
> [ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
> reso
> lve dependencies for project
> org.apache.manifoldcf:mcf-alfresco-connector:jar:0.
> 4.0-SNAPSHOT: The following artifacts could not be resolved:
> org.opensaml:opensa
> ml:jar:1.0.1, bouncycastle:bcprov-jdk15:jar:137,
> xml-security:xmlsec:jar:1.4.1:
> Could not find artifact org.opensaml:opensaml:jar:1.0.1 in alfresco-public
> (http
> ://maven.alfresco.com/nexus/content/groups/public) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> swit
> ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [E
[jira] [Commented] (CONNECTORS-275) Clarify documentation as to how to set up session login for web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167439#comment-13167439 ] Karl Wright commented on CONNECTORS-275: Would you like to create a new ticket to cover changes to the Web Connector itself, as we've discussed above? I think this ticket basically covers documentation only. Once you've decided what you need then I think we'd want a new ticket that is specific for those code changes. > Clarify documentation as to how to set up session login for web connector > - > > Key: CONNECTORS-275 > URL: https://issues.apache.org/jira/browse/CONNECTORS-275 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation, Web connector >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright > Attachments: CONNECTORS-275.patch > > > A book reader has this comment, which basically implies that we need to > improve the documentation for the web connector: > "I was excited to get the full version of the online book, but then > disappointed when it referred back to the online doc for setting up logins > for a Web spidering. The online doc is very vague and only gives one example. > I've used Ultraseek's and Google's spider, but I still find the Session login > sequences non-obvious. > I've got a subscription request into the user mailing list, but here's the > parts that are not clear. > I generally understand about using regexes to define sites and sorting out > content pages from login pages. > But it's not clear why there's TWO Regex's per entry. There's a "Login URL" > regex, and also a "Form name/link target" regex. > It's also not clear about the "page type" radio button choices. > For "rediection", am I saying "look for a redirect event", or am I saying > "then DO a redirect to this page". > And for "form name", what if my login page doesn't have a named form? In the > case of the site I'm trying to spider, when your session expires, you > manually go back to an https page and supply your username and password as > CGI parameters. I know this sounds odd, but it's apparently how a number of > the sites we're trying to spider work, some proprietary software. > Karl, I really think the book or Wiki or doc needs 3 or 4 different examples > of login scenarios. > Here's the scenario I'm trying, if you'd like to use it: > Try to fetch: http://site.com/product?id=1234 > If you get a redirect to: http://site.com/Main.asp > Note that there's no login form nor link on this page. > Then invoke this login URL: > https://site.com/validate?username=me&password=that&otherArg=something > Note that you can't just visit this page and fill in a form, that gives an > error, it has to be passed in (I think as a GET) > Then record the session cookie and try for /product?id=1234 again. > I realize this is odd, I didn't design it. " -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167424#comment-13167424 ] Karl Wright commented on CONNECTORS-313: Since this work is likely to need some refinement over time, I've created a branch to work on it in. Svn url: https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-313 Please go ahead and commit all of your changes to it, and we will get it right there before we finally commit to trunk. Thanks! > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167421#comment-13167421 ] Karl Wright edited comment on CONNECTORS-313 at 12/12/11 9:17 AM: -- Hi Abe-san, connectors.xml is read by the QuickStart java startup class only at this time. You have two choices: (1) Modify the main build.xml to dynamically build your register.sh script, in a manner similar to the way it dynamically builds connectors.xml; (2) Create a new command class in framework/pull-agent/src/main/java/org/apache/manifoldcf/crawler, which parses a connectors.xml and performs the corresponding modification (and nothing else), and then call that command class from your script. You may be able to move the code for this from framework/jettyrunner, and change the jettyrunner code so it is not duplicated. I'm not sure which is better. It depends on how people typically deploy the multiprocess version. was (Author: kwri...@metacarta.com): Hi Abe-san, connectors.xml is read by the QuickStart java startup class only at this time. You have two choices: (1) Modify the main build.xml to dynamically build your register.sh script, in a manner similar to the way it dynamically builds connectors.xml; (2) Create a new command class in framework/pull-agent/src/main/java/org/apache/manifoldcf/crawler, which parses a connectors.xml and performs the corresponding modification (and nothing else). You may be able to move the code for this from framework/jettyrunner, and change the jettyrunner code so it is not duplicated. I'm not sure which is better. It depends on how people typically deploy the multiprocess version. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167421#comment-13167421 ] Karl Wright commented on CONNECTORS-313: Hi Abe-san, connectors.xml is read by the QuickStart java startup class only at this time. You have two choices: (1) Modify the main build.xml to dynamically build your register.sh script, in a manner similar to the way it dynamically builds connectors.xml; (2) Create a new command class in framework/pull-agent/src/main/java/org/apache/manifoldcf/crawler, which parses a connectors.xml and performs the corresponding modification (and nothing else). You may be able to move the code for this from framework/jettyrunner, and change the jettyrunner code so it is not duplicated. I'm not sure which is better. It depends on how people typically deploy the multiprocess version. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: register-draft.sh About register script, sorry, I don't know how to read from connectors.xml. How can this script read xml? > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: (was: CONNECTOR-313.patch) > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: CONNECTOR-313.patch > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-313: -- Attachment: CONNECTOR-313.patch properties.xml is placed at dist folder in this patch. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
