[jira] Commented: (MRM-1061) 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using in parent POM.

["Reiner Saddey (JIRA)" <ji...@codehaus.org>]

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

Reiner Saddey commented on MRM-1061:
------------------------------------

I'd rather prefer Archiva do the effective pom stuff itself (or anything equivalent in order to properly interpret a maven 4.0.0 model version pom), because...

1. in my opinion, supplying additional hints to Archiva within a maven project in a non-standard way would be a plain no-no
2. it would be hard to modify existing external maven projects - and doing so would inevitably lead to chaos and confusion

Maybe Archiva should integrate emerging dependency tools (e.g. http://code.google.com/p/q4e/wiki/DependencyGraphViewer) instead of creating one of its own.

Last-not-least I wonder, whether it would be cleaner and easier to separate concerns, i.e. let the repository manager just do its archiving task and use a universal viewer that can be used with any repository manager. At first I thought that there's something missing from other repository managers. Now, when I come to think of it, it might turn out not to be a bug, but a feature instead. 

Just my thoughts,
Reiner 


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