You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Libor Kramolis (JIRA)" <ji...@codehaus.org> on 2007/08/29 11:45:11 UTC
[jira] Created: (MRM-487) pom version is not resolved
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
Priority: Critical
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
[jira] Work started: (MRM-487) pom version is not resolved
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MRM-487 started by Joakim Erdfelt.
> 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
[jira] Updated: (MRM-487) pom version is not resolved
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt updated MRM-487:
-------------------------------
Assignee: Joakim Erdfelt
Fix Version/s: 1.0-beta-3
> 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
[jira] Closed: (MRM-487) pom version is not resolved
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt closed MRM-487.
------------------------------
Resolution: Fixed
Fixed in archiva/trunk revision 580514.
> 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