[
http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177542#action_177542
]
Olivier Dehon commented on MRM-1061:
------------------------------------
We are talking about the indexing facility of Archiva, not viewing or
archiving. The only way for any indexing tool (Archiva or external standalone
indexer) to have the relevant information that was used at build time is to
have access to the effective pom that was used to build the artifact.
The effective pom is not just additional hints, it is the actual build setup
for that version of that artifact, and it seems fairly standard to me.
Maybe even the Jarring-up of the effective pom could be a nice enhancement to
the Archiver(s) that Maven uses to construct the Jars/Wars/Ears... helping
understand what the actual environment was when the artifact was built.
YMMV... -Olivier
> '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
