maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabrice BELLINGARD (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRM-615) When scanning, Archiva doesn't resolve properties/variables of POMs in managed repositories
Date Tue, 04 Dec 2007 10:03:57 GMT

     [ http://jira.codehaus.org/browse/MRM-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Fabrice BELLINGARD updated MRM-615:
-----------------------------------

    Summary: When scanning, Archiva doesn't resolve properties/variables of POMs in managed
repositories  (was: Whan scanning, Archiva doesn't resolve properties/variables of POMs in
managed repositories)

> When scanning, Archiva doesn't resolve properties/variables of POMs in managed repositories
> -------------------------------------------------------------------------------------------
>
>                 Key: MRM-615
>                 URL: http://jira.codehaus.org/browse/MRM-615
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.0
>            Reporter: Fabrice BELLINGARD
>            Priority: Critical
>
> If you have a JAR with a POM that contains variables (like "pom.version") or properties,
Archiva doesn't resolve them when scanning and analysing the repository. Some of the multiple
consequences are that the "Dependencies" tab can list dependencies without "real" versions,
and that the "Dependency Tree" tabs can break with an exception "Unable to generate graph
for [XXX] : Unable to create ArchivaArtifact with empty version".
> A consequence of this bug can be seen by following these steps:
> * install Archiva 
> * ask for the following artifact: http://localhost:8080/archiva/repository/internal/org/apache/maven/archiva/archiva-model/1.0/archiva-model-1.0.jar
> * then go to the page: http://localhost:8080/archiva/browse/org.apache.maven.archiva/archiva-model/1.0/
> ** on the "Dependencies" tab: there's no version for the dependencies (which is linked
to the fact that the versions are defined in the parent POM, but if ${pom.version} would have
been specified, we would have had "${pom.version}"...}
> ** on the "Dependency Tree", we get the "Unable to generate graph for [XXX] : Unable
to create ArchivaArtifact with empty version" exception
> This bug breaks other functionalities like the "Used by" tab.

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