[
http://jira.codehaus.org/browse/MRM-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185320#action_185320
]
Maria Odea Ching edited comment on MRM-1158 at 7/30/09 3:26 AM:
----------------------------------------------------------------
Just to clarify, the issue here is that the consumer should still process
artifacts with legacy paths s.a. app/poms/app-1.0.pom even though the Archiva
repository it was deployed to has a default layout?
Btw, I was able to successfully deploy the Maven 1 artifact to the Archiva M2
repo. I saw the same log info above and it seemed that the artifact actually
deployed but was just not processed by the consumers.
was (Author: oching):
Just to clarify, the consumer should still process artifacts with legacy
paths s.a. app/poms/app-1.0.pom even though the Archiva repository it was
deployed to has a default layout?
> Maven 1.x deployment fails
> --------------------------
>
> Key: MRM-1158
> URL: http://jira.codehaus.org/browse/MRM-1158
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
> Affects Versions: 1.2
> Reporter: Brett Porter
> Assignee: Maria Odea Ching
> Fix For: 1.2.2
>
>
> deploying with Maven 1:
> {code}
> 2009-03-30 23:17:38,396 [btpool0-7] INFO
> org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer - Not
> processing path that is not an artifact: app/poms/app-1.0.pom (Not enough
> parts to the path [app/poms/app-1.0.pom] to construct an ArchivaArtifact
> from. (Requires at least 4 parts))
> {code}
> It seems this is not using the proper path mapping. I believe this should
> work even though the hosted repo is maven2
--
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
