maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Phillpotts (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MJAVADOC-319) Using groupId and artifactId in dependencySourceInclude results in source not being resolved
Date Tue, 07 Jun 2011 10:47:22 GMT
Using groupId and artifactId in dependencySourceInclude results in source not being resolved
--------------------------------------------------------------------------------------------

                 Key: MJAVADOC-319
                 URL: http://jira.codehaus.org/browse/MJAVADOC-319
             Project: Maven 2.x Javadoc Plugin
          Issue Type: Bug
    Affects Versions: 2.8
         Environment: Maven 3.0.3
            Reporter: James Phillpotts


When using the syntax groupId:* dependencies are resolved fine.

However, when using syntax groupId:artifactIdFragment* or groupId:artifactId, source dependencies
are not resolved.

I have done some debugging, and find that upon entering ResourceResolver.resolveAndUnpack,
the list of Artifacts to be resolved is correct, but on resolution (http://svn.apache.org/viewvc/maven/plugins/tags/maven-javadoc-plugin-2.8/src/main/java/org/apache/maven/plugin/javadoc/resolver/ResourceResolver.java?view=markup
line 336), the list of artifacts returned in the resolution result is null.

I don't know whether this is a bug with the javadoc plugin's use of the resolver, or of the
resolver which I assume is part of maven core, but I'm raising here as I haven't seen the
same problem with filtering anywhere else.

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