Eclipse Community Forums: Buckminster » Aggregator chooses only newest version ?

Home » Archived » Buckminster » Aggregator chooses only newest version ?

Aggregator chooses only newest version ? [message #519480]

Mon, 08 March 2010 18:14

Eclipse User

This is a multi-part message in MIME format.
--------------020407070406000403000000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

i have the following attached Aggregator definition.

My problem/question is: now at the time being there is Gallileo SR2.
However for specific reasons I also want Gallileo SR1.
How can I get this ?

the aggregator seems to fetch only the newest version, e.g.
org.eclipse.jdt.3.5.2 but i would like _also_ the 3.5.1

thanks,
Bernhard.

--------------020407070406000403000000
Content-Type: text/xml;
name="Aggregator.Gallileo.build"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="Aggregator.Gallileo.build"

<?xml version="1.0" encoding="UTF-8"?>
<aggregator:Aggregator xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:aggregator="http://www.eclipse.org/buckminster/2009/aggregator" label="Galieo RCP Target">
<configurations/>
<configurations operatingSystem="linux" windowSystem="gtk"/>
<contributions label="Galileo">
<repositories location="http://download.eclipse.org/releases/galileo" categoryPrefix="galileo">
<metadataRepository href=" p2:http://download.eclipse.org/releases/galileo#//@metadataR epository"/>
</repositories>
</contributions>
</aggregator:Aggregator>

--------------020407070406000403000000--

Re: Aggregator chooses only newest version ? [message #519515 is a reply to message #519480]

Tue, 09 March 2010 02:04

Eclipse User

Hi Bernhard,

the aggregator tries to use the latest version of every mapped IU. The aggregation result is always consistent, i.e. even if you install everything from the aggregated repository, there will never be a version conflict. It may happen that there are lower than latest versions of some IUs if it's necessary for the result consistency.

You cannot have more than one version of an IU in the aggregation result.

If you want to exclude a specific version, you can use the "Exclusion rule" for you mapped repository. You can also define more than one mapping in you aggregator definition, such as

+ Mapped repository http://downloads.eclipse.org/releases/galileo (i.e. map everything from this repo)
+ Mapped repository http://downloads.eclipse.org/releases/galileo
|
+ Bundle org.eclipse.jdt/3.5.1

which will force the aggregator to use version 3.5.1.

Regards
Filip

Note: The buckminster aggregator will be replaced with the b3 aggregator which will provide more flexibility. The b3 aggregator is available on http://download.eclipse.org/modeling/emft/b3/updates-3.6 for testing. It is always synchronized with the latest Helios integration build (synchronization
with the integration build from last weekend will be available with 1-2 days).

Bernhard Merkle wrote:
> Hi,
>
> i have the following attached Aggregator definition.
>
> My problem/question is: now at the time being there is Gallileo SR2.
> However for specific reasons I also want Gallileo SR1.
> How can I get this ?
>
> the aggregator seems to fetch only the newest version, e.g.
> org.eclipse.jdt.3.5.2 but i would like _also_ the 3.5.1
>
> thanks,
> Bernhard.
>

Re: Aggregator chooses only newest version ? [message #520045 is a reply to message #519515]

Wed, 10 March 2010 13:06

Eclipse User

Hi Filip!

On 09-03-2010 08:04, Filip Hrbek wrote:
>
> Note: The buckminster aggregator will be replaced with the b3 aggregator
> which will provide more flexibility. The b3 aggregator is available on
> http://download.eclipse.org/modeling/emft/b3/updates-3.6 for testing. It
> is always synchronized with the latest Helios integration build
> (synchronization
> with the integration build from last weekend will be available with 1-2
> days).

Does this mean that it will no longer be possible to execute the
aggregator headless with Buckminster (I guess if it's not part of
Buckminster there will not be an action)? If so, how will it be possible
to execute it headless?

Thanks.

/John

Re: Aggregator chooses only newest version ? [message #520047 is a reply to message #520045]

Wed, 10 March 2010 18:26

Eclipse User

John wrote:
> Does this mean that it will no longer be possible to execute the
> aggregator headless with Buckminster (I guess if it's not part of
> Buckminster there will not be an action)? If so, how will it be possible
> to execute it headless?
>

b3 provides headless interface similar to buckminster (with eclipse application name "b3").

The update site for headless b3 is http://download.eclipse.org/modeling/emft/b3/headless-3.6

Filip

Previous Topic:	buckminster resets "build automatically" in my workspace
Next Topic:	Aggregator eats CPU and runs forever at 5%... with 3 update sites

Goto Forum:

-=] Back to Top [=-

Current Time: Sat May 17 06:18:13 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter