[
https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3492:
-------------------------------------
Taking a second look at again, as I mentioned in one of the comments above, it seems
impossible to add another version of "com.force.api" maven dependencies in a
single build system and still keep the maven enforcer rules. If we want to add
"34" this must be added as a separate GIT repo project all together, which can
also serve as template, but will not be included with the main build. Is that fine?
Maven enforcer rule does not let you override the version property in the individual
module projects. It simply fails the build.
Provide a mechanism for users to modify the salesforce api version
------------------------------------------------------------------
Key: TEIID-3492
URL:
https://issues.jboss.org/browse/TEIID-3492
Project: Teiid
Issue Type: Feature Request
Components: Salesforce Connector
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.12
We should provide a mechanism to easily target a different salesforce api version. We
are currently defaulting to v22, which is quite old. The version change must be
controlled as the metadata and the sf jars can be incompatible - if you for example build
a model from v22, then you must stay on v22, and then recreate the model once you want to
move to a later version.
Currently the update procedure would be to copy/modify the salesforce translator module
and have it point to newer wsc and partner api jars (which are java api compatible from
what I have seen) and then change the any salesforce resource adapters to use the new api
url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)