sreekanthjnayar Posted July 8, 2014 Share Posted July 8, 2014 I am using the Jasperserver pro version. Recently I downloaded the source code. While compiling the code using the ant script mentioned in your document, I am getting the error shown below [java] [ERROR] Failed to execute goal on project ji-common: Could not resolve dependencies for project jaspersoft.ji-pro:ji-common:jar:5.6.0: The following artifacts could not be resolved: com.jaspersoft.jasperserver.api.metadata.impl:jasperserver-api-metadata-impl:jar:5.6.0, com.jaspersoft.jasperserver:jasperserver-war-jar:jar:5.6.0, com.jaspersoft.jasperserver.api.engine.impl:jasperserver-api-engine-impl:jar:5.6.0, com.jaspersoft.jasperserver.api.metadata.impl:jasperserver-repository-hibernate:jar:5.6.0: Could not find artifact com.jaspersoft.jasperserver.api.metadata.impl:jasperserver-api-metadata-impl:jar:5.6.0 in js-repo-svn (file://D:Sjn_codejsJasperReports-Server-5.6.0-srcjasperserver-repo) -> [Help 1]The ji-common is not bundled in the repo folder which seems to be the issue. Could you let me know how this can be resolved? Link to comment Share on other sites More sharing options...
tkavanagh Posted July 8, 2014 Share Posted July 8, 2014 It looks to me that the ji-common module (ie the <path>/jasperserver-pro/common folder) is looking for a dependency from the Community part of the source code (ie <path>/jasperserver/jasperserver-api-impl/metadata). I'm going to guess that this is because the Community ("ce") source didn't get built yet.Also, it looks like the path to the jasperserver-repo folder is good which is set in your buildomatic/default_master.properties file.Please give this a try:cd <path>/jasperserver/buildomaticjs-ant build-ce (this will build the community source)js-ant build-pro (this will build the commercial part of the source - which also depends on the community source) Link to comment Share on other sites More sharing options...
sreekanthjnayar Posted July 9, 2014 Author Share Posted July 9, 2014 Thanks tkavanagh for the quick reply. Build was successful for me after I ran the CE build. Thought that the CE and Pro versions aren't related, which led to not building the CE code initially. Just wanted to understand the reason behind this common folder dependency. Is it because that they share those code which comes as a part of common? Link to comment Share on other sites More sharing options...
tkavanagh Posted July 9, 2014 Share Posted July 9, 2014 Yes, the Community code is a fully functional web application with all server type functionality (manage users, manage permissions and authorizations, load reports, run reports, set up schedules for report execution, web services APIs, etc, etc). And the Commercial code has additional features (such as support for multiple sub-organizations, "Adhoc" reporting, dashboarding, auditing and diagnostic, etc) which are built on top of the Community functionality. Link to comment Share on other sites More sharing options...
sreekanthjnayar Posted July 10, 2014 Author Share Posted July 10, 2014 Thanks, that pretty much answers my question. 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