[jboss-dev] Integration of naming deployers failed

[Carlo de Wolf]

This works up to a certain point. Our own Hudson can't scale that high 
if we all wanted to run every test suite I would want on it.

Secondly, merging in svn is a bitch and you loose information during 
execution. Upgrading the svn server to 1.6 would give back some, but not 
all.

Carlo

On 01/12/2010 04:17 PM, Andrew Lee Rubinger wrote:
> A technique DML and I have enjoyed in the past is a private branch to
> hold new (potentially volatile) commits; point your private Hudson
> instance to it and run the AS testsuite on your own before merging into
> the mainline trunk.
>
> S,
> ALR
>
> On 01/12/2010 10:02 AM, Bill Burke wrote:
>    
>> Am I wrong in thinking that these naming commits were introduced to
>> trunk/ (because Hudson caught it)?  If so,  you really can't be
>> introducing errors like this.  Such fundamental changes need to go
>> through the automated test cycle before they are committed.  Otherwise
>> you're going to screw up everybody else that is working off of trunk.
>> Especially considering every "maven install" that is done pulls in new
>> snapshots.
>>
>> Ales Justin wrote:
>>      
>>> Yes, like I told you n-times, the api for scoped stuff is poor atm. ;-)
>>> To get around this, we used unique name and "real" alias via @Aliases
>>> annotation.
>>>
>>> Carlo de Wolf wrote:
>>>        
>>>> Hmm, BeanMetaDataDeployer.undeploy doesn't take scoping into account and
>>>> will undeploy a 'random' context.
>>>>
>>>> Carlo
>>>>
>>>> On 01/12/2010 01:52 PM, Carlo de Wolf wrote:
>>>>          
>>>>> The initial runs on Hudson show no success. After a couple of
>>>>> deployments it goes poof with the following error:
>>>>>
>>>>>            
>>      
>