[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] resolving implicit dependency in project configurator

Thanks.  I'll give this a try.

On Wed, May 30, 2012 at 12:25 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> IMaven#resolve can be used to resolve an artifact from specified Maven
> repositories. This call will download the artifact if necessary. There
> is currently no proper way to force re-resolution of the artifact if
> it's available in maven local repository, but you may be able to use
> ArtifactRepository.setReleaseUpdatePolicy and/or .setSnapshotUpdatePolicy.
>
> --
> Regards,
> Igor
>
>
> On 12-05-30 1:39 PM, Andrew Eisenberg wrote:
>>
>> Hi all,
>>
>> I am creating a project configurator for a maven plugin and maven
>> extension.  The extension (among other things) adds an implicit
>> dependency to the project.  I would like to replicate this
>> functionality inside of the project configurator.  I know the
>> artifact, group, and version of the dependency.  My question is: how
>> to I resolve that to get a jar file in the local repo?  Furthermore,
>> if the artifact has not been downloaded yet, how do I force it to be
>> so?
>>
>> thanks,
>> _______________________________________________
>> m2e-dev mailing list
>> m2e-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev