Re: [cbi-dev] Eclipse CBI Juno M6 packaging

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

There are some features marked as 'optional', maybe this is the reason? Some of the features are only available on certain operating systems (and not on Windows / Mac OSX).

BTW: On which operating system are you doing your local tests?

Regards,
Markus

On Wed, Mar 28, 2012 at 04:02, Thanh Ha <thanh.ha@xxxxxxxxxxx> wrote:

Hi Everyone,

I pushed up to the CBI repositories the modifications to have the packaging repository use tycho. You can git clone it with:

  git clone git://git.eclipse.org/gitroot/cbi/org.eclipse.epp.packages.git
  git checkout Juno_M6



There was 2 packages I was not able to successsfull build however the cpp and parallel packages. The both failed due to missing requirement for org.eclipse.linuxtools.rpm.ui.editor.feature_0.0.0. I'm not sure why this is but I left them commented out in the parent pom file for now.


Thanh

On 03/27/2012 10:56 AM, Markus Knauer wrote:

The historical development is different: it's not a merge in the Git repository, it has been always like this in EPP because Buckminster is able to use this layout for the packages. Now it would be interesting to know *why* Igor chose a different layout. Maybe he was running into the same problem that you are mentioning below.

Buckminster uses a top-level feature (aka 'allpackages') which references all the package features. Each package feature contains a .product file and references a branding plug-in. That's why we need only two projects per package: One feature (including the .product file) and one plug-in project.

If I remember it correctly, Igor's approach had separated the .product file from the feature.

Markus

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev