[jboss-dev] Broken builds

[Ovidiu Feodorov]

A way to solve it is to partition your work into pieces that produce 
autonomous artifacts, which are (automatically) tested before you 
publish them in the repository. Then your final product becomes an 
assembly of artifacts, not source files.

You handle versioned complex artifacts the same way you handle your 
source files, with the added bonus that you can tell an artifact is 
functional and you can prove it.

Just a thought.

Adrian Brock wrote:
> The main issue is misuse of version control and 
> people doing "half-a-commit".
> No build tool is going to solve those problems. ;-)
>
> P.S. It looks like the latest breakage was my fault.
>
> i.e. no "svn add" before "svn commit"
>
> Ironic. ;-)
>
> On Fri, 2008-04-18 at 07:40 -0700, Ovidiu Feodorov wrote:
>   
>> This probably doesn't have the slightest chance of happening, but here I 
>> go: I wrote a dependency management and release automation tool that's 
>> available here for download: 
>> https://sourceforge.net/project/showfiles.php?group_id=224810 I 
>> volunteer to install it, make it work in your environment and work with 
>> you to adapt it to JBoss' needs, starting with a small project first and 
>> then expanding it, if proves to be successful.
>>
>> It's a lightweight replacement for Maven and I am using it for my 
>> projects. My clients are using it as well.
>>
>> There's a user manual under doc, if you download the bundle.
>>
>> Cheers,
>> Ovidiu
>>
>>
>> Adrian Brock wrote:
>>     
>>> i.e. broken snapshots or what was equivalent
>>> Clebert's retagging of a jboss messaging release
>>>
>>> With no proper version control we can't even rollback
>>> the broken builds :-(
>>>   
>>>       
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>