[teiid-issues] [JBoss JIRA] (TEIID-3037) Incorrect odata4j jar name

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986637#comment-12986637 ] 

Steven Hawkins commented on TEIID-3037:
---------------------------------------

Yes, we applied https://github.com/teiid/teiid/commit/f2c566e1224254c723f2603b42247ebfdf83bdf0 from our build group, which removed the extra -redhat, but didn't see that they had not corrected the repository.  So yes the build still picked up the -redhat-redhat jar.  The workarounds are to change the module.xml or the jar name.  We'll likely post a rekitting with that addressed.

> Incorrect odata4j jar name
> --------------------------
>
>                 Key: TEIID-3037
>                 URL: https://issues.jboss.org/browse/TEIID-3037
>             Project: Teiid
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 8.8
>            Reporter: Cristiano Nicolai
>            Assignee: Steven Hawkins
>            Priority: Blocker
>
> When deploying Teiid 8.8.0.Final, odata4j fails to initialize due to the wrong jar name.
> MSC000001: Failed to start service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: JBAS018759: Failed to load module: deployment.teiid-odata-8.8.0.Final.war:main
> Module declaration is set as:
> <resource-root path="odata4j-core-0.8.0-SNAPSHOT-redhat.jar" />
> But the provided jar name is:
> odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar
> There is an extra "-redhat" in the jar name.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)