joshuatoepferyahoo.com Posted April 2, 2015 Share Posted April 2, 2015 Hasy anyone else encountered this problem?Linux Red Hat 6.2 > ./js-ant clean-config> ./js-ant build-ce[java] [ERROR] Failed to execute goal on project jasperserver-api-common: Could not resolve dependencies for project com.jaspersoft.jasperserver.api.common:jasperserver-api-common:jar:6.0.1: Failed to collect dependencies at org.jboss.teiid:teiid-engine:jar:8.8.1: Failed to read artifact descriptor for org.jboss.teiid:teiid-engine:jar:8.8.1: Could not find artifact org.jboss.as:jboss-as-parent:pom:7.2.0.Alpha1-redhat-4 in js-repo-svn (file:///home/console/installs/jasperreports-server-6.0.1-src/jasperserver-repo) -> [Help 1]Thanks in advance. Link to comment Share on other sites More sharing options...
joshuatoepferyahoo.com Posted April 2, 2015 Author Share Posted April 2, 2015 Just to follow this with a note. The pom does exist in the jasperserver-repo and in the correct location. Link to comment Share on other sites More sharing options...
hozawa Posted April 2, 2015 Share Posted April 2, 2015 It may be because RedHat 6.0.x is not included as a supported platform by Jaspersoft.Check the following document for supported platforms:http://community-static.jaspersoft.com/sites/default/files/docs/jaspersoft_platform_support_v6.0.pdf Link to comment Share on other sites More sharing options...
joshuatoepferyahoo.com Posted April 3, 2015 Author Share Posted April 3, 2015 I looked at the doc you posted. It seems that the installer is not supported on our version of Red hat, which is fine. But I'm building the project from source. Link to comment Share on other sites More sharing options...
Solution joshuatoepferyahoo.com Posted April 3, 2015 Author Solution Share Posted April 3, 2015 I found I had two issues. The first was security for the user I was trying to run the build process. Once I got that all worked out. I found a second problem, which was the one above. I actually found a work around. The default_master.properties file has a property called maven-localrepo-path. If this is set to the path of where the jasperserver-repo is located it seems to pick up the artifact correctly. The maven process must have not been retrieving the pom correctly or maybe it was my adding the jboss repo to my settings.xml. I did both so either could have fixed the problem. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now