Build Error with Teiid POM Dependency
-------------------------------------
Key: TEIID-2857
URL:
https://issues.jboss.org/browse/TEIID-2857
Project: Teiid
Issue Type: Bug
Components: Embedded
Affects Versions: 8.6
Reporter: Ivan Chan
Assignee: Van Halbert
Labels: teiid
Fix For: 8.7
In the jboss public maven repository:
https://repository.jboss.org/nexus/content/groups/public
The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be
Teiid build/configuration bugs.
These two issues are causing our source code build to fail.
The pom file is located here:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/...
In this pom file there are two declared dependencies:
<version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform>
<jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version>
<dependency>
<groupId>org.jboss.integration-platform</groupId>
<artifactId>jboss-integration-platform-bom</artifactId>
<version>${version.org.jboss.integration-platform}</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-parent</artifactId>
<version>${jbossas-version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Here are the issues:
1) Snapshot dependency existing in the 8.6.0-FINAL Release
- jboss-integration-platform-bom/6.0.0-SNAPSHOT
2) Declared dependency does not exist in the repo
repository.jboss.org
- jboss-as-parent/7.2.0.Alpha1-redhat-4
- We see dependencies only for:
- 7.2.0.Alpha1-SNAPSHOT
- 7.2.0.Fina
I'm not sure why these dependencies are needed when pulling in the Teiid artifacts,
but perhaps because the <scope> of
these dependencies is set to "import" (<scope>import</scope>)
Our usage of the
repository.jboss.org is to have snapshots disabled. So that is why the
6.0.0-SNAPSHOT fails to be found.
For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in
repository.jboss.org so this also fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: