[Anthill-pro] Re: Maven Build Error

[Eric Minick]

Nir,

This I hadn't seen before. I do know that some SCM steps cannot be 
aborted. When you inspect the hung build requests, do you see the 
command it is trying to run?

I wonder if its doing something like trying to get the change history 
since the beginning of time, or something extremely time consuming like 
that.

Regards,

Eric

Silgi, Nir wrote:
> Thanks Eric,
>
> Jason Schatz already answered me and it was indeed that known Maven bug,
> I put a "." and now it works (we will upgrade by the end of this week to
> the new version)
>
>
>
> I have another problem I would like to raise. On the same Maven project,
> when I use Changelog Quiet Period (1 sec, fixed agent) and run a build,
> the build is stuck in Determining Quiet Period forever, abort doesn't
> help either (WF Skip Quiet period is 'no'). I have this problem
> currently with two projects. The only similarity between these projects
> seems to be that both were created as 'copy of' another project. It
> doesn't happen on 'original' projects.
> Is there anything I can do other than not using Quiet Period?
>
>
> Thanks
> NirS
>
>
> -----Original Message-----
> From: Eric Minick [mailto:etm at urbancode.com]
> Sent: Tuesday, July 31, 2007 6:51 PM
> To: Silgi, Nir
> Cc: anthill-pro at lists.urbancode.com; support at urbancode.com
> Subject: Re: Maven Build Error
>
> Nir,
>
> I looked at a couple different versions of AnthillPro, and an error at
> line 96 doesn't make a whole lot of sense in either. Could you please
> remind me which version of Anthill you are using so I can better run
> down the error?
>
> I know in some older versions it might be an issue where the working
> build has a path to build file of '.' while the failing one has a
> completely empty path there. That might be something to double check.
>
> Regards,
>
> Eric
>
> Silgi, Nir wrote:
>   
>> Hi,
>>
>>
>>
>> I have two Maven projects, both of them are configured almost the same
>> way and they use the same agent (same build machine). The Maven build
>> job is configured the same. One of them is building ok, the other one
>> throws an exception in the Maven build step:
>>
>>
>>
>> 2007-07-29 10:14:03,188 ERROR 3831 7 - org.apache.bsf.BSFException:
>>     
> The
>   
>> application script threw an exception: java.lang.NullPointerException
>> BSF info: scripts/maven/maven-build.bsh at line: 96
>>
>> I really think I checked everything I have no idea what could be the
>> problem.
>>
>> Any help would be appreciated.
>>
>> Thanks,
>> NirS
>>
>>
>>
>>
>>     
> <http://775146.sigclick.mailinfo.com/sigclick/06040405/02074D06/07064D07
>   
>> /11314611.jpg> 
>>
>>  
>>     
>
>
>
>
>  
> <http://775146.sigclick.mailinfo.com/sigclick/00050003/07044806/0F074901
> /17252324.jpg>  
>
>