Everything is back to normal.
--
Alex

________________________________________
From: development-bounces+alexander.blasche=theqtcompany....@qt-project.org 
<development-bounces+alexander.blasche=theqtcompany....@qt-project.org> on 
behalf of Blasche Alexander <alexander.blas...@theqtcompany.com>
Sent: Monday, January 19, 2015 09:25
To: development@qt-project.org
Subject: Re: [Development] JIRA broken

I can confirm there is a problem with Jira. We'll investigate.

--
Alex

________________________________________
From: development-bounces+alexander.blasche=theqtcompany....@qt-project.org 
<development-bounces+alexander.blasche=theqtcompany....@qt-project.org> on 
behalf of Guido Seifert <warg...@gmx.de>
Sent: Sunday, January 18, 2015 13:22
To: development@qt-project.org
Subject: [Development] JIRA broken

when I add:

> Project: Qt

> Issue Type: Bug

> Summary: Ninja for qtwebengine out-of-source build not possible

> Affects Version/s: 5.5

> Component/s: Build System

> Description:

> When I do an out-of-source build, e.g. sources in 'qt5' and a
> '../qt5/configure' in a separate 'qt5-build' folder, ninja for the 
> qtwebengine is
> still build within qt5/qtwebengine/src/3rdparty/ninja/ and not in the 
> qt5-build tree.

> Apart from the pure cosmetic ugliness to have created code in a folder
> below 'src', it is ugly because it taints the sources, which prevents
> to move the source tree easily to a different machine, or have the
> sources read-only.

> Environment: Apparently all

I get:
 Error creating issue: Indexing completed with 1 errors

Guido
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to