TEIID Maven dependency is not getting downloaded

[mntripathi]

I want to create and deploy an webapp which will expose a REST welservice as Datasource, and this app will be deployed as a Embedded Server with my app in Tomcat.

Here us my problem

If I add the dependency on older version in maven then it downloads the jar file while if I add dependency on newer version it only downloads pom file. below is my pom config

repository:

<repository>
    <id>jboss-public-repository-group</id>
    <url>http://repository.jboss.org/nexus/content/groups/public/</url>
  </repository>

This will download jar

<dependency>
    <groupId>org.jboss.teiid</groupId>
    <artifactId>teiid-client</artifactId>
    <version>8.5.0.Final</version>
</dependency>

This will download only pom file

<dependency>
    <groupId>org.jboss.teiid</groupId>
    <artifactId>teiid-client</artifactId>
    <version>8.9.1</version>
</dependency>

Can you please help me to understand that what I am doing wrong ?

[rareddy]

Manoj,

The JAR is there, you can see Index of /groups/public/org/jboss/teiid/teiid-client/8.9.1

May be try with mvn -U, to update

Ramesh..

[mntripathi]

Thanks Ramesh,

I tried but still getting error, below is the maven log

[ERROR] Failed to execute goal on project hello-teiid: Could not resolve dependencies for project hello:hello-teiid:jar:0.0.1-SNAPSHOT: Failed to collect dependencies at org.jboss.teiid:teiid-client:jar:8.9.1: Failed to read artifact descriptor for org.jboss.teiid:teiid-client:jar:8.9.1: Could not find artifact org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project hello-teiid: Could not resolve dependencies for project hello:hello-teiid:jar:0.0.1-SNAPSHOT: Failed to collect dependencies at org.jboss.teiid:teiid-client:jar:8.9.1

at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)

at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)

at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project hello:hello-teiid:jar:0.0.1-SNAPSHOT: Failed to collect dependencies at org.jboss.teiid:teiid-client:jar:8.9.1

at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:167)

at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)

... 22 more

Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed to collect dependencies at org.jboss.teiid:teiid-client:jar:8.9.1

at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:292)

at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:317)

at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:159)

... 23 more

Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.jboss.teiid:teiid-client:jar:8.9.1

at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:384)

at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:231)

at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:461)

at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:261)

... 25 more

Caused by: org.apache.maven.model.resolution.UnresolvableModelException: Could not find artifact org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 in central (https://repo.maven.apache.org/maven2)

at org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:170)

at org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:1071)

at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:427)

at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:398)

at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:389)

at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:375)

... 28 more

Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 in central (https://repo.maven.apache.org/maven2)

at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:459)

at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262)

at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:239)

at org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:166)

... 33 more

Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 in central (https://repo.maven.apache.org/maven2)

at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1012)

at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1004)

at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:725)

at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

[ERROR]

[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/DependencyResolutionException

[rareddy]

Well that is different than what you initially indicated. Look at the teiid/settings.xml at master · teiid/teiid · GitHub or use this settings.xml file for *your* maven repository configuration.

[mntripathi]

Thanks Ramesh,

It is working now.

[mickalas]

Hi Ramesh,

Is there a good reason why all dependent artifacts for a final release of teiid aren't in jboss release repo?  Policy of my company is not to add proxies to development repos and so this causes a bit of pain.

Thanks

Mick

[rareddy]

Michael,

Which "jboss releases" repo? Every artifact we produce is in the jboss "public" maven repository, checkout for the list  Index of /groups/public/org/jboss/teiid/teiid-client

Ramesh..

[mickalas]

Hi Ramesh,

Thanks for swift reply.

We are using EmbeddedTeiid with ModelMetaData. ModelMetadata comes from teiid-admin jar, this has a dependency on a number of artifacts that are available only from jboss earlyaccess. for example org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4.

We are using teiid 8.10.0.Final

Mick

[rareddy]

Mick,

Previously (< 8.11) the "teiid-admin" module was only used with the main server distribution as admin support was only available there, so that may be bringing in the additional dependencies that are JBoss AS specific. So, if you are working with versions < 8.11 of embedded you should not need this jar. However in Teiid 8.11, admin-api support has been added thus it may require this JAR. To remove this additional dependencies we may need to do some re-factoring of the code, for that you can add JIRA. Will see if we can get it into final 8.11

Ramesh..

[shawkins]

The admin jar is required for all versions of embedded as our vdb structural metadata classes come from there.

[mickalas]

Hi Ramesh,

ModelMetaData is in teiid-admin and this is used in Embedded example  e.g. Embedded Guide - Teiid 8.11 (draft) - Project Documentation Editor.

So, I think, teiid-admin is required < 8.11 if you want to used Embedded.

I have raised JIRA https://issues.jboss.org/browse/TEIID-3503. Great if this can be done in 8.11

Cheers

Mick

[rareddy]

Thanks Mick and Steve. You guys are right, I forgot that we pulled in the vdb.xml semantics into embedded. Thanks for JIRA.