Sorry,
didn't notice the GRADLE-1712. Seems to be exactly the same dependency which causes GRADLE-1713 and GRADLE-1712

regards,
René

Am 04.08.11 00:24, schrieb Ingo Richter:
Then is this http://issues.gradle.org/browse/GRADLE-1712 a duplicate to http://issues.gradle.org/brows <http://issues.gradle.org/browse/GRADLE-1713>e/GRADLE-1713 <http://issues.gradle.org/browse/GRADLE-1713>

Ingo
--
San Francisco Blog <http://8880km.blogspot.com>
"today is tomorrows past blog" <http://ingorichter.blogspot.com>
LinkedIn Profile: <http://www.linkedin.com/in/ingorichter>
twitter: <http://twitter.com/ingorichter>



On Wed, Aug 3, 2011 at 3:21 PM, Szczepan Faber <[email protected] <mailto:[email protected]>> wrote:

    I encountered the same thing today after nuking the cache. Thanks
    for raising the issue!


    On Thu, Aug 4, 2011 at 12:19 AM, Rene Groeschke
    <[email protected] <mailto:[email protected]>> wrote:

        Hi there,

        I just tried to update my gradle workspace and failed with a
        nullpointer exception when running ./gradlew cleanIdea idea on
        gradles' codebase. I raised an issue for that with a stacktrace at

        http://issues.gradle.org/browse/GRADLE-1713

        regards,
        René

-- -----------------------
        regards René

        rene groeschke
        http://www.breskeby.com
        @breskeby


        ---------------------------------------------------------------------
        To unsubscribe from this list, please visit:

        http://xircles.codehaus.org/manage_email





-- Szczepan Faber
    Principal engineer@gradleware
    Lead@mockito




--
-----------------------
regards René

rene groeschke
http://www.breskeby.com
@breskeby

Reply via email to