You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Dhiraj Bokde (JIRA)" <ji...@apache.org> on 2016/08/02 18:25:20 UTC

[jira] [Commented] (CAMEL-10218) Camel-salesforce-maven-plugin error if version is specified as 37.0

    [ https://issues.apache.org/jira/browse/CAMEL-10218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404535#comment-15404535 ] 

Dhiraj Bokde commented on CAMEL-10218:
--------------------------------------

This has been fixed in CAMEL-10144, and should be available in the next release. If you want you can get the changes from 2.1.7.x branch, patch your local version and work with that until 2.1.7.3 is released. 

> Camel-salesforce-maven-plugin error if version is specified as 37.0
> -------------------------------------------------------------------
>
>                 Key: CAMEL-10218
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10218
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-salesforce
>    Affects Versions: 2.17.2
>         Environment: Windows 7 Enterprise edition 64 bit, Java 1.8, camel 2.17.2, Salesforce API 37.0, Spring Tool Suite 3.7.3.RELEASE
>            Reporter: Rajesh A
>            Priority: Minor
>
> I need to get the Salesforce API version 37.0 DTO in order to use Salesforce Replay ID option. Hence, I included the "version" option in camel-salesforce-maven-plugin JAXB generation. However, maven plugin failed to generate the JAXB classes. Here is the error log:
> *---Error Log ---*
> [INFO] Scanning for projects...
> [INFO]                                                                         
> [INFO] ------------------------------------------------------------------------
> [INFO] Building camel-salesforce 0.0.1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO] 
> [INFO] --- camel-salesforce-maven-plugin:2.17.2:generate (default-cli) @ camel-salesforce ---
> [INFO] Logging initialized @8602ms
> [INFO] Available providers: SUN version 1.8.
> log4j:WARN No appenders could be found for logger (org.apache.camel.maven.CamelSalesforceMojo).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> [INFO] Salesforce login...
> [INFO] Login user xxxxxxxxxxx@xxxx.com at Salesforce loginUrl: https://login.salesforce.com/services/oauth2/token
> [INFO] Login successful
> [INFO] Salesforce login successful
> [INFO] Getting Salesforce Objects...
> [INFO] Logout successful
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 9.964 s
> [INFO] Finished at: 2016-08-02T11:31:52-04:00
> [INFO] Final Memory: 30M/291M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.camel.maven:camel-salesforce-maven-plugin:2.17.2:generate (default-cli) on project camel-salesforce: Error getting global Objects Unrecognized field "mruEnabled" (Class org.apache.camel.component.salesforce.api.dto.SObject), not marked as ignorable
> [ERROR] at [Source: java.io.ByteArrayInputStream@33b082c5; line: 1, column: 343] (through reference chain: org.apache.camel.component.salesforce.api.dto.GlobalObjects["sobjects"]->org.apache.camel.component.salesforce.api.dto.SObject["mruEnabled"])
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [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 read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> If I update the "version" option anything below 34.0 it works. However, I need to version 37.0 API. Please fix this *ASAP*, as this is having an impact in my project schedule.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)