[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Re: Running integration tests with maven
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Tue, 20 Jul 2010 09:00:01 -0700
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: AcsoJJw4G3UQJg0zSAiunIqIPXqMjA==
- Thread-topic: [virgo-dev] Re: Running integration tests with maven
To be fair, I think Virgo build (underpinned by Ant/Ivy) has been quite smooth. If it didn't need to cope with OSGi and versioning, it would be simpler still. It seems Pete's experience of Maven is similar.
So we have some reasonable build solutions, we have some approaches to versioned dependencies that kind of work, and we are feeling our way towards some kind of best practice with distributed development. :-)
On 20 Jul 2010, at 16:47, Pete Carapetyan wrote:
PS. In all my 28 years in this industry, I have never worked on a project where the build/dependency management tool really worked -- they always have little wrinkles that people need to work around -- or that everyone on the project really understood -- people (with the possible exception of one or two build experts, but usually not) just kid themselves into thinking they understand. Virgo is unfortunately no different.
Ditto for me, except last year we moved to a maven build on Hudson with 30+ modules (no OSGi) and for whatever reason it was nearly painless for the entire 1.5 year project. I kept waiting for the shoe to drop, but people came, people went, it just kept on being easy, and it kept on being dumb. And except that I only have 15 years in the industry, not 28 like Glyn. We also used ant for one module, but Hudson didn't care.