[
http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177552#action_177552
]
Olivier Dehon commented on MRM-1061:
------------------------------------
Indexing/Searching is one of most important features for which I use Archiva.
It provides the ability for a developer to retrieve artifacts based on method
names, package names, dependencies used, ... If it were working properly, it
would also allow to perform impact analysis, report statistics on shared
components usage... Possibilities are endless.
The simple (and common) case where dependency versions are defined in the
dependencyManagement section of the parent pom is enough to render the search
feature useless, let alone when dependencies themselves are dependent on the
activation of a profile.
I don't understand why using the output from help:effective-pom cannot be
agreed upon... After all, it is a pom also. Even better it is *the* pom.
I wonder how Nexus deals with this...
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying
> dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent
> POM using the <dependencyManagement> mechanism. This enables us to easily
> specify the version of an artifact to be used for all the modules in our
> project. However, when looking at the 'Dependencies' page of such a module in
> Archiva, the versions of the dependencies are not listed. Furthermore, when
> opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph
> for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to
> create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when
> looking at an artifact's 'Used By' page (for example JUNIT), the page does
> not list the modules that use the artifact if the artifact's version is
> specified in the modules parent POM using the <dependencyManagement>
> mechanism.
--
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
