BTW, this is a maven core fix... right now, flexmojos result does match
dependency:tree output.

VELO

On Tue, Nov 30, 2010 at 5:12 PM, Marvin Froeder <[email protected]> wrote:

> None here, I never dig into core looking for that.  But I think you are on
> the right track
>
>
> On Tue, Nov 30, 2010 at 5:09 PM, Ryan Gardner <[email protected]> wrote:
>
>> I was doing some poking into the maven source to see why transitive
>> dependencies show up in the dependency tree but aren't being included
>> in flex mojos builds.
>>
>> What I'm thinking is that the custom scopes might be causing an issue
>> with the dependency resolver.
>>
>> The project.getArtifacts() javadoc in 3.0.1 has this statement:
>>
>>   /**
>>     * All dependencies that this project has, including transitive
>> ones. Contents are lazily
>>     * populated, so depending on what phases have run dependencies in
>> some scopes won't be
>>     * included. eg. if only compile phase has run, dependencies with
>> scope test won't be included.
>>     *
>>     * @return {...@link Set} &lt; {...@link Artifact} >
>>     * @see #getDependencyArtifacts() to get only direct dependencies
>>     */
>>    public Set<Artifact> getArtifacts()
>>
>> If they are in scope=rsl does maven resolve their dependencies?
>>
>> I'm going to do some more digging in one of the unit tests - it looks
>> like I should be able to quickly modify one of the existing tests (the
>> transitive dependency one) and use that as a starting point to test
>> this.
>>
>> It looks like the LifecycleDependencyResolver might be able to do the job
>> -
>>
>>    public void resolveProjectDependencies( MavenProject project,
>> Collection<String> scopesToCollect,
>>                                            Collection<String>
>> scopesToResolve, MavenSession session,
>>                                            boolean aggregating,
>> Set<Artifact> projectArtifacts )
>>
>> EXCEPT:
>>
>> " NOTE: This class is not part of any public api and can be changed or
>> deleted without prior notice."
>>
>> Which kind of sucks since it looks like it's the easiest hook to force
>> maven to resolve the dependencies for the custom scopes that flexmojos
>> is using.
>>
>> before I get too deep into this - I figured I'd ask for any thoughts
>> since I'm sure people here are more familiar with maven's guts than I
>> am.
>>
>> Ryan
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Flex Mojos" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]<flex-mojos%[email protected]>
>> For more options, visit this group at
>> http://groups.google.com/group/flex-mojos
>>
>> http://flexmojos.sonatype.org/
>>
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos

http://flexmojos.sonatype.org/

Reply via email to