Bug 1018818 - Use community bom for Teiid
Summary: Use community bom for Teiid
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: 6.0
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 13:02 UTC by Nick Cross
Modified: 2014-07-09 05:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-10 19:59:29 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-2697 0 Major Closed Change to use community bom 2014-04-23 11:33:52 UTC

Description Nick Cross 2013-10-14 13:02:13 UTC
Teiid should import dependencies from the community bom (https://github.com/jboss-integration/jboss-integration-platform-bom/)

Comment 1 JBoss JIRA Server 2013-10-14 18:11:31 UTC
Van Halbert <vhalbert> updated the status of jira TEIID-2697 to Coding In Progress

Comment 2 JBoss JIRA Server 2013-10-14 18:12:14 UTC
Van Halbert <vhalbert> made a comment on jira TEIID-2697

committed change to root pom.xml:  [8.4.x e7168ef] Teiid-2697 change to use jboss-integration bom

Comment 3 JBoss JIRA Server 2013-10-14 18:12:17 UTC
Van Halbert <vhalbert> updated the status of jira TEIID-2697 to Open

Comment 4 JBoss JIRA Server 2013-10-14 18:42:47 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2697

Is this a dup of TEIID-2298?  On that one there was an issue at the time on why Ramesh didn't pursue it, but I don't see a comment or related email.  Or is it specific to product and shouldn't be merged forward?

When I run the build with this change I see:

Failed to execute goal on project teiid-admin: Could not resolve dependencies for project org.jboss.teiid:teiid-admin:jar:8.4.1: The following artifacts could not be resolved: org.jboss.as:jboss-as-cli:jar:7.2.1.Final-redhat-10, org.jboss.as:jboss-as-controller:jar:7.2.1.Final-redhat-10: Could not find artifact org.jboss.as:jboss-as-cli:jar:7.2.1.Final-redhat-10 in jboss-eap-alpha (http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Alpha1/maven-repository/)

Are there additional repos needed?

Comment 9 JBoss JIRA Server 2013-10-24 18:13:12 UTC
Van Halbert <vhalbert> updated the status of jira TEIID-2697 to Resolved

Comment 10 JBoss JIRA Server 2013-10-24 18:13:12 UTC
Van Halbert <vhalbert> made a comment on jira TEIID-2697

Added community bom's for:

            <groupId>org.jboss.integration-platform</groupId>
            <artifactId>jboss-integration-platform-bom</artifactId>

             <groupId>org.jboss.as</groupId>
             <artifactId>jboss-as-parent</artifactId>

Comment 11 JBoss JIRA Server 2013-10-25 12:06:12 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-2697 to Reopened

Comment 12 JBoss JIRA Server 2013-10-25 12:06:12 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2697

The changes broke the arquillian tests.  From what I recall these had an issue that no arquillian target for EAP was provided, so this may be somewhat messy to fix.

Comment 13 JBoss JIRA Server 2013-10-25 12:24:13 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2697

It looks like if we just add back the arquillian version and a few more overrides it works as expected.  Can this go back to 8.4.1 as well?

Comment 14 JBoss JIRA Server 2013-10-25 12:32:37 UTC
Van Halbert <vhalbert> made a comment on jira TEIID-2697

Back porting to 8.4.1 would be good.

Comment 15 JBoss JIRA Server 2013-10-25 12:45:48 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-2697 to Resolved

Comment 16 JBoss JIRA Server 2013-10-25 12:45:48 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2697

updated the parent and test common poms for arquillian to run.

Comment 17 JBoss JIRA Server 2013-10-25 16:54:22 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2697

this also broke the cassandra kitting by forcing the managed version of jackson

Comment 18 JBoss JIRA Server 2013-10-25 16:58:49 UTC
Ramesh Reddy <rareddy> made a comment on jira TEIID-2697

ah! I was looking into fixing the deployment and was not sure why it was occurring?

Comment 19 JBoss JIRA Server 2013-10-25 17:48:31 UTC
Steven Hawkins <shawkins> made a comment on jira TEIID-2697

changed the cassandra module.xml to use the managed jackson version 1.9.9 instead of the datastax 1.9.2 - with limited query testing this still worked fine.  We'll put more effort into handling the cassandra dependencies, especially the conflicting ones, with later productization.

Comment 20 belong 2013-11-18 03:08:46 UTC
Fixed before GA of major release - setting to requires_doc_text- accordingly

Comment 21 JBoss JIRA Server 2014-04-23 11:33:54 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-2697 to Closed


Note You need to log in before you can comment on or make changes to this bug.