| Hi David, 
 even with reloading the other runtime target, there are problems
    with the unit "com.ibm.icu". If I remember it correctly, haven't
    re-versioning problems occurred with the com.ibm.icu plug-in a while
    ago? Something like a switch from version 4.8.x to 50.2.x? Could
    that cause the problems?
 
 
 Cheers
 Philip
 
 
 
 
 
 Am 22.01.2014 15:27, schrieb David M
      Williams:
 Yeah, those look like
        the kind of things
        I see when I mentioned sometimes I have to "futz" with it to
        get it to reload ... such as picking the other runtime target
        reloading
        it. Then going back to eclipse-sdk target and reloading it. 
      
 If anyone knows of "the magic
        touch",
        let us know. (But, I do know it "works for me" ... eventually).
 
 
 
 
 From:      
         Philip Wenig
        <philip.wenig@xxxxxxxxxxxxxx>
 To:      
         cbi-dev@xxxxxxxxxxx,
 Date:      
         01/22/2014 09:18 AM
 Subject:    
           Re: [cbi-dev]
        Failure at the end of repository generation
 Sent by:    
           cbi-dev-bounces@xxxxxxxxxxx
 
 
 
 
 Hi David,
 
 that would be great. I've tested it, but the target throws a
        couple of
        errors, even though I've added the "{eclipse_home}" location
        and the integration build "4.4.I20131210". The screenshots are
        attached.
 
 
 Best regards,
 Philip
 
 
 Am 22.01.2014 14:37, schrieb David M Williams:
 Yes, we do have a target for
        'master'
        also.
 
 Assuming you have imported 'aggregator' in workspace, you pretty
        much just
        have to go to PDE Tools Preferences, and you'll see
        'eclipse-sdk-prereqs.target'
        as a choice to pick from "Target Runtimes" ... and that will
        give you all the "third party" prereqs the SDK needs.
 
 The complication is that most developers do not have ALL our
        other non-third
        party bundles loaded in their workspace (such as equinox, swt,
        etc.) so
        you also want "running platform" as part of your target. So what
        I do ... before making switch in PDE preferences ... is  hand
        edit
        'eclipse-sdk-prereqs.target' (you have to use text editor, as
        far as I
        know) and I add the minimum necessary XML to also include
        'running platform'
        to the list of locations:
 
 <location path="${eclipse_home}" type="Profile"/>
 
 (And then of course not commit that local, hand edited version
        of 'eclipse-sdk-prereqs.target').
 
 There is a 'reload' button in target definitions you'll
        occasionally have
        to use to "get current" (and sometimes, I have to "futz"
        with it, such as switch to another target, and then switch back,
        before
        it will really 'reload' prereqs).
 
 And, naturally, you would still need a recent I-build or perhaps
        milestone
        as your "development environment" so your 'running platform'
        is close to what we are submitting to builds.
 
 HTH
 
 
 
 
 
 From:        Lars
        Vogel <lars.vogel@xxxxxxxxx>
 To:        Common-build
        Developers discussion <cbi-dev@xxxxxxxxxxx>,
 Date:        01/22/2014
        05:59 AM
 Subject:        Re:
        [cbi-dev] Failure at the end of repository generation
 Sent by:        cbi-dev-bounces@xxxxxxxxxxx
 
 
 
 
 Hi David,
 
 a bit unrelated but do we also have a target file for developing
        Eclipse
        platform against master? If I checkout platform.ui in a my
        workspace I
        always have to install or import several projects to get rid of
        (most of)
        the compiler errrors.
 
 Best regards, Lars
 
 
 2014/1/22 David M Williams <david_williams@xxxxxxxxxx>
 I think the problem would be many different things, but we (in
        Platform)
        did very recently upgrade our jetty pre-req to the most recent
        version
        in Jetty's "8.x" stream ... so that might be adding to your
        problems?
        (See bug 416718)
         Not sure how you
        specify pre-reqs,
        but we use target files with specific repositories and specific
        versions
        required. (Such as see our current target
            file for
        R4_3_maintenance).
 
 If you build against a "tagged version" of R4_3_maintenance,
        then you may have to move to the very latest to get the changes
        ... M20140117-0910.
 
 HTH
 
 
 
 
 From:        Terry
        Parker <tparker@xxxxxxxxxx>
 To:        cbi-dev@xxxxxxxxxxx,
 Date:        01/22/2014
        12:12 AM
 Subject:        [cbi-dev]
Failure
        at the end of repository generation
 Sent by:        cbi-dev-bounces@xxxxxxxxxxx
 
 
 
 
 I'm trying to do a build from the R4_3_maintenance branch and at
        the end
        of the build I get the error below. The org.eclpse.jetty.*
        plug-ins don't
        appear to be built by the CBI build itself, so is this just a
        temporary
        server availability issue, or a configuration problem?
 
 Thanks,
 Terry
 [ERROR] Failed to execute goal
        org.eclipse.tycho:tycho-p2-publisher-plugin:0.18.1:publish-products
        (default-publish-products) on project
        eclipse.platform.repository: Execution
        default-publish-products of goal
        org.eclipse.tycho:tycho-p2-publisher-plugin:0.18.1:publish-products
        failed: "No solution found because the problem is
        unsatisfiable.":
        ["Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.continuation
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.http
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.io
        [8.1.10.v20130312].", "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.security
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.server
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.servlet
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.util
        [8.1.10.v20130312].",
        "No solution found because the problem is unsatisfiable."] ->
        [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException:
        Failed
        to execute goal
        org.eclipse.tycho:tycho-p2-publisher-plugin:0.18.1:publish-products
        (default-publish-products) on project
        eclipse.platform.repository: Execution
        default-publish-products of goal
        org.eclipse.tycho:tycho-p2-publisher-plugin:0.18.1:publish-products
        failed: "No solution found because the problem is
        unsatisfiable.":
        ["Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.continuation
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.http
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.io
        [8.1.10.v20130312].", "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.security
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.server
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.servlet
        [8.1.10.v20130312].",
        "Unable to satisfy dependency from
        org.eclipse.equinox.server.jetty.feature.group
        1.1.0.v20130429-1600 to org.eclipse.jetty.util
        [8.1.10.v20130312].",
        "No solution found because the problem is unsatisfiable."]
 --Terr_______________________________________________cbi-dev mailing list
 cbi-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/cbi-dev
 
 _______________________________________________
 cbi-dev mailing list
 cbi-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/cbi-dev
 
 _______________________________________________
 cbi-dev mailing list
 cbi-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/cbi-dev
 
 
 
        _______________________________________________
 cbi-dev mailing list
 cbi-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/cbi-dev
 
 
 --
 ~~~~~~~~~~~~~~~~~~~~~~~~
 Dr. Philip Wenig
 
 http://www.openchrom.net
 
 https://www.xing.com/profile/Philip_Wenig
 http://de.linkedin.com/pub/philip-wenig/2a/4a8/877
 ~~~~~~~~~~~~~~~~~~~~~~~~[attachment "Target1.jpg" deleted by
            David M Williams/Raleigh/IBM] [attachment "Target2.jpg"
            deleted
            by David M Williams/Raleigh/IBM] _______________________________________________
 cbi-dev mailing list
 cbi-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/cbi-dev
 
 
 
 
 _______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev
 
 -- 
~~~~~~~~~~~~~~~~~~~~~~~~
Dr. Philip Wenig
http://www.openchrom.net
https://www.xing.com/profile/Philip_Wenig
http://de.linkedin.com/pub/philip-wenig/2a/4a8/877
~~~~~~~~~~~~~~~~~~~~~~~~ |