[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] ECF build v2 -- Build easier

Hi Arvind,

Arvind Gupta wrote:
     Have we thought about maven?

(Scott speaking for himself) Yes sure, I've thought of Maven. I'm personally not convinced it's the way to go, however. My previous experiences with doing OSG-bundle build/deploy with Maven were less than optimal. I understand that Maven's OSGi support has probably come a long way, but frankly it's been a long time since I've worked with it very much myself...and I know exactly nothing about how/whether it creates/edits p2 repos, etc (which is where we will want to go).

Also, there is (and should be I think) some momentum here for working with Eclipse Foundation technologies and projects...e.g: Equinox, PDE, PDE build, Buckminster, p2, and ECF (!), EMF/Nick/Denis/Build Harder effort...in the name of cross-project collaboration and cooperatively sharing build infrastructure (my personal dream :).

But as with most things in ECF, the 'decision' about what technologies to use (to build ECF) is mostly going to be based upon who among us is willing and able to put in the energy to make it a reality. So if you have an idea about a build technology to use (anything we can actually get our hands on/use for an open source project), please bring it up on this list...or even better take the ECF projects/features and get a build running :).

With the build system, I would love to have a single technology solution result in dramatically less work on the ECF build/deploy infrastructure...but frankly I don't ever expect this to happen...and I'm somewhat suspicious of 'silver bullet' arguments (just use this tech and all build/deploy work will magically disappear).

Rather I expect that there will continue to be significant work in building/deploying ECF (whether that work is development of Buckminster modules/extensions, ant scripts, OS shell scripts, maven configuration, Hudson config, ECF features refactoring, etc). Of course I would like to minimize this work with good technologies, and I would also like to spread it around among ECF committers and contributors as much as possible...just so it doesn't overload or burnout anyone.



On Mon, Jul 13, 2009 at 11:38 PM, Chris Aniszczyk <zx@xxxxxxxxxxxxxxxxx <mailto:zx@xxxxxxxxxxxxxxxxx>> wrote:

    On Mon, Jul 13, 2009 at 12:21 PM, Scott Lewis
    <slewis@xxxxxxxxxxxxxxxxx <mailto:slewis@xxxxxxxxxxxxxxxxx>> wrote:

        In broad strokes, we need to:

        1) Add bundle signing (for dev.eclipse.org
        <http://dev.eclipse.org> build)
        2) Setup/refactor the features so that we can build
          a) weekly platform integration builds (i.e. filetransfer and
        ECF core)
          b) auto, daily, integration and release builds (on-demand
        for release...others can be automated)
        3) Add a builder for the features/bundles at OSU OSL
        (including JMS/ActiveMQ, Yahoo provider, TweetHub (product),
        and perhaps other things...e.g. SOC student work)
        4) Add automated junit testing
        5) Add support for Markus' work on distributing testing framework
        6+) The million other things that have to be done for 'build
        system care and feeding' :)
        7) The other things that I've forgotten

Before we hastily move to Buckminster, please note that the Athena common build system supports most of these things. I'm going to CC Nick Boldt to give some input. In PDE, we recently setup a build for some incubator code using Athena and it was easy.

-- Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

    ecf-dev mailing list
    ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>


ecf-dev mailing list