You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2009/03/15 07:33:12 UTC
[jira] Assigned: (MRM-1105) Legacy artifact path not properly
stored when entered from Archiva UI
[ http://jira.codehaus.org/browse/MRM-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching reassigned MRM-1105:
-------------------------------------
Assignee: Maria Odea Ching
> Legacy artifact path not properly stored when entered from Archiva UI
> ---------------------------------------------------------------------
>
> Key: MRM-1105
> URL: http://jira.codehaus.org/browse/MRM-1105
> Project: Archiva
> Issue Type: Bug
> Components: browser
> Reporter: Kannan Kesavan
> Assignee: Maria Odea Ching
> Fix For: 1.2-M2
>
> Attachments: legacy_artifact_path_issue.zip
>
>
> For one of the module in our project (which violates artifact conventions) we need to add legacy artifact path. I have tried to add this from archiva admin screen. Please find the attached screen shot for this.
> Once it is entered, it come to summary screen. In the summary screen value for the 3rd part is null (i.e) In my example
> part[0] -> gp
> part[1] -> sr-gp-test
> part[2] -> null ---> 3rd part, which is incorrect. I have entered Version for this artifact.
> part[3] -> 1.0.2 ---> whatever we entered in Version is misplaced in Classifier.
> I have also attached 3rd screen shot when I try to browse this artifact. I went through LegacyArtifactPath.java where these split ups are actually occurring with respect to legacy artifact path.
--
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