archiva-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRM-487) pom version is not resolved
Date Mon, 25 Aug 2008 01:56:27 GMT

    [ http://jira.codehaus.org/browse/MRM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145854#action_145854
] 

Brett Porter commented on MRM-487:
----------------------------------

yes

> pom version is not resolved
> ---------------------------
>
>                 Key: MRM-487
>                 URL: http://jira.codehaus.org/browse/MRM-487
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0-beta-1
>            Reporter: Libor Kramolis
>            Assignee: Joakim Erdfelt
>            Priority: Critical
>             Fix For: 1.0-beta-3
>
>         Attachments: archiva.log, pom-version-is-not-resolved.png, pom.xml
>
>
> I compose pom.version from 4 properties:
> --
> 	<version>${prj.ver.maj}.${prj.ver.min}.${prj.ver.inc}${prj.ver.suf}</version>
> 	<properties>
> 		<prj.ver.maj>2</prj.ver.maj>
> 		<prj.ver.min>0</prj.ver.min>
> 		<prj.ver.inc>5</prj.ver.inc>
> 		<prj.ver.suf>-SNAPSHOT</prj.ver.suf>
> 	</properties>
> --
> But it looks Archiva does not resolve pom.version and it is not possible to browse this
artifact (see attached screenshot).
> Attached archiva.log, mentioned project's pom.xml and screenshot of browse page.

-- 
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

        

Mime
View raw message