Due to issues beyond my control, I can only build and support JasperServer 3.5.0 until the latest source code is updated for 3.7.1 or later.
That being said, I am getting a new error when building with maven:
I am referencing a build log from a committer @ FreeBSD that is working with me in getting the port into the FreeBSD portstree. He ran into an issue found below, and I was able to verify the same error.
http://people.freebsd.org/~ohauer/diffs/PR150208_jasperserver_build_err.txt
Any ideas?
11 Answers:
I am having what appears to be a similar issue with building 3.7. I get the following reason for my error:
Project ID: jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot
Reason: Error getting POM for 'jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot' from th
e repository: Unable to read local copy of metadata: Cannot read metadata from '
C:\\Documents and Settings\\userid\\.m2\\repository\\jaspersoft\\ji-pro\\ji-jpivot-ui
\\ji-jpivot\\3.7.0-SNAPSHOT\\maven-metadata-JasperForge Maven Repository.xml': end
tag name </td> must match start tag name <span> from line 263 (position: END_TAG
seen ...</span></span></td>... @267:173)
jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot:pom:3.7.0-SNAPSHOT
for project jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot
When I go to my local maven repository, it has file maven-metadata-JasperForge Maven Repository.xml, however that file is actually the HTML of a Jasper web page. My thought is that there is something wrong with their Maven/POM setup.
Note: I do not use the Buildomatic scripts as they do not work for my application, however, I have built this successfully several times last week during some testing, and now when ready to deploy to production, I can't get a production build. Nothing has changed from my setup that worked last week.
Here is a listing of my directory and the content of the only metadata file in it:
| Code: |
[jhelfman@eggman /root/.m2/repository/commons-collections/commons-collections]$ ls -1 3.1 3.2 maven-metadata-JasperForge Maven Repository.xml maven-metadata-central.xml maven-metadata-central.xml.sha1 maven-metadata-jaspersoft.xml maven-metadata-js-repo-svn.xml [jhelfman@eggman /root/.m2/repository/commons-collections/commons-collections]$ cat maven-metadata-js-repo-svn.xml <?xml version="1.0" encoding="UTF-8"?> <metadata> <groupId>commons-collections</groupId> <artifactId>commons-collections</artifactId> </metadata> </td></tr></tbody></table><br><br>Post Edited by jgh at 11/03/2010 16:23 |
The problem to me, seems to be with JasperServer Maven repository, or something related. My maven-metadata-JasperForge Maven Repository.xml file doesn't contain valid Maven data, but rather an html web page.
See attached file.
Also see a forum posting that jasperforge was down for updates on 10/20/2010. My guess is this broke something major.
Found this solution on the JasperReports forum.
http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=80434
I just disabled the Jasper repository and didn't add the mirror, and my build is now working. Still something that needs fixed on the JF side I beilieve, but this at least go me around it.
jgh
Wrote:
| Can you paste your xml file? I received this error. add-jdbc-driver: [exec] Error reading settings.xml: Expected root element 'settings' but found 'profiles' (position: START_TAG seen <profiles>... @1:10) [exec] Line: 1 [exec] Column: 10 BUILD FAILED |
I found how to get the settings in. But it still fails with the error below the setting file:
| Code: |
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>default</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>jaspersoft</id>
<name>Jasper Soft</name>
<url>http://jasperforge.org/maven2/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
</profile>
</profiles>
</settings>
[exec] Unable to get dependency information: Unable to read local copy of metadata: Cannot read metadata from '/home/jhelfman/.m2/repository/commons-collections/commons-collections/maven-metadata-jaspersoft.xml': end tag name </td> must match start tag name <span> from line 263 (position: END_TAG seen ...</span></span></td>... @267:173)
[exec] commons-collections:commons-collections:jar:null
[exec]
[exec] from the specified remote repositories:
[exec] JasperForge Maven Repository (http://jasperforge.org/svn/repos/maven2),
[exec] central (http://repo1.maven.org/maven2),
[exec] Maven Snapshots (http://snapshots.maven.codehaus.org/maven2),
[exec] jaspersoft (http://www.jasperforge.org/maven2),
[exec] js-repo-svn (file:///home/jhelfman/jasperserver/work/jasperserver-3.5.0-src/jasperserver-repo),
[exec] Repo1 Maven (http://repo1.maven.org/maven2/)
[exec]
[exec] Path to dependency:
[exec] 1) com.jaspersoft.jasperserver.api.metadata:jasperserver-api-metadata:jar:3.5.0
[exec] 2) jasperreports:jasperreports:jar:3.5.0
[exec]
[exec]
[exec]
[exec] [INFO] ------------------------------------------------------------------------
[exec] [INFO] For more information, run Maven with the -e switch
[exec] [INFO] ------------------------------------------------------------------------
[exec] [INFO] Total time: 3 minutes 39 seconds
[exec] [INFO] Finished at: Wed Nov 03 19:53:31 GMT 2010
[exec] [INFO] Final Memory: 20M/51M
[exec] [INFO] ------------------------------------------------------------------------
BUILD FAILED
/home/jhelfman/jasperserver/work/jasperserver-3.5.0-src/jasperserver/buildomatic/dev.xml:159: The following error occurred while executing this line:
/home/jhelfman/jasperserver/work/jasperserver-3.5.0-src/jasperserver/buildomatic/dev.xml:11: exec returned: 1
</td></tr></tbody></table> |
sample settings.xml uploaded.
I changed the local path to just say userid (this is from a win xp machine)
I changed our internal repository location to just read ourRepo
The main change that made it work for me was by setting the below values to false in both the standard and JasperServerDevProfile profiles
<repository>
<id>JasperForge Maven Repository</id>
<url>http://www.jasperforge.org/maven2</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
<releases>
<enabled>false</enabled>
</releases>
</repository>
I build by running mvn -PJasperServerDevProfile install
What is odd to me, is that anything is actually required to build outside of the source code. Why not just include the maven source code in the jasperserver released code for that version?
It is a snapshot in time and it will always build, and really decreases a chance of build failure.
The url below:
http://www.jasperforge.org/maven2/commons-beanutils/commons-beanutils/1....
does not exist.
| Code: |
[exec] Downloading: http://www.jasperforge.org/maven2/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.pom
[exec] 0/6K
[exec] 1/6K3/6K5/6K6/6K8/6K11/6K13/6K15/6K18/6K19/6K21/6K23/6K24/6K6K downloaded (commons-beanutils-1.7.0.pom)[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '46a30661ce4a939950d8dfd36fb00fa99c01022f'; remote = '<!DOCTYPE' - IGNORING
[exec] [WARNING] POM for 'commons-beanutils:commons-beanutils:pom:1.7.0:compile' is invalid.
[exec]
</td></tr></tbody></table><br><br>Post Edited by jgh at 11/03/2010 22:44 |
