On Tue, May 13, 2008 at 2:01 PM, hackaton <[EMAIL PROTECTED]> wrote: > > >I think it's complaining of the mismatched versions.. the version set in > the > >pom is '2.0.6' while in the filename it's '2.0.8'. > > This is the maven-artifact-2.0.8.pom, I cannot see it mention anything > about > 2.0.6 and in fact it explicitly say the version is 2.0.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";> > <parent> > <artifactId>maven</artifactId> > <groupId>org.apache.maven</groupId> > <version>2.0.8</version> > </parent> > ... > </project>
Oh, I was pertaining to this snippet that was in the first email: File maven-artifact-2.0.8.pom has an invalid project model [groupId:org.apache.maven |artifactId:maven-artifact|version:2.0.6|packaging:null]; The model version [2.0.6] does not match the version portion of the filename: 2.0.8 But from the pom file snippet you pasted in your last email, the version is indeed 2.0.8. I have no idea why the message in the report says it's 2.0.6. Was there anything on the logs that might be helpful in debugging this? > > > >The only way to get rid of these errors is to fix the pom files, but i > think > >archiva 1.0.1 has a bug of not updating or reflecting the changes > >in the poms. Please see.. > > >http://jira.codehaus.org/browse/MRM-608 > >http://jira.codehaus.org/browse/MRM-622 > > >These two issues have already been fixed though, and will be included in > the > >next release. > > I am using 1.0.2 now, but the problem still exist. Do I have to remove any > file to force a fresh rescan? Could you try removing the repo from Archiva, add it back again and then do a repo & db scan? I'm not sure if this would work, but doing this would cleanup the database. If the behavior is still the same after doing the suggestion above, could you please file a jira for this? :-) > > > Also, error can also be found in these POM as well: > maven-plugin-tools-java-2.1.pom > maven-model-2.0.7.pom > maven-settings-2.0.7.pom > maven-profile-2.0.8.pom > maven-reporting-2.0.8.pom > maven-error-diagnostics-2.0.7.pom > maven-artifact-manager-2.0.8.pom > > They are part of Maven project, it is not likely they released incorrect > POMs! Yeah, I agree with you.. > > -- > View this message in context: > http://www.nabble.com/Unable-to-find-project-model-tp16393440p17201659.html > Sent from the archiva-users mailing list archive at Nabble.com. > > Thanks, Deng
