Re: ant build scripts done; should be possible for others to build now
Shalin Shekhar Mangar wrote: On Wed, Feb 17, 2010 at 2:28 AM, Karl Wright kwri...@metacarta.com wrote: I've set it up so there's a master build script under modules, which fires off individual module build scripts as specified. If you haven't installed required client libraries for any given connector, it should simply skip that one. I've also checked in properly versions of all jars that can legally redistributed by apache; we may well want to change how that's done, but since upstream modifications are needed on a few of them, that seemed like the fastest way to get going. Thanks Karl! I'm able to run ant all successfully. There are just a few warnings due to Java 5. Any suggestions as to the base package name? I was thinking either org.apache.lucene.cf or org.apache.lcf, to replace com.metacarta. Any preferences? Other suggestions? May I suggest org.apache.lucene.connect or perhaps just org.apache.connect? We don't really need to have lucene in our package names. For obvious reasons I prefer shorter to longer, as well. And since LCF is back-end agnostic, there's no technical reason it should be bound to Lucene. +1 Karl -- Karl Wright Software Engineer MetaCarta, Inc. 350 Massachusetts Avenue, 4th Floor, Cambridge, MA 02139 USA (617)-301-5511 www.metacarta.com http://www.metacarta.com Where to find it. This message may contain privileged, proprietary, and otherwise private information. If you are not the intended recipient, please notify the sender immediately.
activation.jar, mailapi.jar
The Meridio connector needs both of these jars to function, but they seem to be licensed by Sun as non-redistributable. For now, I've set them up as a build requirement of the connector - if they aren't there, the connector build will be skipped. But does anyone know an official Apache way to deal with these? Thanks, Karl
Re: activation.jar, mailapi.jar
Hi, On Wed, Feb 17, 2010 at 12:58 PM, Karl Wright kwri...@metacarta.com wrote: The Meridio connector needs both of these jars to function, but they seem to be licensed by Sun as non-redistributable. For now, I've set them up as a build requirement of the connector - if they aren't there, the connector build will be skipped. But does anyone know an official Apache way to deal with these? The Geronimo project has produced ALv2 versions of these jars: http://repo2.maven.org/maven2/org/apache/geronimo/specs/geronimo-javamail_1.4_spec/ http://repo2.maven.org/maven2/org/apache/geronimo/specs/geronimo-activation_1.1_spec/ BR, Jukka Zitting
Re: ant build scripts done; should be possible for others to build now
On Feb 17, 2010, at 6:55 AM, Karl Wright wrote: +1 for o.a.lcf +1
Official list of conditionally required upstream jars, wsdls, etc.
The complete list of stuff one needs to add to the source tree to get *everything* to build is as follows: kwri...@kuskokwim:~/wip/lcf/trunk/modules$ svn status ? connectors/documentum/dfc/dctm.jar ? connectors/documentum/dfc/dfcbase.jar ? connectors/documentum/dfc/dfc.jar ? connectors/filenet/filenet-api/Jace.jar ? connectors/meridio/wsdls/MeridioDMWS_axis.wsdl ? connectors/meridio/wsdls/RMDataSet.xsd ? connectors/meridio/wsdls/DMDataSet.xsd ? connectors/meridio/wsdls/MeridioRMWS_axis.wsdl ? connectors/meridio/wsdls/RMClassificationDataSet.xsd ? connectors/memex/mxie-java/JavaMXIELIB.jar ? connectors/sharepoint/wsdls/versions.wsdl ? connectors/sharepoint/wsdls/Permissions.wsdl ? connectors/sharepoint/wsdls/usergroup.wsdl ? connectors/sharepoint/wsdls/Lists.wsdl ? connectors/sharepoint/wsdls/DspSts.wsdl ? connectors/sharepoint/wsdls/webs.wsdl ? connectors/livelink/lapi/lapi.jar ? connectors/jcifs/jcifs/jcifs.jar Some notes: (1) jcifs.jar is LGPL and can be downloaded from http://jcifs.samba.org (2) lapi.jar is a product from OpenText - part of the LiveLink suite of products; we use the latest lapi (9.7.0 I think). I can ask about redistribution through OpenText Support, unless somebody has better contacts than I do. (3) SharePoint wsdls can be obtained easily from an installed SharePoint 3.0 instance, which anyone with an MSDN subscription should be able to install. See modules/sharepoint/upstream-diffs for details. Grant is checking on redistribution rights. (4) JavaMXIELIB.jar comes from Memex - I'm not sure they sell it separately, worth a check to see if we can redistribute. I can contact Memex and find out whether this is OK or not. (5) meridio wsdls and xsds must be downloaded from an installed Meridio server, version 5.0 SP1 or better, and then modified according to instructions described in connectors/meridio/upstream-diffs. Autonomy will not grant redistribution rights for these components, so people are on their own here. (6) FileNet Jace.jar is part of the FileNet P8 API component that IBM sells. Unlikely, but maybe worth a check to see if we can redistribute. Does anybody have decent IBM/FileNet contacts? (7) Documentum dfc jars are part of EMC's DFC product. This connector was tested with the 5.3.5 SP1 jars, which are old (they are on 6.5 now). Highly unlikely that we can get agreement to redistribute, but could be checked if someone has good contacts. I'm unlikely to have the needed patience to attempt it. Karl
[jira] Resolved: (CONNECTORS-3) Ant build needs to be created for code base
[ https://issues.apache.org/jira/browse/CONNECTORS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-3. -- Resolution: Fixed Ant builds are complete for the java part of the project. Still need builds for C part and for documentation, but will open separate tickets for those. Ant build needs to be created for code base --- Key: CONNECTORS-3 URL: https://issues.apache.org/jira/browse/CONNECTORS-3 Project: Lucene Connector Framework Issue Type: Task Reporter: Karl Wright The code granted by MetaCarta was built within a debian system. It would be much more consistent with Apache philosophy to make a self-contained ant build for the code base. In the future, if debian packages are again required, they could simply wrap the ant build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-2) Revamp package names and paths to remove MetaCarta references
[ https://issues.apache.org/jira/browse/CONNECTORS-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-2. -- Resolution: Fixed Code reorganized as described. Revamp package names and paths to remove MetaCarta references - Key: CONNECTORS-2 URL: https://issues.apache.org/jira/browse/CONNECTORS-2 Project: Lucene Connector Framework Issue Type: Task Reporter: Karl Wright The software grant from MetaCarta will not be reorganized prior to the grant, so MetaCarta-specific package and class names will be present. The code needs to be appropriately rearranged to adhere to Apache package-name standards. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
