Eclipse Community Forums: B3 » Mirror only required dependencies from a Mapped Repository

Help

Home

Home » Archived » B3 » Mirror only required dependencies from a Mapped Repository

Show: Today's Messages :: Show Polls :: Message Navigator

Mirror only required dependencies from a Mapped Repository [message #784061]

Fri, 27 January 2012 02:32

Spencer Van Hoose

Messages: 4
Registered: January 2012

Junior Member

Is it possible to add a Mapped Repository to a Validation Set, but only mirror IUs that are required dependencies for a Feature in another Mapped Repository?

I'm trying to use b3 aggregator to mirror org.eclipse.m2e.feature.feature.group from the m2e update site. I am validating against a local p2 repository that I created from my Eclipse install using FeaturesAndBundlesPublisher.

Aggregation fails with the following error:

Cannot complete the install because one or more required items could not be found.
Missing requirement: async-http-client 1.6.3.201106072137 (com.ning.async-http-client 1.6.3.201106072137) requires 'package org.ietf.jgss 0.0.0' but it could not be found

JavaPackage(org.ietf.jgss) is required by:
  ValidationSet(main)
    Contribution(m2e)
      MappedRepository(C:\Users\svanhoose\Documents\update_sites\mirrors\m2e-releases)
        Feature(org.eclipse.m2e.feature.feature.group 1.0.100.20110804-1717)
          InstallableUnit(org.eclipse.m2e.core.ui 1.0.100.20110804-1717)
            InstallableUnit(org.eclipse.m2e.core 1.0.0.20110607-2117)
              InstallableUnit(com.ning.async-http-client 1.6.3.201106072137)
Missing requirement: async-http-client 1.6.3.201108040830 (com.ning.async-http-client 1.6.3.201108040830) requires 'package javax.crypto 0.0.0' but it could not be found

JavaPackage(javax.crypto) is required by:
  ValidationSet(main)
    Contribution(m2e)
      MappedRepository(C:\Users\svanhoose\Documents\update_sites\mirrors\m2e-releases)
        Feature(org.eclipse.m2e.feature.feature.group 1.0.100.20110804-1717)
          InstallableUnit(org.eclipse.m2e.core.ui 1.0.100.20110804-1717)
            InstallableUnit(org.eclipse.m2e.core 1.0.0.20110607-2117)
              InstallableUnit(com.ning.async-http-client 1.6.3.201108040830)

If I change it to validate against the indigo update site, everything is fine. How can I add the indigo update site as a Mapped Repository but not mirror anything from it except whatever is required by m2e?

Thanks in advance.

Report message to a moderator

Re: Mirror only required dependencies from a Mapped Repository [message #831554 is a reply to message #784061]

Thu, 29 March 2012 03:11

Spencer Van Hoose

Messages: 4
Registered: January 2012

Junior Member

Anyone?

It seems like a design oversight to me that each mapped repository and the rules for mirroring from that repository are tightly coupled. Would it not be more flexible to specify a number of source repositories and the items that should be mirrored separately? Then one could:

Mirror a feature from any available source repository.
Mirror a feature from a repository and also mirror dependencies of that feature from another repository (what I'm trying to do)

Report message to a moderator

Re: Mirror only required dependencies from a Mapped Repository [message #831580 is a reply to message #831554]

Thu, 29 March 2012 04:08

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

Hi Spencer,

On 03/29/2012 05:11 AM, Spencer Van Hoose wrote:
> Anyone?
>
> It seems like a design oversight to me that each mapped repository and the rules for mirroring from that repository are
> tightly coupled. Would it not be more flexible to specify a number of source repositories and the items that should be
> mirrored separately? Then one could:
>
> Mirror a feature from any available source repository.

Not sure why this would matter. The reason you specify a feature below a repository is that it's in that particular
repository that you find the feature.

> Mirror a feature from a repository and also mirror dependencies of that feature from another repository (what I'm trying
> to do)
>
You can do this provided that all repositories are contributed in the same validation set.

There's an implicit rule that if no features are selected in a repository, then select all. So you will get the desired
effect if you add Indigo and specify one of the features that is already required by the m2e contribution. The 'select
all' rule will then not apply.

A better way of disabling the 'select all' would be great to have. Please file an enhancement request for that.

- thomas

Report message to a moderator

Previous Topic:	Possible to ignore conflicting dependencies?
Next Topic:	Adding maven central as repository to an aggregation does not complete

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Nov 09 03:37:15 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter