You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/10/13 06:50:51 UTC
[jira] Updated: (MRM-951) "Unable to find project model" although
everything seems to be perfectly fine
[ http://jira.codehaus.org/browse/MRM-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-951:
-----------------------------
Fix Version/s: 1.2
some patches were recently applied to trunk - it would be worth reviewing if this issue is related and/or fixed by them
> "Unable to find project model" although everything seems to be perfectly fine
> -----------------------------------------------------------------------------
>
> Key: MRM-951
> URL: http://jira.codehaus.org/browse/MRM-951
> Project: Archiva
> Issue Type: Bug
> Components: browser
> Affects Versions: 1.1.2
> Environment: Linux, Standalone-Version, Maven2-Repository
> Reporter: David Bilge
> Fix For: 1.2
>
>
> We had a problem with our m2-repository (which Archiva uses as its "internal"-repository) in such a way that we could not install artifacts from one of our projects into the repository. We would get the error "Error installing artifact's metadata: Error installing metadata: Error updating group repository metadata input contained no data" - obviously something messed up with the maven-metadata.xml or maven-metadata-local.xml. So I deleted this directory from the repository and built the project again - unfortunately (now as before) whenever I try to view the version-properties via "browse", I get the following error:
> "Unable to find project model for [our.project.version]."
> Looking into the log-file I find:
> 2008-09-16 13:48:34,703 [btpool0-4] ERROR org.apache.maven.archiva.consumers.database.ProjectModelToDatabaseConsumer - Unable to process model /root/.m2/repository/our.company.project/version/artifact-version.pom due to : javax.jdo.JDOUserException : Field org.apache.maven.archiva.model.Exclusion.artifactId
> is null, but is mandatory as its described in the jdo metadata
> javax.jdo.JDOUserException: Field org.apache.maven.archiva.model.Exclusion.artifactId is null, but is mandatory as its described in the jdo metadata
> at org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:120)
> at org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757)
> at org.apache.maven.archiva.model.Exclusion.jdoProvideField(Exclusion.java)
> at org.apache.maven.archiva.model.Exclusion.jdoProvideFields(Exclusion.java)
> at org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115)
> at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252)
> So I checked the pom which does not have an artifactId according to Archiva. There I find:
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <parent>
> ...
> </parent>
> <artifactId>ARTIFACT</artifactId>
> <packaging>war</packaging>
> <name>Name</name>
> <build>
> ...
> </build>
> ...
> </project>
> I.e.: there is an artifactId in the pom.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira