Jump to content
We've recently updated our Privacy Statement, available here ×

How to upgrade to jrs-rest-java-client 8.1.0 ?


fabio.constantino

Recommended Posts

We're using jrs-rest-java-client and jasper reports on version 6.2.2 and want to upgrade to the latest release available - 8.1.0.

However, while trying to do this, one of the transitive dependencies for jrs-rest-java-client 8.1.0 is the jasperserver-dto-8.1.0 which references a parent dependency com.jaspersoft.jasperserver:server version 8.1.0.

While trying to build this project, we got the error "Could not find artifact com.jaspersoft.jasperserver:server:pom:8.1.0". Looking further into this, it seems that even though the available jasperserver-dto-8.1.0.pom in the jasper repository references this parent version 8.1.0, the downloaded jar file comes with "release-8.1.0-SNAPSHOT" as the parent version. Also, looking into https://jaspersoft.jfrog.io/ui/native/jrs-ce-releases/com/jaspersoft/jasperserver/server/ we can see that the latest release for com.jaspersoft.jasperserver:server is in fact 7.9.0.

How would you advise to proceed here? Can you make the release for com.jaspersoft.jasperserver:server 8.1.0 available? If not, is there an alternative?

 

Best regards.

Link to comment
Share on other sites

  • 1 month later...
  • Replies 12
  • Created
  • Last Reply

Top Posters In This Topic

Hello, thank you for taking the time to look into this.

I've looked at those git repos before. The issue is that if you look at the available 8.1.0 release source code, the pom.xml file is referencing a jasperserver-dto version 8.1.0 that does not exist. That's what leads into the problem I described in my question.

Link to comment
Share on other sites

  • 2 weeks later...

Hi fabio.constantino,

Sorry for the delay in our response. I have worked with our internal team and with their help uploaded the missing files for the server and got the build verified. 

Can you please download the references and let us know if you face any error building this project?

https://jaspersoft.jfrog.io/ui/native/jrs-ce-releases/com/jaspersoft/jasperserver/server/
https://jaspersoft.jfrog.io/ui/native/jrs-ce-releases/com/jaspersoft/jasperserver/jasperserver-dto

https://jaspersoft.jfrog.io/ui/native/jrs-ce-releases/com/jaspersoft/jasperserver/jasperserver-dto/8.1.0/
https://jaspersoft.jfrog.io/ui/native/jrs-ce-releases/com/jaspersoft/jasperserver/server/8.1.0/

Thanks.

Link to comment
Share on other sites

Hello,

I have re-tested my application with jrs-rest-java-client 8.1.0 and I'm getting the following error (I believe it's the same problem as before):

Failed to read artifact descriptor for com.jaspersoft.jasperserver:jasperserver-dto:jar:8.1.0org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for com.jaspersoft.jasperserver:jasperserver-dto:jar:8.1.0    at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:305)    at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:171)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:538)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:523)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:410)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:362)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process(DefaultDependencyCollector.java:349)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:506)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:362)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process(DefaultDependencyCollector.java:349)    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:254)    at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:284)    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:170)    at org.apache.maven.project.DefaultProjectBuilder.resolveDependencies(DefaultProjectBuilder.java:227)    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:200)    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:124)    at org.eclipse.m2e.core.internal.IMavenToolbox.readMavenProject(IMavenToolbox.java:88)    at org.eclipse.m2e.core.internal.project.registry.DefaultMavenDependencyResolver.lambda$0(DefaultMavenDependencyResolver.java:70)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:214)    at org.eclipse.m2e.core.internal.project.registry.DefaultMavenDependencyResolver.resolveProjectDependencies(DefaultMavenDependencyResolver.java:66)    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refreshPhase2(ProjectRegistryManager.java:573)    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.lambda$5(ProjectRegistryManager.java:481)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:479)    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:362)    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:314)    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:146)    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$0(MavenBuilder.java:84)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:394)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:275)    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:214)    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:83)    at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:192)    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:1020)    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:247)    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:392)    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:395)    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:506)    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:454)    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:536)    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:196)    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:289)    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)Caused by: org.apache.maven.model.resolution.UnresolvableModelException: com.jaspersoft.jasperserver:server:pom:8.1.0 was not found in https://artifactory.devops.ellucian.com/artifactory/admin-framework-local/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of snapshots has elapsed or updates are forced    at org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:176)    at org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:222)    at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1150)    at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:916)    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:361)    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:267)    at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296)    ... 49 moreCaused by: org.eclipse.aether.resolution.ArtifactResolutionException: com.jaspersoft.jasperserver:server:pom:8.1.0 was not found in https://artifactory.devops.ellucian.com/artifactory/admin-framework-local/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of snapshots has elapsed or updates are forced    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:425)    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:229)    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:207)    at org.apache.maven.repository.internal.DefaultModelResolver.resolveModel(DefaultModelResolver.java:172)    ... 55 moreCaused by: org.eclipse.aether.transfer.ArtifactNotFoundException: com.jaspersoft.jasperserver:server:pom:8.1.0 was not found in https://artifactory.devops.ellucian.com/artifactory/admin-framework-local/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of snapshots has elapsed or updates are forced    at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:217)    at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:189)    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:574)    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:484)    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:402)    ... 58 more[/code]

Looking over the jars, the pom.xml inside of the jasperserver-dto is still referencing:

<parent>    <groupId>com.jaspersoft.jasperserver</groupId>    <artifactId>server</artifactId>    <version>release-8.1.0-SNAPSHOT</version>  </parent>[/code]

 

Link to comment
Share on other sites

Hi fabio.constantino

Our team has tried and they are able to build this project without this issue referring the same pom and artifacts. If you are still facing this issue, can you just outline the steps you followed?

I also have seen one customer facing same issue as yours, due to reference to "release-8.1.0-SNAPSHOT" as <parent> element, which our engineering team is not facing. If you want to try replacing it with "release-8.1.0" and can use local artifactory then please try that.

Thanks.

Link to comment
Share on other sites

Hello, I seem to have posted my previous answer as a comment by accident, sorry about that.

  1. "If you are still facing this issue, can you just outline the steps you followed?"
    1. I am simply changing my pom.xml to use jrs-rest-java-client version 8.1.0 and running a maven update. What I can see is that jrs-rest-java-client 8.1.0 has a transitive dependency for jasperserver-dto 8.1.0. During the maven update, the jar for jasperserver-dto 8.1.0 is downloaded but then it fails due to its parent version being release-8.1.0-SNAPSHOT.
  2. "and can use local artifactory then please try that"
    1. ​​​​​​​This is not possible for us.

 

Link to comment
Share on other sites

Hi,

Have you tried capturing the build errors with maven debug enabled, to see if it can provide more details? If not can you try that and provide that here? 

Also, do you have right reference to the maven repo? Your stack trace has below error for jasperserver:server. 

Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: com.jaspersoft.jasperserver:server:pom:8.1.0 was not found in https://artifactory.devops.ellucian.com/artifactory/admin-framework-local/ during a previous attempt

Why is it searching in https://artifactory.devops.ellucian.com/artifactory/admin-framework-local/  repo for the jasperserver:server ?

Make sure you have below three repo referenced property.

repositories>    <repository>        <id>central</id>        <name>Maven Central</name>        <url>https://repo.maven.apache.org/maven2</url>    </repository>    <repository>        <id>jaspersoft-clients-snapshots</id>        <name>Jaspersoft clients snapshots</name>        <url>https://jaspersoft.jfrog.io/jaspersoft/jaspersoft-clients-releases</url>    </repository>    <repository>        <id>jaspersoft-central</id>        <name>jaspersoft-releases</name>        <url>https://jaspersoft.jfrog.io/jaspersoft/jrs-ce-releases</url>    </repository></repositories>[/code]
Link to comment
Share on other sites

  • 3 weeks later...

Hello jmand,

Sorry for the delay in the response, other priorities came up. I was using the following URLs:

https://jaspersoft.jfrog.io/artifactory/jaspersoft-clients-releases/
https://jaspersoft.jfrog.io/artifactory/jrs-ce-releases/

Looking at the ones you provided, it looks like the problem I reported initially is resolved. I still have to test this but will let you know as soon as I do.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...