[
http://jira.codehaus.org/browse/MRM-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171680#action_171680
]
Dennis Lundberg commented on MRM-1161:
--------------------------------------
In the previous example, the jar-file is inserted into the Archiva repository.
However if I try to deploy an old corporate artifact and specify a hand crafted
pomFile on the command line, only the jar file is inserted into the Archiva
repository - not the POM itself. Something like this:
H:\svn>mvn deploy:deploy-file
-Dfile=P:/Development/lib/databas/RELEASE-1_5/shared/lib/mdh-databas-shared.jar
-DpomFile=mdh-databas-shared-1.5/pom.xml -Dversion=1.5
-Durl=dav:http://repo.mdh.se/archiva/repository/internal
-DrepositoryId=internal -e
This renders the same error message/stack trace as the previous example.
> indexing causes NullPointer when getting a SNAPSHOT that has been deployed
> with maven 2.1
> -----------------------------------------------------------------------------------------
>
> Key: MRM-1161
> URL: http://jira.codehaus.org/browse/MRM-1161
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: nicolas de loof
> Priority: Critical
> Fix For: 1.2.1
>
>
> A fresh SNAPSHOT has been deployed on a (file based) repo. Archiva is
> configured to proxy this one to "snapshots" managed repo.
> getting the SNAPSHOT metadata, POM or JAR results in :
> java.lang.NullPointerException
>
> org.sonatype.nexus.index.context.DefaultIndexingContext.copyDocument(DefaultIndexingContext.java:582)
>
> org.sonatype.nexus.index.packer.DefaultIndexPacker.writeIndexChunks(DefaultIndexPacker.java:168)
>
> org.sonatype.nexus.index.packer.DefaultIndexPacker.packIndex(DefaultIndexPacker.java:94)
>
> org.apache.archiva.consumers.lucene.NexusIndexerConsumer.completeScan(NexusIndexerConsumer.java:211)
>
> org.apache.archiva.repository.scanner.functors.TriggerScanCompletedClosure.execute(TriggerScanCompletedClosure.java:48)
>
> org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
>
> org.apache.maven.archiva.repository.scanner.RepositoryContentConsumers.executeConsumers(RepositoryContentConsumers.java:265)
>
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:576)
>
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:163)
>
> org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:554)
>
> org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.processRepository(ArchivaDavResourceFactory.java:430)
>
> org.apache.maven.archiva.webdav.ArchivaDavResourceFactory.createResource(ArchivaDavResourceFactory.java:236)
>
> org.apache.maven.archiva.webdav.RepositoryServlet.service(RepositoryServlet.java:116)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:413)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
>
> org.apache.struts2.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:99)
> Same thing don't occurs if the SNAPSHOT is deployed with webdav in archiva
> directly
--
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
