You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2009/10/09 10:34:31 UTC

[jira] Resolved: (SLING-837) Integrate JCRInstall integration tests with the main integration tests

     [ https://issues.apache.org/jira/browse/SLING-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-837.
---------------------------------------

    Resolution: Won't Fix

Issues refers to old jcrinstall code that will be removed (SLING-1141), marking won't fix.

> Integrate JCRInstall integration tests with the main integration tests
> ----------------------------------------------------------------------
>
>                 Key: SLING-837
>                 URL: https://issues.apache.org/jira/browse/SLING-837
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: JCR Install 2.0.4
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JCR Install 2.0.4
>
>
> JCRInstall integration tests currently fail since the test setup has not been adapted to the new launchpad yet. In addition, these tests may cause the build to breack due to PermGen space problems (at least on my box). Finally all integration tests should probably run together.
> So we should do this:
>   * in the short-term I switch off the JCRInstall integration tests
>   * Migrate the JCR Integration tests to the main integration tests (launchpad/testing)
>   * Configure the JCR Integration tests in a build profile, which is not active by default

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.