[
http://jira.codehaus.org/browse/MRM-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117177
]
Maria Odea Ching commented on MRM-622:
--------------------------------------
I applied the patches locally and it doesn't seem to work for me :( I tested it
with the scenario specified above using maven-antrun-plugin as the test
artifact. i've just edited the pom file itself (changed the dependency junit
version from 3.8.1 to 3.8.2 ) instead of re-deploying after making the changes.
I got this error during the database update:
jvm 1 | 2007-12-18 14:56:21,093 [pool-1-thread-1] ERROR
org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project
- Unable to process model
/home/deng/TestFiles/sample-local-repo/org/apache/maven/plugins/maven-ant-plugin/2.0-beta-1/maven-ant-plugin-2.0-beta-1.pom
due to : javax.jdo.JDOUserException : Field
org.apache.maven.archiva.model.ArchivaProjectModel.origin is null, but is
mandatory as its described in the jdo metadata
jvm 1 | javax.jdo.JDOUserException: Field
org.apache.maven.archiva.model.ArchivaProjectModel.origin is null, but is
mandatory as its described in the jdo metadata
jvm 1 | at
org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:120)
jvm 1 | at
org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757)
jvm 1 | at
org.apache.maven.archiva.model.ArchivaProjectModel.jdoProvideField(ArchivaProjectModel.java)
jvm 1 | at
org.apache.maven.archiva.model.ArchivaProjectModel.jdoProvideFields(ArchivaProjectModel.java)
jvm 1 | at
org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115)
jvm 1 | at
org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252)
jvm 1 | at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519)
jvm 1 | at org.jpox.store.StoreManager.insert(StoreManager.java:920)
jvm 1 | at
org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667)
jvm 1 | at
org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646)
jvm 1 | at
org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198)
jvm 1 | at
org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1261)
jvm 1 | at
org.apache.maven.archiva.database.jdo.JdoAccess.saveObject(JdoAccess.java:192)
jvm 1 | at
org.apache.maven.archiva.database.jdo.JdoAccess.saveObject(JdoAccess.java:165)
jvm 1 | at
org.apache.maven.archiva.database.jdo.JdoProjectModelDAO.saveProjectModel(JdoProjectModelDAO.java:86)
jvm 1 | at
org.apache.maven.archiva.consumers.database.ProjectModelToDatabaseConsumer.processArchivaArtifact(ProjectModelToDatabaseConsumer.java:170)
jvm 1 | at
org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:52)
jvm 1 | at
org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
jvm 1 | at
org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateUnprocessed(JdoDatabaseUpdater.java:152)
jvm 1 | at
org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllUnprocessed(JdoDatabaseUpdater.java:86)
jvm 1 | at
org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:78)
jvm 1 | at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
jvm 1 | at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
jvm 1 | at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
jvm 1 | at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
jvm 1 | at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
jvm 1 | at java.lang.Thread.run(Thread.java:595)
Was this the error you've mentioned regarding the effective cache in your email
in the dev list?
It would really be better if you could also provide tests for these changes :)
Thanks Darios!
> database not being updated with project model information
> ---------------------------------------------------------
>
> Key: MRM-622
> URL: http://jira.codehaus.org/browse/MRM-622
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: OS: Windows XP
> Software: Java 5 Update 12 and Maven 2.0.4
> Reporter: Dário Oliveros
> Fix For: 1.1
>
> Attachments: archiva-database-consumers.patch,
> archiva-database.patch, archiva-scheduled.patch
>
>
> I noticed Archiva database was not being updated with project model
> information in the following scenario:
> 1) Project B (1.0-SNAPSHOT) depends on Project A (1.0)
> 2) Project B is deployed to Archiva repository
> 3) Project B changes Project A dependency version from 1.0 to 1.1-SNAPSHOT
> 4) Project B is deployed to Archiva repository again.
> 5) The user executes 'Scan Repository Now' and 'Update Database Now' using
> Archiva.
> At this point, if you browse project B, you'll notice it still keeps the
> reference to the former version of Project A, 1.0, and not 1.1-SNAPSHOT.
> However, if you download the POM file, you will see it has the lastet
> dependency version as expected.
> NOTE: In project B POM file the snapshotRepository is configured with
> uniqueVersion equals to false.
--
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
