Issue migrated from: https://sourceforge.net/tracker/index.php?func=detail&aid=1486078&group_...
[ 1486078 ] JasperServer build
Submitted By: Heme Aqui - heme_aqui
Date Submitted: 2006-05-10 18:15
Last Updated By: lucianc - Comment added
Date Last Updated: 2006-05-11 05:10
Number of Comments: 2
Number of Attachments: 0
Assigned To: T Kavanagh
I followed the JasperServer source build article to retrieved the source code of JasperServer.
I'm experiencing a problem when executing the 'mvn install' command. Here's the error message that I get:
[ERROR] BUILD ERROR
[INFO] Failed to resolve artifact.
Try downloading the file manually from the project
Then, install it using the command:
mvn install:install-file -DgroupId=jasperreports
Path to dependency:
1 required artifact is missing.
from the specified remote repositories:
Am I missing something here? Please help.
Date: 2006-05-11 05:10
Logged In: YES
JasperReports 1.2.2 is not yet uploaded on the public Maven repository as it depends on Commons Javaflow which is not yet available on Maven. We've been trying to see how to get a Javaflow snapshot uploaded on Maven, and once that happens we will upload JR 1.2.2 as well.
Therefore, currently, JR 1.2.2 is only available on jasperserver-repo; the jar found there is not Javaflow-enabled.
Date: 2006-05-10 21:59
Logged In: YES
I believe that the jasperreports jar is coming from the jasperintel/jasperserver-repo source tree. The
jasperserver-repo tree is for jars that are not up on the on-line maven2 repositories. The jasperreports-1.2.2.jar is
actually up on maven2 now, so this should probably be
cleaned up in our build (I will follow up).
Nevertheless, this should work for you. I am thinking that your settings.xml (which points to jasperserver-repo) might
be not quite right. Perhaps there is an extra "trunk" dir name after the ~/jasperintel/jasperserver-repo ?
Name Description Download
No Files Currently Attached
Field Old Value Date By
assigned_to nobody 2006-05-10 22:00 tkavanagh
Teodor Danciu: 02/20/2007 4:06 AM PST
This should no longer be an issue in more recent JasperServer releases.
Closed set to 02/20/2007
Status changed from Open to Closed