I think I've fixed this one on post 6.5 beta builds (in current dev).
The problem was in handling input/output. In some situations it wa`s
not released properly and the thread queue designated for the
processing got stuck. The symptom was that every new build resulted in
empty output window.
Milos
On Wed, Sep 10, 2008 at 1:16 AM, Ravi Luthra <
coding@...> wrote:
> Hi,
>
> We've got a few different users of Mevenide. We have a NB 6.1 3.1.4
> (Windows) user, and two NB 6.5 4.0.2 (one Ubuntu and one Windows).
>
> We often use the external Maven (2.1.0 RC 16) now because of some
> incompatibilities with the deployment module. Lately we've actually
> had some freeze ups when using the external one. It happens seemingly
> randomly, but pretty often. I think it might have something to do with
> invoking the build on a project that is already building... like
> mis-clicking on build now twice.
>
> We've tried Maven 2.1.0 RC 16 on both NB 6.1 and NB 6.5 and get the
> freezing a lot. We can't use the release Maven at the moment because
> of fixes we had to make to accommodate a similar problem on Hudson.
>
> Is anyone else getting this build freezing behavior?
> WARNING: You are running Maven builds externally, some UI
> functionality will not be available.
> Executing:/home/ravi/java/apache-maven-2.1.0-M1-RC16/bin/mvn install
>
> Normally very quickly there's a "Scanning for projects..." following
> the last line above.
>
> Anyone else got a frozen mevenide?
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
