[
https://issues.apache.org/jira/browse/CONNECTORS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204068#comment-13204068
]
Karl Wright edited comment on CONNECTORS-402 at 2/8/12 11:06 PM:
-----------------------------------------------------------------
I created a branch CONNECTORS-402 for this work.
Problems still outstanding:
(1) Since JDBC drivers must be built into the war files, they cannot be
delivered into connector-lib. This means we have no ability to prebuild the
JDBC connector to include oracle, mssql, sybase, or mysql support. We need a
way of suppressing inclusion of these JDBC jars when building for release, even
though we will likely have run the "ant download-dependencies" target in the
release branch.
(2) The tests all need to be run and checked, since the place where proprietary
materials are placed has now become "lib-proprietary" across the board.
(3) The how-to-build-and-deploy documentation needs significant changes.
(4) The process components of the FileNet and Documentum connectors are where
the proprietary jars wind up; we need a solution for these.
(5) How to make commented-out connectors.xml entries when building for release,
for those connectors that have proprietary components.
was (Author: kwri...@metacarta.com):
I created a branch CONNECTORS-402 for this work.
Problems still outstanding:
(1) Since JDBC drivers must be built into the war files, they cannot be
delivered into connector-lib. This means we have no ability to prebuild the
JDBC connector to include oracle, mssql, sybase, or mysql support. We need a
way of suppressing inclusion of these JDBC jars when building for release, even
though we will likely have run the "ant download-dependencies" target in the
release branch.
(2) The tests all need to be run and checked, since the place where proprietary
materials are placed has now become "lib-proprietary" across the board.
(3) The how-to-build-and-deploy documentation needs significant changes.
(4) The process components of the FileNet and Documentum connectors are where
the proprietary jars wind up; we need a solution for these.
> Separate the proprietary / non-proprietary deliverables for each connector
> --------------------------------------------------------------------------
>
> Key: CONNECTORS-402
> URL: https://issues.apache.org/jira/browse/CONNECTORS-402
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Build
> Affects Versions: ManifoldCF 0.4
> Reporter: Piergiorgio Lucidi
> Assignee: Karl Wright
> Fix For: ManifoldCF 0.5
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> As we have spoken today this ticket is dedicated to try to work on the build
> process to separate proprietary and non-proprietary libraries in the release
> package.
> In this way, for example, we could have a standard way to release a specific
> library for the connector (mcf-alfresco-connector) without release
> proprietary libraries and allow users to add proprietary libraries in a
> specific folder "connector-lib-proprietary" that could be added to the
> ManifoldCF classloader.
--
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
