Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Eclipse CBI Juno M6 packaging 
Tycho requires separate project for RCP applications (i.e. project
packaged based on .product files). This is required to guarantee proper
project dependencies.

--
Regards,
Igor

On 12-03-27 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

On Tue, Mar 27, 2012 at 16:46, Thanh Ha <thanh.ha@xxxxxxxxxxx
<mailto:thanh.ha@xxxxxxxxxxx>> wrote:

    Hi Everyone,

    I have another question related to tycho.

    In the new EPP repository the org.eclipse.epp.package.java.__product
    directory contents was merged into the
    org.eclipse.epp.package.java.__feature directory.


    In Igor's repository this was 2 separate directories and thus in the
    pom files they were defined as follows:

    java.feature pom:

    <artifactId>org.eclipse.epp.__package.java.feature</__artifactId>
    <packaging>eclipse-feature</__packaging>

    java.product pom:

    <artifactId>org.eclipse.epp.__package.java.product</__artifactId>
    <packaging>eclipse-repository<__/packaging>

    <build>
    ...
    </build>


    I'm not exactly sure how to properly merge these 2 into 1 pom. Can
    this be done?


    Thanks,



    Thanh


    On 03/27/2012 09:54 AM, Markus Knauer wrote:

        Hi Thanh,

        that's correct, the EPP project moved to Git just a few weeks
        ago. So every work should be based on [2] that you mention below.

        About the packages in question: If you are working with the HEAD
        in the EPP repository, you are working with the configuration
        for Juno. There are some new packages (e.g. the Automotive,
        maybe others will follow), and some have been removed compared
        to Indigo (e.g. Javascript, LinuxTools), and I did a bit
        clean-up (e.g. the transition feature, Pulsar, PHP packages).

        Does that help?

        Regards,
        Markus

    _________________________________________________
    cbi-dev mailing list
    cbi-dev@xxxxxxxxxxx <mailto:cbi-dev@xxxxxxxxxxx>
    http://dev.eclipse.org/__mailman/listinfo/cbi-dev
    <http://dev.eclipse.org/mailman/listinfo/cbi-dev>





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

Back to the top